GEH 6700 Jan2018 Toolbox
GEH 6700 Jan2018 Toolbox
GEH 6700 Jan2018 Toolbox
GE Internal
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.
GE Internal – This document is proprietary. It contains information that belongs to the General Electric Company 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 or the information it contains shall not be reproduced in whole or in part or disclosed to
any third party without the express written consent of GE.
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.
For further assistance or technical information, contact the nearest GE Sales or Service Office, or an authorized GE Sales
Representative.
GE Internal
Document Updates
Location Description
Updated the table with support for Windows 7 Ultimate or Professional as both a
Computer Recommendations Recommended and Supported operating system
Added an Attention for ToolboxST Windows10 Display Issues
Updated the figure ControlST Installation Options to include the ControlST Supplement
Installation Package installation option, which installs Mark VIeS Safety Controller V05.03, as well as
the associated Distributed Safety I/O packs.
Updated the figure System Settings Window to remove the Display Variable Aliases
System Settings instead of Variable Names setting, which has been moved to the WorkstationST
Preferences menu
Moved the Display Variable Aliases instead of Variable Names setting to the
Variable Names and Aliases WorkstationST Preferences menu, and added the figure WorkstationST Preferences
Menu
Users and Roles Added procedure to define users and roles in ToolboxST
Removed the Display Variable Aliases instead of Variable Names setting from the Alias
Mark VIe, Mark VIeS, MarkStat, EX2100e, and description and refer to the section Variable Names and Aliases
LS2100e Program Variables Added the available visibility option descriptions in the table Data Grid Variable
Properties
Mark VIe, Mark VIeS, WorkstationST, MarkStat,
Updated the description for Enable Alias Prefix in the table General Tab Properties
EX2100e, and LS2100e General Tab
Added two properties to the WorkstationST General Properties table
WorkstationST General Tab • Crash Dump Location
• Number of Crash Dumps to Retain
Added the diagnostic alarm message that displays in the Status tab when the factory
System Component Password Change
default controller password has not been changed
Added FOUNDATION Fieldbus Alarm Confirm Time property to the Settings Properties
Controller Settings table and updated the Controller Settings Window figure, which was removed from the
PFFA Hardware tab Property Editor and moved to Controller Settings.
Updated the screenshot of the Property Editor and the Fieldbus Device Properties table
in the procedure To instance a fieldbus device placeholder to remove the FOUNDATION
Instance (Add) a Fieldbus Device Placeholder
Fieldbus Alarm Confirm Time property from the PFFA Hardware tab Property Editor and
moved it to Controller Settings
Updated the screenshots showing the Property Editor in the procedure To enable H1
Fieldbus Device Alerts device alerts and To add alerts to a FOUNDATION fieldbus task to remove the
FOUNDATION Fieldbus Alarm Confirm Time property
Download Fieldbus Devices Added a reference to the section Controller Settings
Added the diagnostic alarm message that displays in the Status tab when the factory
Mark VIe, Mark VIeS, MarkStat, EX2100e, and default controller password has not been changed
LS2100e Controller Password Change Added the procedure to synchronize controller passwords when a controller in a
redundant set is replaced
System Controller Device Types Added UCSC to Mark VIeS Safety Control list of supported controller device types
Control Constants Import and Export Updated this section with newer formatting
Mark VIe, Mark VIeS, MarkStat, Power
Conversion, WorkstationST, EX2100e, and
Restructured this section for each product for consistency
LS2100e,
Download to Controller
Added an Attention note to notify users using PPRF, PPNG, and PCSA in a dual network
Mark VIe Download to Controller configuration requires an offline load if the output map changes, as well as instructions to
not add or remove Mark VI VME boards during an online download
Related Documents
Document Title Document #
Mark VIe and Mark VIeS Control Systems Volume I: System Guide GEH-6721_Vol_I
Mark VIe and Mark VIeS Control Systems Volume II: General-purpose Applications GEH-6721_Vol_II
Mark VIe and Mark VIeS Control Systems Volume III: For GE Industrial Applications GEH-6721_Vol_III
WorkstationST GSM 3.0 User Guide GEH-6757
WorkstationST Application Mark V Feature System Guide GEH-6759
ControlST Software Suite How-to Guides GEH-6808
Mark Controllers Shared IONet User Guide GEH-6812
WorkstationST Alarm Viewer Instruction Guide GEI-100620
WorkstationST OPC DA Server Installation Guide GEI-100621
WorkstationST OPC AE Server Instruction Guide GEI-100624
WorkstationST Alarm Server Instruction Guide GEI-100626
WorkstationST Recorder User Guide GEI-100627
WorkstationST Historian Instruction Guide GEI-100628
WorkstationST HMI Configuration User Guide GEI-100629
WorkstationST Web View Instruction Guide GEI-100661
Mark VIe Controller Standard Block Library Instruction Guide GEI-100682
WorkstationST Network Monitor Instruction Guide GEI-100693
WorkstationST Modbus Feature Instruction Guide GEI-100696
WorkstationST / CIMPLICITY Advanced Viewer Integration GEI-100697
WorkstationST Device Manager Gateway Instruction Guide GEI-100757
Trender Instruction Guide GEI-100795
WorkstationST Control System Health Instruction Guide GEI-100834
Indicates a procedure or condition that, if not strictly observed, could result in damage
to or destruction of equipment.
Caution
Attention
This equipment contains a potential hazard of electric shock, burn, or death. Only
personnel who are adequately trained and thoroughly familiar with the equipment
and the instructions should install, operate, or maintain this equipment.
Warning
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.
Always ensure that applicable standards and regulations are followed and only
properly certified equipment is used as a critical component of a safety system. Never
assume that the Human-machine Interface (HMI) or the operator will close a safety
critical control loop.
Warning
Note For the requirements for ToolboxST to run on the HMI, refer to ControlST Software Suite Upgrade Guide (GEI–
100694) the section, HMI Compatibility.
• Windows 7 64-bit
Attention • Loss of connection in the middle of a configuration download from ToolboxST to the
controller
Microsoft has resolved the issue with a Hotfix (KB2588507) for both operating
systems. GE is not able obtain redistribution rights for this Microsoft Hotfix. Users
with large memory ToolboxST system configurations (such as FOUNDATION Fieldbus)
using Windows 7 and Windows Server 2008R2 should download and install the
Microsoft Hot Fix. Refer to Customer Service Bulletin EGD Configuration Server
Ping Failure (CSB25337) for further details.
Note The ControlST Software Suite no longer supports Windows 2000 and Windows XP, and does not support using
CIMPLICITY V8.2 and V9.0 with Windows Server 2012R2.
ToolboxST users with Dell© Precision 5510 mobile workstations with GE Core Load
with a 4K display (Hi DPI) resolution running on Windows 10 64-bit OS will
experience several display issues. To resolve this, upgrade Windows 10 using the
following URL: https://www.microsoft.com/en-us/software-download/windows10. Click
Update Now to download the Windows10Upgrade9252.exe file. (This upgrade will
take approximately 6 hours, followed by 3 or 4 reboots.) After the upgrade, right-click
Attention the ToolboxST icon from the desktop, and select Properties, click the Compatibility
tab, select (check) Override high DPI scaling behavior, then select System
Enhanced. This applies to all supported versions of ControlST running on Windows
10.
Note Contact the nearest GE Sales or Service office, or an authorized GE sales representative for assistance.
• Go To Variable
• Go To Hardware Diagnostic
• Go To Locator
• -NoSplash
• Archive a ToolboxST System
Note If the ToolboxST application is already opened, starting it again with the /variable option sends a message to the
already running ToolboxST application to cause it to navigate to the appropriate location.
Note Using /EGDAction:ADD requires no /EGDDevice identifier. The application started determines the ProducerID(s) and
device names(s) to be used.
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 system file, that system file is used for the variable search.
Otherwise, the first file in the most recently started ToolboxST system is opened.
Example 2
/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 system 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.
-NoSplash
If the text -NoSplash is contained in an argument, the splash screen does not display when the ToolboxST application starts.
Example 3
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 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 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.
Attention
Always install new versions of the ToolboxST application before removing older
versions to preserve your personal settings.
Attention
Do not install ControlST component releases (individual .msi files) without first
installing a full ControlST release. Then, component releases can be installed. You
must install the ControlST Software Suite to properly install the ToolboxST
component.
Attention
1. Place the ControlST Software Suite DVD in the DVD-ROM drive.
2. The ControlST Software Suite Setup Notes dialog box displays. Click Continue.
Note If the installation does not begin automatically, navigate to the DVD-ROM drive and run the installation file setup.
exe.
3. The Setup - ControlST Software Suite dialog box displays the installation options. Select the applicable installation
options and click Install.
CMS-SVN Server and GE HART® Message Server options are typically only installed
on one computer per site. If either of these options is selected, a message displays
asking you to confirm that you want to install the option.
Attention
Note The installation associates .tcw files on a single machine with the ToolboxST Version Selector. This helps determine
the correct version that should be used to open the .tcw file. However, if the most recently installed version is prior to
ControlST V03.03.xx, all .tcw system files are associated with that specific ToolboxST version.
7. From the Custom Setup window, select the features to install or not install. All components are installed by default.
8. Click Next.
9. Click Install.
10. After installation is complete, click Finish.
11. If any other options were selected (such as WorkstationST), a Setup dialog box displays asking if you want to install the
next selected option. Click Yes and repeat the installation procedure for each selected option.
12. When all selected installation options are complete, click Yes to exit setup.
Note Icons for installed applications are automatically placed on your desktop.
Note You can install multiple versions of the ToolboxST application. If a new version is included, the desktop icons and
Start menu update to reflect the most recently installed version.
Note The Alarm Viewer is installed with the WorkstationST application. It can also be installed separately on a remote
computer.
Note If you installed the Configuration Tools Documentation option, the ControlST Documentation application can be
opened from the Start menu.
➢ To uninstall or modify the ToolboxST application: from the Start menu, select Settings, Control Panel, and
Add/Remove Programs, right-click the ToolboxST application version and click Uninstall.
Note If the installation does not begin automatically, navigate to the DVD-ROM drive and run the installation file setup.exe.
2. The ControlST Software Suite Setup Notes dialog box displays. Click Continue.
3. The Setup - ControlST Software Suite dialog box displays the installation options.
8. Click Next.
9. Select the installation location for the GE AcDcEX runtime drive product (included with installation unless selected
to not install in step 7).
10. Click Install.
11. After installation is complete, click Finish.
12. If both Legacy options were selected, a Setup dialog box displays asking if you want to install the next selected option.
Click Yes and repeat this installation procedure for each selected option.
13. When all selected installation options are complete, click Yes to exit setup.
Icons for the installed applications are automatically placed on your desktop.
➢ To open GE Legacy installed applications: from the Start menu, select GE Legacy Support and select the
program.
➢ To display ControlST versions: from the Start menu, select All Programs, GE ControlST, and Versions to
display a complete list.
The ControlST Versions dialog box contains the following tabs:
• Tree View displays all installed products, their versions, the setup used for installation, and the installation date.
• Form View displays complete information for all installed products in a table format that can be copied and pasted into a
spreadsheet.
• DVD Tree View displays a list of products installed from the DVD.
ControlST Versions
Note The ControlST Documentation application can be installed with the ControlST Software Suite. Refer to the section
Installation for further details.
2. From the Search field, enter a document number or a keyword or phrase for which to search and press Enter.
The Search Enhancement dialog box displays a notification that the search capability can be improved by enabling full text
search. Click Yes or No to continue.
From the Search Enhancement dialog box, click Yes to display the
document How to Enable the Adobe PDF Full Text Search for ControlST
Documentation (GHT-200030). Perform the procedures in that document
to enable full text search.
To view this document at any time, click ControlST Documentation Global Search.
Note: To prevent the Search Enhancementdialog box from displaying every time you
perform a search , check the option Do not show again .
• Internal GE search:
− Link to document(s) containing the document number, keyword, or phrase entered in the Search field
− Link to Mark Controller Solutions Support Site
− Link to GE’s Automation & Controls Customer Center Site
• External GE search:
− Link to document(s) containing the document number, keyword, or phrase entered in the Search field
− Link to GE’s Automation & Controls Customer Center Site
3. Click the document link to view the document.
4. Click the website link to open the website and search for additional documentation or information.
➢ To enable full text search: refer to the document ControlST Software Suite How-to Guides (GEH-6808), the chapter
How to Enable the Adobe® PDF Full Text Search for ControlST Documentation.
• Hardware key for Legacy ControlST versions prior to V03.06.09, and from V03.06.09 to V04.07.xx (green or blue USB
Protection Device (UPD) known as a dongle)
• Hardware key for ControlST V05.00 and higher (white M4 )
• Software activation key, Project Advantage license, that is typically assigned to a computer, but can also be assigned to a
USB key
If a user logs in and tries to open the ToolboxST, Trender, and Alarm Viewer application and the number of allowed sessions
is exceeded, the following error message is displayed. Additional sessions can be added by purchasing additional Terminal
Server Connection licenses.
Before you insert the key, install the ToolboxST and/or WorkstationST application. If
you insert the hardware key before installing these applications, the key may appear
to be installed but it is not associated with the correct drivers. This will correct itself
after the application is installed.
Attention
Note The most current licensing installation is available at the following location: http://support.ge-ip.com/licensing.
➢ To install the hardware key: insert the hardware key into an empty USB port on your computer.
Note Only one hardware key of the same type (Keylok, M4) can be installed at a time.
➢ To install and activate the Project Advantage license: enter your activation code (provided by email) in the
Product Lifecycle Management (PLM) Activate License window.
PLM connects to the License Server and performs various checks run by the License Server (valid activation code, license
already assigned, and so forth).
Note Additional information and troubleshooting for Advantage software license activation is available at GE Automation &
Controls Support website.
➢ To open the License Client (Manager/Viewer): from the Start menu, select All Programs, Proficy Common,
and License Client (Manager/Viewer).
License Client/Viewer/Manager
Enter a name for the new system. Some characters are prohibited ; if you enter a valid
character, a small red exclamation mark displays .
Specify the working directory to contain the ToolboxST system. Either enter a Location
path or click Browse to navigate to a file location.
Note: If you enter a path that does not exist, the ToolboxST application creates it for you.
Note Refer to the section System Configuration Files for more information.
• Tree View
• Property Editor
• Summary View
• Component InfoView
Property Editor
allows you to
configure all
system
properties when
the system is
selected in the
Tree View.
Component
properties are
configured in the
specific
Component
Editor
Component InfoView
displays specific system
feedback information
ToolboxST System with Configured Components
➢ To view Alarm Help: from the Alarm Viewer, right-click an alarm and select Alarm Help to display the Operator
Guidance window. For more information, refer to the WorkstationST Alarm Viewer Instruction Guide (GEI-100620).
Note Alarm help files are published when the device containing the alarm changes is saved. The Log tab in ToolboxST
indicates when publishing is complete.
Password protection can also be set for individual components to restrict certain functions and property modifications. For
further details, refer to the section Password Protection for your component.
To change the password, refer to the section System Component Password Change.
➢ To edit system components: from either the Tree View or Summary View, double-click the system component to
open the Component Editor.
Note You can add components to the root component of a system or group. Some components display a wizard or window
that prompts you for additional information when you add them to the system.
System
Group of Components
WorkstationST application
Printer
Library Container
Network
Trender
Watch Window
LiveView
CMS Administrator
ControlST Documentation
Mark V component
Note 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.
• 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 two exceptions:
• When a group is copied, a new Group is created. The contents of the previous Group remain in place and are not copied
to the new Group.
• The drag-and-drop feature is not 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 the drag-and-drop feature. (To import from the file system, drag the Device.xml or Library.xml
file that represents the component.)
➢ To display system properties: from the Tree View, select a system item to display the system properties in the
Property Editor.
System Properties
Note This property only applies to Mark VIe and Mark VIeS secure systems.
Bob
Bob
• Trender
• WorkstationST Alarm Viewer
• WorkstationST Status Monitor
Note Refer to the chapter, WorkstationST — Working Online, the section, WorkstationST Status Monitor. For further details,
refer to the WorkstationST Alarm Viewer Instruction Guide (GEI-100620) and the Trender Instruction Guide (GEI-100795).
Note Pre-defined theme files are provided in the installation directory (Program Files\GEEnergy\ThemeFiles).
4. Click Save. It will take up to two minutes for the changes to be implemented.
Examples of the operator-facing tools enabled with the selected theme GE GrayScale are provided in the following table. To
use a standard Windows display style, leave the Theme File property empty.
Trender
WorkstationST
Alarm Viewer
WorkstationST
Status Monitor
Attention
The ToolboxST system provides a Batch command to allow you to select multiple controllers and perform the Instance All or
Build commands.
Right-click the
system item and
select Insert New,
Tool , and Batch
Commands
From the
Component
drop-down list,
select the
component and
click to enable.
From the On
Error drop-down
list, select the
action to take
(Stop, Continue
(skip to), or Next
Component))
when the first
error occurs.
Status Icons
Icon Status Indicates
Component Diagnostics – No
NTP Diagnostics – No
EGD Diagnostics – No
I/O Diagnostics – No
Healthy
Number of Forced Variables – 0
DDR Equality – Equal
Configuration Equality - Equal
Network Status Monitor - Healthy
NTP Diagnostics – No
EGD Diagnostics – No
I/O Diagnostics – No
Unhealthy Number of Forced Variables – 0
DDR Equality – Equal
Configuration Equality – Major difference
Network Status Monitor - UDH has errors
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
Warning measures should be strictly enforced in conjunction with this procedure.
Note It is possible to scan and perform configuration downloads to multiple controllers simultaneously.
After a Build has been performed on all components, the scan takes place. The scan allows the ToolboxST application to
obtain each component’s version status of the base load, the firmware, and the application code and parameters.
The application displays a message if any components selected for download have any conditions (for example, issues with
firmware or application code) that could cause them to be in an inappropriate download state.
When the scan is complete and you are prompted to generate a scan report, click Yes.
The scan report displays any controllers that are Not Equal.
➢ To start the scan download: from the wizard window, click Next.
Download Completed
The user must change the factory default password. The maximum number of
characters for the new password is limited to 8 characters. The new password cannot
be the factory default password. If you do not know the factory default password,
contact the nearest GE Sales or Service Office, or an authorized GE Sales
Attention Representative.
Note For a component configured with redundant controllers, the password applies to all controllers in that component.
Note This password is required to configure the network address during controller setup.
2. A message displays asking you to confirm that you fully understand the effects of the changes to the control constants
values in the controller(s) to the controller(s). Click OK to proceed.
3. Click Browse… and select the .csv file to import. Use the following .csv file format:
4. Click one of the import options:
• Import to Device Values modifies the values in the device only, which results in a faster load.
5. A message indicates when the import is finished in the lower left corner of the window and a report log is available to
view. Click View Log to view a report of the import details.
2. Select the device(s) to export the associated control constants and parameters.
3. Click Browse... to select the location for the export file.
4. Click Begin Export to export the control constants and parameters of the selected device(s).
5. When the export is complete, click View Log to review the results.
Note The Entry High Limit and Entry Low Limit values are imported and exported with the live values for control constants
and parameters.
Note If all configured components have been upgraded to the latest installed version, the System Upgrade Wizard window
displays the message No components require upgrade.
All component editors must be closed to perform an upgrade from the system.
It is recommended that users back up the ToolboxST .tcw file prior to upgrading the
system.
Attention
1. Check for available upgrades.
Note The latest version for components is displayed by default and the I/O module versions default to the latest compatible
hardware.
2. Select the components for upgrade. By default, components are listed by Component Name but you have the option to
list by component hardware type as well.
The New Version column displays the version to which the component will be upgraded.
Select Upgrade for the appropriate component(s), then click Next to proceed.
Upgrading the component to the new incompatible version will require replacing
existing I/O modules with supported hardware.
Attention
Place your cursor on the Caution icon to display a Tool Tip indicating that the selected
upgrade version does not support the existing I/O module hardware and if you proceed
with the upgrade you will have to replace the existing hardware.
Note Selecting No does not cancel the upgrade. You must unselect the incompatible component(s) if you want to
proceed with the upgrade for other compatible components.
Tip � Place your cursor on the component name to display a Tool Tip listing all controllers that contain the I/O module
selected for upgrade.
If Hardware Type was selected and any I/O modules cannot be upgraded due incompatible hardware, the Hardware
Mismatch dialog box displays notifying the user that the incompatible I/O module hardware cannot be listed by Hardware
Type.
➢ To instance components
From the
System menu,
select Instance
Components to
display the
Select Devices
dialog box
Select
individual
components
or click
Select All
and OK
Information
and progress
for both the
Instance and
Build
commands
display
• Simple Replicate — the name and IP addresses for the duplicate components are automatically assigned in linear order
from a base value
• Replicate using Properties from CSV — the name, IP addresses, and group for the duplicate components are read from a
Comma Separated Value (.csv) file. Since the name and IP address of each component can be specified, this command is
more flexible than the Simple Replicate.
Note The Replication Wizard cannot replicate a component with validation errors. If a validation error message displays
when Simple Replicate is selected, perform the Build command.
Note Any component name or IP address conflicts display in red in the Status column.
Note If the component cannot be replicated, the replicate commands are unavailable.
1. From the Tree View, right-click a component and select Export Component Properties from CSV.
2. Select a name for the .csv file.
3. Using Notepad or Microsoft Excel®, edit the .csv file.
Each line represents one component to create during replication, and each column defines a component property:
Note All existing Trenders and Watch Windows in system components are replicated, as well.
Attention
The Create System Wizard allows you to create a new system from selected components of an EGD configuration server or
SDB server. If a selected component supports uploading the configuration, an attempt is made to perform the upload. If
Upload is not supported or the upload fails, a component of the correct type is created in the system based on the information
in the EGD configuration server.
Note The new system will not be an exact copy of the original. Not all information required to create a system is available
from the EGD configuration server or SDB, including libraries. The new system will have the default NTP settings; however,
this may not reflect what is configured in the original system.
Note If the system is already open, it will be closed before the wizard starts.
Select the
check boxes
for the desired
components
and click OK.
Attention
Alarm Shelving allows the operator to temporarily suppress Alarms from the Alarm Viewer live Alarm data display, and from
HMI screens that display Alarms. The Out-of-Service feature allows the operator to place an Alarm in the out-of-service state
or to return the Alarm back to in-service. The Alarm Shelving property is enabled in the System Editor. Alarm Shelving and
the Out-of-service feature apply to Process Alarms only.
Attention
In conjunction with the Alarm \Shelving feature and the ANALOG_ALARM and BOOLEAN_ALARM blocks,
Condition-based Unshelving allows you to create the Unshelve sub-variable.
Select the
analog variable.
Shelved variable
attached as input pin
The Unshelve sub-variable
also displays in the Block
Diagram Editor.
Sub-variables Properties
display
Copy I/O
This feature is available with either Mark VIe Wind turbines or MarkStat Wind
DFIG controllers.
Attention
It is possible to copy all parameters and connections for I/O packs in a controller to other controllers at the system level.
When the
welcome page
displays, click
Next.
Note Ports configured with the connection type Default_Native Device Connection or not used can have a network
component connection.
➢ To add a network component connection to a port: from either the Data Grid or the Property Editor, click the
ellipsis button next to the Network Component property.
Select a
component
and click OK
➢ To save changes to the current system: from the File menu, select Save System.
This feature is not available for Mark VIeS Safety Control systems.
Attention
When changes to the system or to an individual component are saved, you are given an option to view your changes.
This feature is not available for Mark VIeS Safety Control systems.
Attention
The optional Control Data Highway (CDH) is a second Unit Data Highway (UDH) that allows two separate controllers to
communicate with each other. There are two ways to configure a CDH. In a standard network configuration, the CDH is
configured in the same manner as a UDH. Each controller core in the two controller sets is connected directly to a network
switch. EGD exchanges are transmitted by whichever controller is designated as the CDH communicator.
In a direct connect network configuration, the CDH is configured with a single wire connection between the two R, S, and T
controller cores. This method is only possible if the following criteria is met:
To avoid voter mismatches, the ToolboxST application issues a Build warning for dual
or TMR redundancies when it detects EGD exchanges on the CDH being transmitted
at a rate other than frame rate unless it determines that network switches have been
configured for the CDH.
Warning
For Transport,
select IP
Enter a page
name and
click OK
The EGD Page cannot be configured to transmit on more than one Ethernet network
(UDH and CDH) on this component. Only one Ethernet platform should be enabled
(True). If both are enabled, ToolboxST displays an error message.
Attention
➢ To add variables
• 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)
• Block Diagrams, a folder containing the diagrams for user blocks defined in each library
The .xml files used by the ToolboxST application should NEVER be modified by ANY
other application.
Caution
Configuration files can be both compressed and encrypted. 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.
Note The ToolboxST application cannot open a configuration file saved in a newer ToolboxST version.
Multiple ToolboxST versions can be used on a system (for example, during an upgrade), and upgrading the configuration files
is undesirable. To help prevent accidental upgrades to configuration files, you are warned if saving the file will prevent older
ToolboxST versions from opening the file.
When you are saving a system that causes a version upgrade, you are asked if you wish to continue (a backup of the original
system is created, as well).
Note This feature is enabled from the System Property Editor. For further details, refer to the section System Properties.
When opening a system in a newer ToolboxST version, the following prompt may display. Click Yes for the .tcw file to be
written in a format compatible with the ToolboxST version that last saved the system. Individual components will continue to
be saved in the newer version.
• Systems saved by ToolboxST versions prior to V04.04.11C cannot enable the Maintain Backward Compatibility property
• Certain features added to the system may require the newer file format. If you attempt to use one of these features, a
message displays to ask if you wish to proceed.
Click Cancel to cancel the change. Click OK to save the change and upgrade the system to the current ToolboxST version.
Note Refer to WorkstationST Alarm Viewer Instruction Guide (GEI-100620) for more information about viewing language
options.
➢ To view system options: from the Options menu, select Settings to display the Settings window.
➢ To open the System Information Editor: from the System Editor Edit menu, select System Information.
System
Information
Editor Tree
View
This feature is not available for Mark VIeS Safety Control systems.
Attention
Alarm Block Templates are used in conjunction with the ANALOG_ALARM block in certain controller configurations. The
ANALOG_ALARM block provides Analog Alarm documentation defined in application code; it also allows automatic
configuration of the Alias properties of each Alarm associated with the Analog Alarm.
Note For further details on these blocks, refer to the Mark VIe Controller Standard Block Library Instruction Guide
(GEI-100682).
Enter a name
for the template
and click OK
➢ To edit Alarm Classes: from the System Information Editor Tree View, select Classes.
A data grid with the existing Alarm Classes displays in the Summary View.
Note When colors are selected, unnamed colors may display in the Data Grid as RGB codes.
3.9.2 Sounds
Use the System Information Editor to define options that annunciate certain sounds within the Alarm Viewer. A specific
sound definition is assigned to an alarm class.
➢ To edit sounds: from the Tree View, select Sounds to edit the configured sounds in the Summary View.
The following table lists the available properties when a sound is selected in the Data Grid.
Sound Properties
Property Description
Time lapse between sounds (from 100 to 10,000 ms). The Repeat Quantity property must be 1 or
Delay
more
Duration Sound’s duration (from 100 to 10,000 ms)
Frequency Sound’s frequency (range is 100 to 500 Hz)
Name Sound’s name
Repeat Quantity Number of times the sound is repeated
Sound Type Type of sound annunciated; options are Tone, Wave File, and Text to Speech
If selected as the Sound Type, displays the name of the Wave File. When the system information is
Wave File
saved, the wave files are published to the Master WorkstationST computer
A second language must be selected from the System Editor Property Editor before
using this feature or it will not function properly.
Attention
➢ To export all diagnostics to a .csv file
1. Verify that a second language has been configured in the System Editor Property Editor.
2. From the System Editor Tree View, double-click the system item. The System Information Editor displays.
3.
3. Right-click
Diagnostic
Translations
and select
Export Product
Diagnostics .
Note The Export Product Diagnostics option creates an All_Product_Diagnostic Translations.csv file that contains
diagnostics for all I/O packs installed on this computer. It can be opened with Notepad or an .xml spreadsheet.
4. From the Tree View, right-click Diagnostic Translations and select Import Diagnostics. Select the .csv file just
created.
5. Expand the Diagnostic Translations item to display each individual system component, including diagnostics
grouped as Common. Diagnostics text can be translated in either the .csv file or the System Information Editor.
6. Select a component to display the message text containing the Second Language column with empty text.
Note Selecting the Diagnostic Translations item exports all I/O pack items within to a single .csv file. However, if an
individual I/O pack is selected, the diagnostics for that I/O pack only are exported.
5. Open the Component Editor for each device in the system that had translated diagnostics, and click Save. This adds the
second language descriptions to the controllers/devices in a running system.
Note Any errors or warnings that occur during validation display in the Component InfoView. Double-click an error or
warning to be connected to that diagnostic.
The Validation command 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 runtime.
Note The text displays in English if there is no Second Language translation for a particular diagnostic.
Note This command only deletes the selected translation records. If a diagnostic occurs and its translation record was
deleted, it still displays in English.
Note If the configuration in the ToolboxST application is equal to the configuration running on the controller, the new
information is published to the EGD configuration 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 downloaded for the changes to take effect.
From the
WorkstationST
component
General tab,
select General
Or
Note When you select Use Second Language from Regional Settings, that becomes your permanent default setting,
regardless of what is configured in the ToolboxST application.
The Alarm Viewer provides a means to override this setting. For more information, refer to ControlST Software Suite How-to
Guides (GEH-6808), the section, How to Configure a Second Language for ControlST HMI Applications.
The option Select Active Measurement System allows you to specify either English or metric measurements. Refer to
ControlST Software Suite How-to Guides, the section, How to Define a Measurement System for Use by ControlST HMI
Applications.
Using this formula, a conversion from Celsius to Fahrenheit would be calculated by the HMI as follows:
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 add format specifications to a Format Specification Set: from the Tree View, select a Format
Specification Set .
A grid of format specifications displays in the Summary View.
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 add device names and descriptions: from the Tree View, select the HMI Resources item.
• Adding and deleting screen files (from the System Information Editor only)
• Defining use of screen files by HMI WorkstationST components
• Editing screen files (from the System .tcw location or the master location if CMS is not enabled)
• Downloading screen files from master location to HMI WorkstationST components
Note It is recommended that HMI screen files be managed from the System Information Editor, although they can also be
managed from the WorkstationST components.
Master
location
path
System File location is the HMIScreens folder in the same location as the .tcw file.
HMI WorkstationST location is the path defined in the HMI Config tab in the WorkstationST application.
Access the HMI screen files from the System Information Editor.
➢ To view HMI screen files: from the System Information Editor Tree View, select HMI Screens to display HMI
WorkstationST components and HMI screen files in the Summary View.
Note When CMS is enabled, the system must be checked out to add screens.
1. From the System Information Editor Tree View, right-click HMI Screens (or any item under it or in the
Summary View) and select Add HMI screen file to display a Select a Folder window.
2. Add a folder name, if desired. This folder will be located within the HMIScreens folder at the system .tcw location.
Otherwise, click OK and the screen file will be added to the HMIScreens root folder.
3. Browse to and select the screen file or files you wish to add and click Open. The screen file is added to the system file
location.
Note If a WorkstationST component is configured for automatic download, a manual download cannot be performed.
When pre-configured for automatic download, the WorkstationST application periodically compares the date of the file in the
Master location to the date of the file in the WorkstationST location. When an HMI screen file is saved to the Master location,
its date changes. The component detects the change and automatically copies the new file to the WorkstationST HMI screens
folder. HMI screen files can be downloaded to an HMI WorkstationST component without checking out the system or
individual HMI screens from the Configuration Management System (CMS).
➢ To manually download HMI screen files from the Master location to the designated HMI WorkstationST
components
1. From the System Information Editor Tree View, select HMI Screens or HMI WorkstationSTs.
2. From the Summary View, select one or more HMI screen files.
3. From the Summary View, right-click to select Download selected HMI screens.
Note Any screens selected for download that are not configured to be used on the WorkstationST component will not be
downloaded.
When not pre-configured for automatic download, the WorkstationST application compares the local HMI screen dates with
the Master during a build of the WorkstationST component. An option to download the mismatched screens is then presented
to the user when the WorkstationST component is downloaded.
Note The process of editing an HMI screen file is different, depending on whether CMS is enabled.
• From the System Information Editor, right-click the file to be edited and check it out by selecting CMS and
CheckOut. The checked-out status displays.
• Right-click the screen file again and select Edit. The file opens in CimEdit for editing.
• Save the edits and close the file.
• Right-click the file and check it in by selecting CMS and CheckIn to update the file in the System .tcw location.
• A message displays asking if you wish to publish the changes to the Master. Typically, you will click OK. This updates
the screen file in the Master location.
Note The edit window displayed depends on the state of both the Master file and your system file.
The source of these HMI screen files is the System .tcw location. When CMS is disabled, the Check Out function copies the
file from the System .tcw location to the computer where the editing is taking place. The file is then checked back in to the
System .tcw location.
There are three possible states, as follows:
Note To ensure that the latest screens from the Master are included in the archive, perform the Copy Master to Local
function before the archive function.
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\abcSystem
\abcSystem.tcw. The HMI screen files are located at C:\site\abcSystem\HMIScreens. This is the System .tcw location of the
HMI screen Files.
Note If files already exist in the Master location when copying from the system, a warning dialog displays to ask if you wish
to overwrite the existing files.
Note The Copy Local to Master is not typically required except when setting up a system or the Master WorkstationST
component for the first time. The Copy Master to Local is required prior to performing a system archive to ensure that the
latest screens from the Master have been copied to the System .tcw location before creating the archive.
Note Although User names must match Windows logon names, Role names do not have to match.
The following table lists the User and Roles properties available in the Property Editor.
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
Warning measures should be strictly enforced in conjunction with this procedure.
A Group name can also be specified here, by prepending the name with an at @ sign. Groups
Name can either be locally defined on the PC or come from a domain. Some limitations apply, such as
local groups that reference domain groups cannot be used. However, local groups can contain
domain users. For example, a group name of @SITEDOMAIN\Operators will allow all users in
that Domain group to log on and be granted the Role and HMI Resources assigned to that entry
in the User list.
Role Defines the user’s access privileges
Associated with a User
Users are configured in the System Information Editor and can be assigned to variables. Users
who have a resource that matches a variable’s resource can write to live data for that variable if
HMI Resources the privilege is assigned. If a variable does not have a resource, it defaults to allow the user to
modify the data if the user’s role supports that privilege. Users with an empty list of resources
are only allowed to modify variables without an Human-machine Interface (HMI) resource
defined. Refer to the section HMI Resources.
Role Settings
Role Name User name and privileges
Alarm Privilege Allows you to acknowledge and reset Alarms in the Alarm Viewer
Alarm Service Privilege Allows you to place Alarms as out-of-service from the Alarm Viewer
Allows you to shelve or unshelve one or more Alarms in the Alarm Viewer. Refer to the section
Alarm Shelving Privilege
Alarm Shelving.
Download Privilege Allows you to download to a controller
Go To Definition From HMI Allows you to right-click within an HMI graphics window and go to the definition in the ToolboxST
Graphics Privilege controller logic
Live Data Force Privilege Allows you to force live values
Allows you to modify live values
The Live Data Modify Privilege must be set to True for the Live Data Force Privilege to be
Live Data Modify Privilege
enabled, and to remain enabled. If the Live Data Modify Privilege is changed to False, the Live
Data Force Privilege will automatically default to False.
Tag Out Privilege Allows you to lock out control functions on the HMI
Allows you to use the WorkstationST Status Monitor to start and/or stop WorkstationST
Start/Stop WorkstationST
features. This privilege also allows you to start or stop features from the Status tab when the
Features
component in online.
This feature is not available for Mark VIeS Safety Control systems.
Attention
The ToolboxST application can interface with a System Database (SDB) from the System Editor.
Note The ToolboxST application uses the EGD configuration server if it has been enabled in the System Editor.
An issue in the Windows operating system handling of 32-bit application addresses has
been identified in large (~2 GB) ToolboxST system configurations on two platforms:
• 64-bit Windows 7
Microsoft has resolved the issue with a Hotfix (KB2588507) for both operating
systems. GE Automation & Controls is not able obtain redistribution rights for this
Microsoft Hotfix. Users with large memory ToolboxST system configurations (such as
FOUNDATION Fieldbus) using Windows 7 and Windows Server 2008 R2 should
download and install the Microsoft Hot Fix. For more information refer to Customer
Service Bulletin (CSB25337) EGD Configuration Server Ping Failure.
➢ To compare the local EGD configuration to the server configuration: from the System Editor View menu,
select EGD Configuration Server, then select View Differences.
OR right-click the status bar shortcut menu and select View Differences.
The Local Configuration Compare to Server Configuration window displays the comparison results between the local EGD
configuration files and the EGD configuration server files.
Note Publishes to the EGD Configuration server occur when a component is saved. If a component in a .tcw file is not the
latest configuration (for example, if the most current configuration is on another computer), publishing the local EGD
configuration sends the old configuration to the server.
• The Search text box allows the user to filter the display for the entered criteria.
• Color coding represents differences and missing documents:
− Salmon color indicates documents that are missing from the configuration server
− Green/gray color indicates rows containing differences
• The toolbar above the grid provides two icons:
− Select the Toggle icon to only display the documents that do not match in the table.
− Select the Help icon to display a diagram that illustrates the dataflow of configuration documents between tools
(Configuration Server and WorkstationST).
Missing
Different
Note The CMS Status column displays information only if the user is currently logged into CMS and the ToolboxST system
is under CMS control.
1. If the external device does not already exist as a ToolboxST component, create an External Device component to
represent it.
2. Select the external device in the System Editor Tree View. The component properties display in the Property
Editor.
3. Set the Enable Get from SDB property to True.
4. From the Tree View, right-click the external device and select Get EGD from SDB. A window displays the destination
SDB Host and Path.
5. Click OK to proceed with the Get EGD from SDB operation. When it is complete, the results display on the Log tab of
the Component InfoView.
Note If the EGD configuration server is enabled for the system, the EGD configuration will also be put to the EGD
configuration server.
Note Refer to the specific Mark control platform section Report Features for further details.
Note The Privileges features is accessible from the WorkstationST application or WorkstationST Status Monitor icon in the
taskbar notification area.
The following figure illustrates how the ToolboxST application, CimView, and CimEdit authenticate system access using the
Privileges feature.
! +
!
),-
+ + ./0
)
)' )
./0
)
Note Privileges can only be modified from the System Information Editor.
Note An event message indicating the logged-on user (and role) is generated in the Alarm Viewer.
➢ To replace the current user: right-click the WorkstationST Status Monitor icon and select Privileges Log On.
The user selected (with defined privileges) replaces the current user.
The user maint is now logged on over the current user (now sub-user). The previously defined user privileges for maint take
effect.
Note An event message indicating that the user logged off is generated in the Alarm Viewer.
➢ To set the Auto LogOff Timeout: from the System Editor Tree View, double-click the system item to display the
System Information Editor.
From the
Property Editor,
enter the Auto
Logoff Timeout
in minutes.
If the temporary user remains inactive through the timeout period, that user is logged off and message displays that the user
administrator is again active.
➢ To log off the Current User: right-click the WorkstationST Status Monitor icon and select Privileges Log Off.
The current user is now logged off. If the current user was the temporary user, the sub-user now becomes the current user and
previously defined user privileges now apply.
Note Only users with roles assigned to a protected object can access that object.
By default, when a role is assigned to an access right, only users with that role can access the protected object (programs,
tasks, and such). Permissions are also inherited from parent objects. For example, if a component has the Modify Design role
assigned to Operator, all objects in that component require the Operator role before allowing design changes. However, each
Role name can optionally be applied with the Grant keyword. This reverses the normal behavior so that users with the Grant
keyword have access to the object regardless of any parent objects. As an example, the Modify Design access could be
restricted for an entire component to users with the Maintenance role, but one particular program could be modifiable by
users with the Operator role.
Note The Shared IONet feature is not available for the UCPA controller.
Beginning with ControlST* V04.06, sharing data between two control sets on a single Ethernet input/output network (IONet)
is available for some Mark* controllers. The owner controller allows for the configuration of the owned I/O modules, writes
outputs, reads SOEs, and provides diagnostic information. Owned I/O modules are attached to their owner controller that can
configure and write to them, and obtain their IP addresses from their owner controller. Outputs from controllers are received
by their owned I/O modules (not shared I/O modules).
Note A control set is the group of controllers (based on redundancy) with the set of owned I/O modules. From the
ToolboxST* System Editor Summary View, a control set displays as a single controller.
A shared I/O module sends field device inputs to both its owner controller and to the consumer controller. The consumer
controller receives the field device inputs from the shared I/O modules that are owned by the other owner controller.
Configuration of the control sets is managed with the ToolboxST application. The computer with the ToolboxST application
communicates with the I/O devices through a software gateway function residing in the controllers. Refer to Mark Controllers
Shared IONet User Guide (GEH-6812) for further details.
The following controller combinations are able to exist on the same IONet:
• One Mark VIeS Safety controller and one Mark VIe controller
• One Mark VIe controller and one MarkStat controller
• Two Mark VIe controllers
3. If inserting a new controller, from the Tree View, right-click the Shared IONet group and select Insert New,
Controller, and Mark [VIe, VIeS, or Stat] Controller.
a. Complete the Creation Wizard pages to add the controller.
b. If inserting a new second controller, repeat these steps.
Or
b. Delete the controllers from inside the group.
2. Select and delete the group folder.
3. Restart the WorkstationST* OPC DA server to refresh the I/O diagnostics as displayed from the system-level controller.
If the server is not restarted, active diagnostics may not display from the system level.
When attempting to delete the Shared IONet group without first removing the controllers, the following message displays.
2. A Download Shared IONet System wizard displays. Notice that the check boxes for the individual controllers
cannot be cleared.
3. Complete the wizard screens to build and download to the Shared IONet Group.
Note For further details, refer to Mark VIe and Mark VIeS Controllers Shared IONet Instruction Guide (GEH-6812).
Master
UCPA No No No No Simplex only No (PSCA),
Slave
Master
Simplex,
UCSA Yes Yes No Yes Yes (PSCA),
Dual, TMR
Slave
Simplex, Master
UCSB Yes Yes Yes Yes Dual, Yes (PSCA),
TMR Slave
Simplex, Master
Yes
UCSC Yes Yes Yes Dual, Yes (PSCA),
Restore only
TMR Slave
† Refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose Applications System Manual (GEH-6721_Vol_II), the
sections UCSC Restore and UCSB Backup and Restore for these procedures.
Simplex,
Slave
UCSB Yes No Yes Yes Dual, No
(Read Only)
TMR
Simplex,
Yes Slave
UCSC Yes No Yes Dual, No
Restore only (Read Only)
TMR
† Refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose Applications System Manual (GEH-6721_Vol_II), the
sections UCSC Restore and UCSB Backup and Restore for these procedures.
Yes
UCSC No No Yes Simplex only No No
Restore only
† Refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose Applications System Manual (GEH-6721_Vol_II), the
sections UCSC Restore and UCSB Backup and Restore for these procedures.
† Refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose Applications System Manual (GEH-6721_Vol_II), the
sections UCSC Restore and UCSB Backup and Restore for these procedures.
† Refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose Applications System Manual (GEH-6721_Vol_II), the
sections UCSC Restore and UCSB Backup and Restore for these procedures.
Master (PSCA),
UCSA Yes Yes No Yes Simplex Yes
Slave
† Refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose Applications System Manual (GEH-6721_Vol_II), the
sections UCSC Restore and UCSB Backup and Restore for these procedures.
Attention
There are two system components for creating downloadable application software, controllers, and Library Containers.
Controller components contain the software that is downloaded to a particular controller. Library containers contain user
block libraries of reusable blocks that can be referenced and used by controller components.
Controller software consists of function blocks that perform logical and mathematical operations on the block variables. This
network of blocks and connected variables controls a particular machine through physical inputs and outputs.
Function blocks arranged and connected within a software element are called tasks. Tasks are grouped into other software
elements called programs. For more information, refer to the section Software Tab.
User-defined blocks called user blocks are created using existing function blocks, as well as other user blocks. User blocks
can be used in a task in the same manner as function blocks.
Note A variable Alias report can be generated for a list of all variables with aliases.
Instance
If a library definition is changed, programs, tasks, or user blocks associated with the definition are NOT automatically
updated. This is true within a Library Container as well as in a controller component.
The process of updating programs, tasks, or user blocks with current library definitions is called instancing.
➢ To instance a single item: from the Software tab Tree View, right-click a program and select Instance to update
all software within that program.
➢ To instance an entire system component: from the Software tab Tree View, right-click Programs and select
Instance All.
Definitions can contain user blocks or tasks that were created from other definitions in a library. To be certain that all current
definitions have propagated to all necessary places in a controller component:
• From the Library Container, perform the Instance All and Save commands.
• From the controller component, perform the Instance All command.
Note Programs, tasks, and user blocks that do not come from a library definition are called Embedded, and they do not have
the Unlinked property.
Note An alternative method is to insert an embedded user block, then drag the linked user block from the library palette onto
the block diagram for that embedded user block.
Validate checks the configuration Summary View is used Library View contains
for errors, connection compatibility, to edit the user block categories of blocks that
data types, and equations selected in the Tree View perform various functions
Tree View
displays all
items in the
editor. Add or
delete libraries
here
Property
Editor displays
properties for
the item
selected in the
Tree View
Component
InfoView
displays
information
whenever an
action occurs
It is highly discouraged that systems contain multiple libraries or objects with the
same name for the following reasons:
• Duplicate named libraries – Even though a system can contain multiple libraries
with the same name, a Library Container or device can only reference one of these
libraries. Therefore, if the libraries have a different subset of objects the system will
not be able to access all of the objects in both libraries.
• Duplicate named objects – Even though a system can contain multiple objects with
Caution the same name, an unexpected instancing operation can occur if a device or Library
Container references more than one of these objects. This could also lead to confusion
for future users who may not be intimately involved in the system design. If a user
designs a system in this manner it is their responsibility to test and understand the
instancing operation and convey that information to all system users.
Tip � Different versions of the controller component can be used as the basis for a library component. A software block
library is always included that contains basic function blocks, such as Move and Average. There are also optional libraries,
which contain more specialized blocks that can be included in the Library Container.
When new versions of the controller software are installed, Library Containers continue to use their current configuration
until they are upgraded. (If the old version is uninstalled, the Library Container must be upgraded before it can be opened.)
From the System Editor Tree View, double-click the Library Container.
From the Libraries menu , select Add Library or Add Existing Library.
Tip � The Summary View Libraries item displays names and locations of all function blocks and user block libraries defined
in the Library Container. The function block library version used by the Library Container can be determined by looking at
the Directory field and observing the path to the library.
Library containers and devices should have a reference to all top-level and nested
linked objects. Failure to do this may cause the Instancing and Update All Uses
features to generate errors due to not being able to update all selected objects. This
results in the following error message displayed in the Log window: The block [user
Attention block 1] is not found in block library assembly.
Note The Go to Definition and Compare to Definition features will not work for any object that does not contain a reference
to the source object.
Devices and Library Containers must have library references to the source code of all
linked objects for the Go to Definition and Compare to Definition features to operate. If
no library reference exists for an object these functions will not be displayed in the
right-click menu.
Attention
Note If the user performs an Instance All operation the system updates all nested link contents from their source code if they
are defined within the Library Container. However, nested links that were defined in referenced libraries are updated here
with an exact copy as they exist in that reference library. The reference library content is not updated by the Instance All
operation.
Instancing behaves differently from Instance All in that if the user performs an Instance operation the system updates all
nested link contents from their source even is the source is referenced from another library.
Property Description
Description Description for this library
Name Unique name for this library
Access Roles are assigned to users to protect each access right for the object.
Modify Data allows you to modify data values and forcing of variables.
Protection
Modify Design allows you to modify the design of defined blocks in this library.
View Design allows you to view details of defined blocks in this library.
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
Warning measures should be strictly enforced in conjunction with this procedure.
• Block3.mht
• Block4.htm
The ToolboxST application first searches for a .chm file that corresponds to the Library name. If this is not found, it searches
in the HelpFiles directory for a help file that matches the block name. The search order is:
• .mht
• .htm
• .txt
Note If passwords were set in the Property Editor for this library, the following functions require a password.
The Data Grid displays the differences and allows you to edit the table data values in the controller. Once the table data values
are correct, click the Save to Initial Values button to capture the values in the ToolboxST configuration.
From the System Editor Tree View, double-click the Library Container.
User block definitions can be sorted alphabetically. If additional user block definitions are added, repeat the sort.
➢ To sort user block definitions: from the Tree View, right-click the library item and select Sort Definitions.
• Add Variable allows a variable to be added to the selected User Block. Once the new variable is added, properties
become available in the Data Grid.
• Add Undefined Variables allows you to add all undefined variables in the User Block Definition to the variables of
the User Block Definition. Undefined variables are ones that have been referenced in a User Block Definition but have
not yet been defined as part of user block variables or user block.
3. Select the Attributes item in the Tree View to display modifiable properties in the Data Grid.
➢ To add an Instance Script: from the Tree View, right-click the user block definition and select Add Instance
Script.
4.2.14.2 Instance
Select this command to get a new copy of the user block definition from the library. In addition to updating the user blocks,
this command causes the instance scripts and text substitutions for all top-level user blocks to run. It is not possible to undo
this command.
➢ To instance a User Block Definition: from the Tree View, right-click the user block definition and select Instance.
4.2.14.3 Validate
This command checks the selected user block definition for errors. Validate also checks connection compatibility, data types,
and equations. Validation status displays in the Log tab. Double-click the error in the Log tab to locate the software that
caused the problem.
➢ To check a User Block Definition for errors: from the Tree View, right-click the user block definition and select
Validate.
Note Changes in user block definitions (as well as in task and program definitions) can be pushed (update all uses) directly
from one library to other libraries and to the controllers as opposed to changes being pulled (Instanced) from the library from
individual libraries or controllers.
Note The Enter Password dialog box displays if this action is password-protected.
Click Yes .
Note When Update All Uses is selected, you are prompted to save changes if changes have not been saved. Once changes
are saved, the Controllers and Libraries to Update dialog box displays.
Note A Library Container/controller with an OK status is the only one that can be updated. Users can only select a Library
Container when the OK to Push To status is OK.
The following Warning dialog box displays to remind users that any open Library Containers or controllers will not be
updated.
Click Yes .
The search results display in the Find Results tab of the Component InfoView.
The system notifies the user in the search results of unlinked objects and duplicate names.
Note In some locations, including Reports and the Block Diagram Editor, shortcut menus contain commands that allow
single pages or reports to be printed.
Prints a
summary of Page Numbering
configuration controls page
settings number
assignment
Includes a list
of sections Linear pages
with page number
numbers sequentially
Includes a starting with page 1
quick
reference Hierarchical
symbol guide pages include
sections and
Prints all subsections (1, 1.1,
component and such)
programs
4. Right-click Programs again and select Add Program. Complete the Add Program dialog box and click OK.
5. From the Tree View, right-click Prog1 and select Add Task. Complete the Add Task dialog box and click OK.
6. Save the changes and close the editor.
4. Click in the Value cell for attr1, then click the ellipsis button (...) to display the Modify Value dialog box.
Name of the
attribute
being
modified
If selected, the
attribute values
are restricted to
an enumeration
(a predefined
set of allowable
values).
Right-click the
MOVE_2 block
and select Add
Instance Script
4. Change the attribute name to Attr1_u and click OK. A new Attributes item displays in the Tree View under the user
block definition Lib1Usb1.
5. From the Tree View, select Attributes.
6. From the Data Grid, change the Attr1_u data type to STRING by clicking the Type cell (which currently contains
UNDEFINED), and selecting STRING from the drop-down list.
7. Change the PromptForInput cell of Attr1_u to True. (You may have to scroll right in the Data Grid to locate the
PromptForInput column.)
8. Now that the attribute has been created, create a user block variable with text substitution in its name. From the Tree
View, click Variables.
9. From the Data Grid, click the Name cell in the Append row (indicated by an asterisk *) and {Attr1_u}_thing. Leave
the data type set to the default value, BOOL.
10. Text substitution can also be used in variable connections. To connect the variable that was just created, click the
MOVE_1 block in the Tree View.
11. In the Summary View, double-click the enable pin of the block MOVE_1.
This feature is not available for the WorkstationST or Power Conversion components.
Attention
Software in the controller consists of blocks that perform control logic functions. The controller runtime provides a library of
standard blocks that can be combined to form user blocks. The Block Diagram Editor allows you to create and edit user
blocks using a visual interface and drag-and-drop tools. The Block Diagram Editor displays in the Summary View when a user
block is selected in the Tree View .
Additional editing tools display on the toolbar, and a sidebar called the Library View displays on the right side of the
Summary View to allow you to make changes to a user block.
Note If the user block is read-only or linked, an error message displays. If the user block is protected, you are prompted to
enter the appropriate password.
Property Description
Auto-Layout Mode Controls how the blocks on the diagram are arranged. Refer to the section Layout Modes.
Diagram Settings Displays the Diagram Settings
Append Sheet Adds a new drawing sheet at the end of the drawing
Insert Sheet Inserts a sheet immediately before the current sheet in manual mode
Delete Sheet Deletes the current sheet in manual mode
Rename Sheet Opens the Rename Sheets dialog box
Edit Sheet Border Opens the Sheet Border Editor
Print Sheet Prints the current sheet
Zoom Adjusts the zoom level to either a preset zoom level or a custom value
View Settings Allows you to toggle the rulers, library view, and print border
Paste Inserts the contents of the clipboard at the selected location
➢ To rename sheets: from the Tree View, right-click Programs or right-click anywhere in the empty portion of the
diagram.
Note For a particular sheet, you can enter a complete sheet name or use certain substitution characters to automatically
number or letter the sheets within a particular diagram.
Sheet Names
Substitution
Represents Example
Character
# Sheet number
@ Sheet letter
{AttributeName} Attribute
➢ To customize the sheet border: from anywhere in the Block diagram: right-click and select Edit Sheet Border.
Select Border or
Footer options.
Preview
selected
options.
Edit footer,
then select
either Export
or Import for
border re-use.
Outer Line When selected, draws a rectangle around the outer edge of the border
Inner Line When selected, draws a rectangle around the inner edge of the border
When selected, draws the footer. When unchecked, the Footer Options and Footer Block section of
Footer
the dialog box is grayed out.
Footer Height Total vertical space allocated to the footer
Number of rows in the footer; each row is allocated vertical space equal to the footer height divided
Footer Rows
by the number of rows
Number of columns in the footer; each column is allocated horizontal space equal to the border
Footer Columns
width (which is paper size-dependent) divided by the number of columns
5.3.2 Preview
The Preview section displays how the border looks with the selected options. Additional preview features include the
following:
Cell Description
Next Cell Selects the next cell in the footer (list is sorted in Z order back to front)
Previous Cell Selects the previous cell in the footer (list is sorted in Z order back to front)
Delete Cell Removes the current cell from the footer. The button is only visible if a cell is selected.
Adds a new cell to the footer at the current Row and Column. The button is only visible if no cell is
Create Cell currently selected. Clicking an empty spot on the footer in the Preview makes the Create Cell visible
and presets the Row and Column fields to where you clicked in the preview.
Top-most Footer row for the current cell. It does not need to be within the footer boundaries, which
Row
allows special effects like non-rectangular footers.
Export Saves the current border from the editor to a specific .xml file
• Caption is text displayed in a smaller font on the first line of the cell.
• Text is text displayed in a larger font on the second line of the cell.
For both fields, the text is clipped to the size of the cell (no wrapping) and both support Attribute substitutions. For example,
if the custom text for a border cell is custom Text with {Attr1} substitution, the {Attr1} is replaced with the current value of the
user attribute Attr1 in whatever context the border is drawn. If Attr1 is not defined, it is removed from the text. These attribute
substitutions allow the user to customize footer contents for specific programs, tasks, or user blocks.
• Customer Site
• Customer Name
• Drawing Number
• Engineer
• Requisition Number
• Process Application
• Shop Order Number
• DM Number
• Serial Number
• Machine Size
Automatically-generated configuration data includes:
Some complex blocks have functional groups of input and output pins.
Grouped
input pins
MODE_OPT
set to NONE
MODE_OPT
set to AUTO Auto
displays Auto mode
mode pins pins
Note Pins hidden by animations always display if they are connected to a variable.
Layout Modes
Arranges blocks in execution order in one column, with inputs and outputs lined up on the edges of
List Layout the sheet. All Rung blocks display as Rung diagrams rather than blocks. This mode is ideally suited
for sequencing, and can be used to simplify very large diagrams where wiring becomes confusing.
Does not arrange blocks or wires, but leaves all layout tasks to the user. It is ideal for users familiar
Manual Layout with a sheet-oriented approach to design or for applications where very specific documentation
standards must be met.
➢ To add a block
1. From the Library View, select a category and the desired block, then use the drag-and-drop operation to move the block
to the Block Diagram Editor.
Or
From the Tree View, right-click a task, a user block, or a block and select Add Block.
2. Select the desired block and click OK.
Block Properties
Property Description
Block Type Name of the library block from which this block was created
Description Text describing the selected block
Unique identifier that allows the block (as well as its attributes and pins) to be referenced
Instance Name
from other places in the ToolboxST application
Instance Script Script that runs when the block is instanced
Height Height of the block in the diagram
Left Location of the left of the block in the diagram
Selected Pin Pin currently selected in the block highlighted in the diagram
Show Description When set to True, displays the description text for this block on the diagram
Top Location of the top of the block in the diagram
Width Width of the block in the diagram
Detached Summary File Backsheet for the selected block
Version Read-only the version number of the source for this block instance
Determines when the block is run. Setting this property automatically renumbers other blocks
Execution Order
in this user block. The blocks are run in sequential order
operation. You can also use the Wiring Tool for pin connections , which forms connections to both normal blocks and to
blocks with a configurable number of inputs (rubber pins).
Forcing of control logic for an operating process is strongly discouraged. 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 protective functions is never permissible for an operating unit. All safety
Warning measures should be strictly enforced in conjunction with this procedure.
Note While using the Zoom tool, the diagram hyperlinks are active.
Menu Items
Item Description
Block Help Displays a help window for the selected block
Opens the New Trender dialog box. Once you enter a name, Trender opens with the block
Add To Trend automatically added.
Refer to the Trender Instruction Guide (GEI-100795).
Opens the new Watch Window dialog box. Once you enter a name, Watch Window opens
Add to Watch
with the block automatically added.
Toggles the display of description text for the block. This text is the most effective way to
Show Description on Diagram
document a block, as the text stays attached to the block when the diagram is rearranged.
Edit Block Pins Displays the Edit Block Pin Connections dialog box.
Unhide all Pins Causes the pins to display
Use Status When enabled, uses the status of each input to calculate the status of each output
Add Pin Group If selected, adds additional inputs
Remove Empty Pin Groups Removes empty inputs
Show boolean logic as Rung (RUNG blocks) displays Boolean logic for the block
Displays the RLD Editor
Edit Ladder Logic
Refer to the section Rung Editor.
Copy Copy a block
Paste Paste the copy to the diagram
Cut Cut a block from the diagram
Delete Delete a block from the diagram
Bring to Front Reorder blocks, causing them to display above or below all other blocks and shapes on
Send to Back the diagram when overlap occurs.
Insert whatever is on the clipboard but sets the run order of the blocks to occur
Paste After
immediately after the right-clicked block.
➢ To connect a single pin: from the Block Diagram Editor, double-click a pin.
Note Press Enter while entering text to select the next pin on the block, allowing rapid entry of connections.
3. Select the Connection column to display a drop-down list that includes Browse Globals and Browse Locals. Any
enumerated values that are legal for the selected pin also display in the drop-down list. Select an option to display the
Select a Variable dialog box.
All block pin connection changes take effect immediately. (The Edit Block Pin Connections dialog box does not contain an
OK nor a Cancel button.)
➢ To reverse any changes: from the Component Editor Edit menu, select Undo.
➢ To toggle between live variables and values: from the diagram Layer toolbar, click the down arrow and select the
desired action.
Variable only:
Value Over Variable displays the live value larger than the variable:
Variable Over Value displays the variable name larger than the live
value:
Variable Inline with Value both display larger and may overlap other
shapes in the diagram:
Forcing of control logic for an operating process is strongly discouraged. 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 protective functions is never permissible for an operating unit. All safety
Warning measures should be strictly enforced in conjunction with this procedure.
➢ To change the value of a variable: from the Software tab (any place variables are used), double-click a variable
value to display the Send Value dialog box and change it as needed.
Boolean Values
Click Send to
send the New
Value to the
Enter a value to
controller.
be added to or
subtracted from
the variable. Click to increase
or decrease the
variable by the
Select Force delta value and
Value to prevent send to the
selected value controller.
from being
overwritten.
Numerical Values
Array Values
The Variable Rail Tool arranges inputs along the left side of a sheet and outputs along the right side to improve
readability. It inserts a variable reference that can be wired to a block pin and moved around freely.
Inputs Outputs
Properties
Item Description
Variable Displays the variable represented by the shape
Top Displays the top location of the variable shape
Left Displays the left location of the variable shape
Width Displays the width of the variable shape
On a variable rail display with symbols and cross references that indicate the role of the variable in the
Variables
system
Note The Variable Rail tool is only used in Manual Layout mode. (Refer to the section Layout Modes.) When you select the
Variable Rail tool, a message displays that enables you to switch to this mode.
Local input
Global variable
Undefined variable
EGD variable
Pin callout
I/O
Note The text in the I/O symbol indicates the redundancy for an input.
Connected I/O can be:
• Simplex Input with 1 IONET (S1)
• Simplex Input with 2 IONET (S2)
• Dual Input (D)
• TMR Input (T)
• HotBackup Input (H)
To define a rectangular
area for the rail, click
and drag the cursor.
Tip � Clicking in the right or left two inches of the sheet docks the rail to the sheet’s edge.
Note Variables from other windows (Watch Windows, Trenders, and such) can be dragged and dropped into a variable rail.
➢ To connect variables on a rail to a block pin: drag a variable from the rail and drop it into a block pin to form a
wired connection.
➢ To move variables on a rail: select and drag the variable from the rail to the desired location.
Variable Commands
Command Description
Displays a list of all places that the selected variable is used (hardware I/O, EGD page, and
Go To Where Used
such)
Add To Trend Adds the selected variable to a defined Trender
Add To Watch Adds the selected variable to a defined Watch Window.
Navigates to the location where the variable is defined. It automatically selects the Where Used
Go To Definition
tab in the Component InfoView.
Change Live Value Displays the Change Live Value dialog box (you must be online).
Add To EGD Set the EGD page for the selected variable
➢ To add Rectangle or Ellipse: click the desired upper left corner of the shape, drag to the desired lower right corner
and release the mouse button.
Rectangle / Ellipse Tool Properties
Properties Description
Line Color Displays the color of the shape's line
Line Thickness Displays the thickness of the shape's line
Filled When set to True, causes the shape to be filled with the color specified in the Fill Color property
Fill Color Displays the color the shape is filled with when Filled is set to True
Top Displays the top location
Left Displays the left location
Height Displays the height
Note The image file is not embedded in the diagram. All images must be distributed separately from the .xml files for the
diagram.
Tip � To ensure that images can be found when the diagram is moved on the hard disk, avoid hard-coded path names or
mapped drive names. Relative names, such as ...\Metafiles\bom1.wmf are best.
For example, if the system settings specify the paper size as Letter, the library and user settings specify Use Parent Setting,
and the diagram settings set the paper size to Legal, that diagram displays on legal-size paper while all other diagrams display
on letter-size paper.
➢ To configure diagram settings: from Edit mode, right-click an open area of a diagram and select Diagram
Settings.
Tip � Selecting the Default to parent setting or a dimmed check box indicates that you have no preference at the current
level. The diagram uses the settings from the next level down in the hierarchy.
The rung block controls variable values using Boolean logic equations. While you can specify a Boolean logic equation
directly by connecting it to the EQN pin of the rung block, a graphical RLD Editor is also available to simplify the process.
➢ To open the RLD Editor: from a Block Diagram, double-click a Rung Block.
The RLD Editor window consists of both a 16x16 or smaller grid of cells that can contain contacts or wires and a set of tools
used to edit the contents of the cells.
Drag
separators
to add or
remove rows
Displays the
current
equation or
error message
directly or the negation of the variable are added to a ladder diagram using the contact tools.
➢ To add a contact
1. Select the contact tool that matches the type of contact you want to add. The cursor changes to
reflect the selected contact type.
2. Click a cell to add a new contact.
3. Double-click inside the cell above the newly inserted contact to open the Connect Contact dialog box.
5.15.2 Wires
Wires are used to connect contacts to the coil and to each other.
➢ To add a wire: select the Wire tool and click a location on the grid.
Wires can only be drawn vertically or horizontally:
➢ To add or remove rows or columns: drag the boundary between any row or column. Blue text indicates the result of
the action.
5.15.5 Errors
You can create rung diagrams in the RLD Editor that do not convert to compatible Boolean logic functions. Typical errors
include not connecting a contact to a variable, creating a wire or contact that is not connected to power and ground, or
creating a short circuit. If you make one of these mistakes, text displays on the status bar to help you resolve the error.
Note When the output equation displays on the status bar, the diagram is correctly drawn and no errors are detected.
➢ To open the Combinational Logic Editor: from the Block Diagram or Tree View, double-click a LOGIC_
BUILDER block or right-click a LOGIC_BUILDER block and select Edit Combinational Logic.
Note The Combinational Logic Editor can remain open while you work in other ToolboxST windows.
Pins
list
Status
bar
Logic gates AND, OR, and NOT can be used in Combinational Logic. If there is an existing equation on the block being
edited, it is automatically converted to a logic diagram. Each + operator becomes an OR gate, each * operator becomes an
AND gate, and each ~ operator becomes a NOT gate. Gates can also be added to the diagram.
Note The position of the gate will change as interconnections are made with Inputs and other gates.
Combinational logic blocks have up to 32 input pin groups. These are added and removed from the block using the block
diagram or Edit Block Pin Connections dialog box. As soon as inputs are changed, the Input List in the Combinational Logic
Editor is updated. Once a pin displays in the Pin List it can be used to make connections to logic gates.
or
4. Click a gate to add a new input to the gate.
Note A Tool Tip displays warnings for connections that cannot be made.
The only output for the equation displays in the pin list as OUT. Only one gate can write to the OUT, and OUT cannot be used
as an input.
The drag-and-drop feature can be used to connect pins on gates. Tool Tips provide feedback on permitted connections. Wires
between gates alter the automatic arrangement of the diagram.
If there are errors within the diagram, an equation will not be calculated and the OK and Apply buttons are grayed. Click the
status bar to display errors.
• Unconnected pins
• Unreachable gates, or gates that have no direct or indirect connection to the OUT variable
• Feedback, where the output of a gate is used as input to the same gate or a gate that feeds into the same gate
• Multiple gate outputs connected to a single gate input
• OUT used as an input
• Inputs used as a gate output
➢ To create a component: from the System Editor Tree View, right-click the system and select Insert New,
Controller, and Mark VIe Controller.
Tree View
lists the items
that can be
configured.
The list
changes when
a different tab
is selected.
Property
Editor
allows you to
edit the item
currently
selected in
the Tree
View.
Component
InfoView
displays
information
about the
currently
selected item.
➢ To edit the component: select an item in the Tree View. The configuration information displays in the Summary
View and Property Editor.
➢ To edit a property in the Property Editor: select an item by clicking its value field.
Click the drop-down menu button to select a value from a drop-down list.
Note If no button displays, edit the value directly in the corresponding text box on the right side of the Property Editor.
Log Tip � If there is a build problem, the error is listed on the Log tab. Double-click the error. The input focus goes
to the location in the component configuration where the error occurred.
Status Displays operating state and equality information about the component
Keeps a navigation history for each user session and allows you to return to different places in the
History 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.
Finds all uses of a variable within a Library Container
The write icon at the beginning of some lines indicates that the variable is being written at that location.
Where 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.
Each time a Build is performed, a message displays that allows you to view the Change log.
When Errors or Warnings are present, the Log tab notifies the user by displaying the current count, as well as a description.
Click each button to hide the corresponding item. For example, click Warning to hide the warnings listed in the Log tab;
Click Warnings again to display the warnings in the Log tab.
Note Some Data Grids, especially those without an Append Row, may not support all available features.
Quickly set a property to the Left-click the row header for the first row to be edited. Then, while pressing the CTRL key,
same value for multiple rows left-click added row headers. After selecting all desired rows, use the Property Editor to
change properties for all selected rows. (Some properties are omitted when a group of rows is
selected, and properties with conflicting values will display no value in the property editor.)
To... Do this:
Resize a column Drag the vertical bar on the right of the column header to a new location.
Quickly remove a single column Right-click the column header and select Hide Column.
Move a column to a different location Drag the column header to a new location.
Sort by a column Click a column header. The column sorts in ascending order. To sort in descending
order, click the column header again.
Reset columns to the original Right-click any column header and select Default Column Organization.
configuration
Add or remove columns Right-click any column header and select Organize Columns to display the
Organize Columns dialog box.
Select a
column name
and use the up
arrow to move
it to the left-
most side of
the Data Grid.
in the destination grid and select Paste Row(s) to insert the row into its new
location.
Copy and paste multiple rows Left-click the row header for the first source row. Then, while pressing the CTRL key,
left-click added row headers. After selecting all desired rows, continue to hold down the
CTRL key and right-click any selected header. From the shortcut menu, select Copy
Selected/Current Rows to place the rows on the clipboard. Then, right-click the header
for the append row in the destination grid and select Paste Row(s) to insert the rows into
their new location.
Copy and paste a range of two or Click the top left cell of the desired range and drag to the bottom right cell. Right-click the
more cells selected region and select Copy Selected/Current Rows to place the cells on the
clipboard. Then, click the top left cell of the destination range and drag to select the
same number of columns and rows that were copied to the clipboard. Right-click inside
the destination region and select Paste Row(s).
Move rows between data grids Arrange windows on screen so both the source and destination grid are visible. (An
entry in a Tree View is acceptable as a destination). Left click the row header for the first
row. Then, while pressing CTRL, click any added row headers to be moved. Release the
CTRL key and drag a row header to the new data grid.
Add a variable to a block diagram, Arrange windows on screen so both the source grid and a destination block diagram,
Trender window or Watch Window Trender window or Watch Window are visible. Then, drag the row header for the variable
from a data grid 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.
Settings Properties
Property Description
Download
When set to True, allows you to download application code to redundant controllers in
Controller Parallel Online Download
parallel
Displays the boot loader in the Download Wizard when it does not have to be
Show Boot Loader
downloaded
FOUNDATION Fieldbus
Enable User Configuration of Link When set to True, allows you to configure the link master device on a FOUNDATION
Master Devices Fieldbus segment link
The minimum time between retries of FOUNDATION fieldbus alert reports. Units are 1/32
FOUNDATION Fieldbus Alarm ms, (32000 = 1 sec). This applies to the entire device. (Range is 1 to 640000).
Confirm Time Note Setting this value too small may adversely affect the reporting of alerts from
runtime. The recommended value is 640,000.
Linking Device Parameters are
Prevents modifying of linking device parameters
Read-only
I/O Diagnostics
Makes controller I/O diagnostic Alarm events available for automatic Alarm updates in
Enable I/O Diagnostic Alarm Events
the I/O Diagnostic Viewer
PROFIBUS
Show Advanced Importer Screen Displays the advanced importer screen when importing a PROFIBUS configuration
V300
When set to True, allows users to configure the Wind Turbine Control for Wind Farm
Management at the System level using the System menu item Set Wind Turbine
V300 Advanced Options
Control Configuration. For more information, refer to the section System Editor Menus,
listed as a System menu Command item.
6.9 Security
The ToolboxST application provides security based on user-entry passwords. Passwords ensure that only authorized persons
have access rights to view or modify system components. Protected objects can have one or more of these access rights and
each access right can have a different password. Some objects can be password-protected if they are contained in another
parent object, which is protected by its own password(s).
Access Rights
Access Rights Description
Allows you to set Modify Data and Modify Design access rights to pre-defined user roles. Once roles
Access Roles
have been assigned to a protected object, only users with those roles can access the object.
Allows you to make changes to data values associated with an object without changing how it works.
Modify Data 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.
Allows you to change the way a protected object works. For example, this protects block creation and
Modify Design 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.
Note Passwords are case-sensitive – secret and Secret are not considered to be the same password.
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.
➢ To clear all passwords and protect the component: from the Device menu, select Restore Password
Protection.
Protection Properties
Property Description
Access Roles Allows you to set modifying data and design rights to previously defined user roles
Allows you to modify data values and forcing of variables
➢ To upgrade a component
After a component has been upgraded, you cannot undo the upgrade. You also cannot
upgrade a component to its current or a previous version.
Attention
1. Install the latest version of the ToolboxST application.
2. Open the ToolboxST application, open the system .tcw file, and double-click a component.
3. From the File menu, select Upgrade, then select the component and appropriate I/O module(s) to upgrade.
To select all I/O modules for upgrade, click the top box in Item column box. From the New column drop -down list,
select the new firmware version .
To select one I/O module, select the box next to the I/ O module name.
Click the document icon next to the
To select multiple I/O modules, press and hold the Ctrl or Shift Key and version to display release notes for the
select each I/O module. selected version .
Note User manuals, product updates, and other information sources are available on the GE Automation & Controls
Support website under Mark Controls.
Note For more information, refer to the Mark VIe and Mark VIeS Control Systems Volume 1: System Guide (GEH-6721_
Vol_I).
5. From the toolbar, perform a Build and Download to the Mark VIe controller.
7. From the toolbar, perform a Build and Download to the Mark VIe controller.
8. Repeat these steps for each Mark VIe controller in the system.
A Compare Results: window displays differences between the two selected devices.
➢ To configure Mark VIe control: open the Component Editor and select the General tab.
Note These properties are displayed in the footer section of logic sheets. Refer to the section Customize Sheet Borders.
Note The first time you attempt a password-protected function, the Enter Password dialog box displays. All protected
functions performed during the remainder of the ToolboxST session do not require re-entering the password.
6.18.3 Attributes
Attributes are device-level values that affect how the configuration is generated. Select the Attributes item in the General tab
Tree View to edit controller attributes in the Summary View data grid.
Attribute Columns
Column Description
Name Unique identifier for the attribute
Description Stores added comments about the attribute
Value displays and modifies the current attribute value
➢ To open the Attribute Value Editor: from an attribute Data Grid, select a Value Cell and click the ellipsis button.
Name of the
attribute being
modified
If checked, the
attribute values
are restricted to
an enumeration
(a predefined set
of allowable
values).
To add a value to
the enumeration,
enter the Name,
and a Description
(optional) and click
OK.
Note For more information on EFA, refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose
Applications System Manual (GEH-6721_Vol_II), the section UCSC Embedded Field Agent (EFA).
For information on the virtual network, refer to GEH-6721_Vol_II, the section Virtual Network.
The following table describes the properties displayed in the Property Editor when a Virtual Network Adapter item is selected
in the Tree View.
Virtual Network Adapter Properties
Property Description
Adapter Settings
Enabled If set to False, disables the selected Virtual Network Adapter. Set to True to enable the network adapter.
IP Address Default IP address for the selected network adapter (not usually changed from default setting)
Network Settings
Network EFA (typically the only type of network)
Subnet Mask Default subnet mask for the network (not usually changed from default setting)
The OPC UA server currently only supports anonymous connections. If you are
deploying a Mark VIe controller in a secure state, it is recommended that you set all
variables available through OPC UA to Read-only access, using the External Access
property in the ToolboxST application.
Attention
Note This feature is not available for the UCPA or Mark VIeS UCSBS1A controller.
Use of the OPC UA server will reduce controller idle time, which is directly affected by the following:
• Number of clients
• Sampling intervals of the OPC UA client
• Type and number of variables being used
The OPC UA server makes a subset of variables available to OPC UA clients. Set the variable’s Download Info property to
True to make a variable available through OPC UA.
4. Download to the controller and verify that it is online and in the controlling state.
After the OPC UA server has been enabled and the clients are configured and requesting data, the controller idle time should
be observed to ensure adequate performance.
• Make fewer variables available through the OPC UA server by setting Download Info property to False for as many
variables as practical.
• From the client, decrease the number of variables requested or increase the sampling interval.
• From the client, disable OPC UA to reduce the total number of clients requesting data from the Mark VIe controller.
Typical Idle Time Starting at 95.4 with UCSBH4A Controller and 500 ms fixed sampling interval
Typical Idle Time Starting at 95.4 with UCSBH4A Controller and 250 variables
Typical Idle Time Starting at 93.1 with UCSA Controller and 250 variables
Note The first time you attempt a password-protected function, the Enter Password dialog box displays. All protected
functions performed during the remainder of the ToolboxST session do not require re-entering the password.
➢ To change the network redundancy: from the Hardware tab Tree View, select the Distributed I/O item.
Select an I/O
module type. The
available types
are based on I/O
pack redundancy.
Click Next.
Enter the
Terminal Board
Position.
Bar Code is the unique hardware bar code for the I/O terminal board.
Position is an identifier consisting of 3 or 4 alphanumeric characters that identifies the location of the I/O terminal board
within the cabinet. This information is on a label next to the I/O terminal board. Note: If the position is left blank, it will
default to the module ID.
Note The Shared IONet feature is not available for the UCPA controller.
Beginning with ControlST* V04.06, sharing data between two control sets on a single Ethernet input/output network (IONet)
is available for some Mark* controllers. The owner controller allows for the configuration of the owned I/O modules, writes
outputs, reads SOEs, and provides diagnostic information. Owned I/O modules are attached to their owner controller that can
configure and write to them, and obtain their IP addresses from their owner controller. Outputs from controllers are received
by their owned I/O modules (not shared I/O modules).
Note A control set is the group of controllers (based on redundancy) with the set of owned I/O modules. From the
ToolboxST* System Editor Summary View, a control set displays as a single controller.
A shared I/O module sends field device inputs to both its owner controller and to the consumer controller. The consumer
controller receives the field device inputs from the shared I/O modules that are owned by the other owner controller.
Configuration of the control sets is managed with the ToolboxST application. The computer with the ToolboxST application
communicates with the I/O devices through a software gateway function residing in the controllers. Refer to Mark Controllers
Shared IONet User Guide (GEH-6812) for further details.
In a Shared IONet group containing one Mark VIe controller and one Mark VIeS Safety controller, the Mark VIeS Safety I/O
module inputs can be shared between both controllers. However, the safety controller only receives inputs from its owned
safety-certified I/O modules. The safety controller continues to send outputs using a broadcast addressing scheme.
In a Shared IONet group with either two Mark VIe controllers or one Mark VIe controller, either controller can receive each
other's inputs and send outputs in a peer-to-peer communication. The Mark VIe controller delivers outputs to I/O modules
through a multicast packet that contains a specific section for each output device. Multicast is the delivery of a message or
information to a group of destination IONet devices simultaneously in a single transmission from the source. Mark VIe
controllers use multicast addressing to send outputs to I/O modules unless legacy hardware requires otherwise.
After I/O modules have been added to both owning controllers, inputs can be shared to the other Mark VIe controller. Inputs
from Mark VIe controllers can not be shared to a Mark VIeS Safety controller.
Select I/O
modules and
click OK.
➢ To create a Group: from the Hardware tab Tree View, right-click Distributed I/O and select Add Group.
Enter a
Description
(optional).
2. When the cursor changes to a symbol, release the mouse button to move the module.
Modifiable properties
include:
Terminal Board Type
Bar Code
Position
TB Connector
Note For more information, refer to the ControlST Software Suite How-to Guides (GEH-6808), section How to Upgrade a
BPPB-based I/O Module with a BPPC-based I/O Module.
• Summary
• Variables
• Diagnostics
• Status
Note For information about the settings configured by I/O pack-specific tabs, refer to the I/O pack documentation.
The Summary tab displays a graphical overview of the selected I/O module.
Note Some infrequently used parameters are classified as Advanced, and are hidden by default. To display Advanced
parameters, click the Show/Hide Advanced button on the toolbar.
Note For some I/O modules, these tabs are split into more module-specific input/output tabs that better define their function.
The Variables tab displays available variables from the I/O module that have no physical endpoint. These variables exist
only internally in the I/O module, and can be connected to another variable for use in code.
The Extra Circuits tab contains input/output variables found on the I/O module terminal boards, which can be associated
with the application software. For some I/O modules, these tabs are split into more I/O module-specific input/output tabs that
better define their function.
The Input and Output tabs contain input/output variables found on the I/O module terminal boards, which can be
associated with the application software.
The Diagnostics tab allows you to check Alarms and errors on I/O packs. Each I/O pack has a unique set of diagnostic
signals that can be monitored.
Inactive Alarm(s)
Active Alarm(s)
Note For more information about the fault codes used in an I/O pack, refer to the Mark VIe and Mark VIeS Control Systems
Guide (GEH-6721_Vol_III).
Note A software item (programs, tasks, and such) must be defined in the Software tab before this feature can be performed.
➢ To attach a software variable to an I/O variable: from the Data Grid, select the Variables tab.
You can also attach a variable by entering the variable name in the Connected Variable column and pressing Enter. If the
variable name entered is a defined variable, it continues to display and the cursor moves to the next field. If the variable name
entered is undefined, click Yes when the Undefined Variable dialog box displays.
➢ To upgrade an I/O module: from the Tree View, right-click the I/O module and select Upgrade.
Note You must be online to view all diagnostics, with the exception of reports.
Normal
Inactive Alarm(s)
Active Alarm(s)
Link broken
Link error
Link warning
Link information
Note Place the mouse over the icon to display Tool Tips.
• Alarm
• Revision
• Communication
• Hardware
Each report contains configuration or diagnostic details about the I/O hardware.
Note For more information, refer to the section Mark VIe Reports.
➢ To download parameters to a module: from the Hardware tab Tree View, right-click the module to be
downloaded and select Download Parameters.
Compare Parameters
While making changes to a module’s configuration, it is often useful to compare the downloadable configuration items
currently stored in the pack with the current configuration of the same items in the ToolboxST application.
Module parameters directly affect the operation of the controller and associated I/O
modules. To reduce the risk of improper operation or damage to the unit, always
check the Compare Parameters dialog box before downloading new parameter values
to a component.
Caution
➢ To open the Compare Parameters dialog box: from the Hardware tab Tree View, right-click a module to
compare and select Compare Parameters.
Note The first time you attempt a password-protected function, the Enter Password dialog box displays. All protected
functions performed during the remainder of the ToolboxST session do not require re-entering the password.
If adding a
program group,
enter a name
and click OK
Note The Add Existing Program command reads an .xml file from another system or controller into the current controller.
When the controller is online, double-click the live value of the variable _Enable for the task, select True to enable the task
or False to disable the task, then click Send & Close.
Disabled
Task Disabled
• Function block libraries describe software that is part of the controller firmware
• User block libraries combine these function blocks into user blocks
Attention
➢ To instance a user block: from the Tree View, right-click a user block and select Instance.
Note Variables can also be added in the Summary View by directly editing the append row of the variable grid.
➢ To unlink a program: from the Tree View, right-click a program item and select Unlink Permanently.
The linked icon next to the item in the Tree View changes and the program is unlinked from the library.
Property Editors
Programs
Removes the unused variables for all linked user blocks in this device when the user block is
Remove Unused Variables
instanced
Program
Library Type Name of the library definition that this program came from
Properties control the Access Roles, Modify Data, Modify Design, and View Design
Protection
permissions for this program
Task
Block Type Name of the user block definition in the library from which this task started
Help File Allows you to locate the Help file by clicking the ellipsis button
Help Text Locally defined Help that supersedes the global Help
Properties control the Access Roles, Modify Data, Modify Design, and View Design
Protection
permissions for this task
Revision History Allows you to edit the revision history by opening the Edit Text dialog box
Schedule Offset Offset from beginning of frame at which the task runs
User Block
Block Type Name of the library block of which the selected block is an instance
Unique identifier that allows the block to be referenced from other locations in the ToolboxST
Instance Name
application
Instance Script Causes the script to run when the block is instanced
Programs
Left Location of the left of the selected block
Selected Pin Pin currently highlighted in the diagram
Show Description When set to True, displays the description of the selected block
Enable When set to True, enables variables for the selected block
Version Version number for the source of the selected block instance
Execution Order Determines when this block is started
➢ To add a variable to a program: from the Software tab, expand the Programs item.
Includes:
• Not Logged
Controller
• Average Linear: this is a linear average {1/N * sum(values)}
Connected
• Average Linear Angle: This is an average for angle based variables; it takes into account 0 degrees
equals/360 degrees wrap-around for angles.
• Average Cosine Phi: This average calculation is for power factor (cos phi). It effectively calculates the
average of the arccosine of each of the data values during the interval. The value returned is the
cosine of this average.
• Data Snapshot: This selection is for end-of-interval values. The last value captured during the
specified interval is returned.
Enables the automatic collection by the Historian when:
Historian
Boolean and set to Logged on Change
Deadband
Analog and set to 0 or higher
Historian
Deadband Defines the deadband value as either engineering units or percent of range.
Definition
Enables the automatic collection by the Recorder when:
Recorder
Boolean and set to Logged Continuous or Logged on Change
Deadband
Analog and set to 0 or higher
Recorder
Deadband Defines the deadband value as either engineering units or percent of range
Definition
Usage
Allows a variable to be designated as a configuration setting. The default value is False, which prohibits
Control Constant
changing live values. Setting the property to True allows you to change live values.
If set to True, downloads extended information to the controller that is used by the web server, as well as
Download Info other processes. For example, to view alarms on the touchscreen, the Download Info parameter must be
set to True for each alarmed variable.
EGD Page Used to assign the variable to an Ethernet Global Data Page
Used primarily for EGD:
ReadOnly variable can be read on EGD
External Access
ReadWrite variable can be written to through EGD
NoAccess variable cannot be changed with the ToolboxST application
The variable's global name prefix type (None, Full, Block, Program, Task).
This controls the form of the global name that displays on the EGD page. For example, the name for
variable IGVA in user block VG_Health in task Task1 in program CORE would display (depending on the
Global Name Prefix) as:
Global Name
None: IGVA
Prefix
Full: CORE.VG_Health.IGVA
Block: VG_Health.IGVA
Program: Task1.IGVAv
Task: Task1.IGVAv
From the
Summary View,
select a variable.
From the Type
drop-down list,
select the
variable type.
Or:
from the
Property
Editor,
select Type
and the
variable type
• Replace the blockware detail view for the task or userblock with a graphic
• Add the graphic as a Sheet tab in the block’s detail view
• Display the graphic in a separate window using the eyeglasses button on the toolbar
• Diagnostic Alarms
• Process Alarms
• Hold List Alarms
• Events
• Sequence of Events (SOE)
Beginning with ControlST V04.04, controller configurations must not exceed the
following limits. If these limits are exceeded, reduce the number of configured Process
Alarms, Events, and Holds.
Note For further details, refer to the Mark VIe and Mark VIeS Controls Systems Guide (GEH-6721_Vol_I), the chapter
Alarm Overview, and the Workstation Alarm Server Instruction Guide (GEI-100626).
Parent and child Alarms can be exported using Alarm Rationalization. Parent alarms only can be imported from a .csv file.
Corresponding child Alarms are automatically placed in the configuration.
➢ To change the frame multiplier or the schedule offset: from the Summary View, click the Frame Multiplier
or Schedule Offset cell and select from the drop-down list.
Note Since the schedule offset depends on the frame multiplier, it is possible to select a frame multiplier for which the
current schedule offset is invalid. This causes a validation error when you build the application.
Note There is a 12 MB size limit on the memory that can be allocated to the DDRs. If this memory allocation is exceeded,
an error is reported during validation.
➢ To add a variable
1. From the DDR tab Tree View, right-click the DDR and select Add Variable.
2. Select the desired variables and click OK.
DDRs can be updated separately from the application code download.
➢ To update a DDR: from the Device menu, select Download and Update Dynamic Data Recorder.
Note DDRs cannot be downloaded if there is a major difference in the device. In this case, the application code must be
downloaded.
➢ To import or export a DDR: from the DDR tab Tree View, right-click the desired DDR and select Import
Configuration or Export Configuration.
Note If the .xml file being imported contains the formatting flags %n, it is replaced by the component Design Memo (DM)
number. This is a GE Power Systems project number and can be edited by selecting the General tab and Requisition Info.
4. Create a User Block in the program, and add two FuncGen blocks from the Data Collection section. Set up the pins
on the two blocks as follows. FuncGen1 is set up as a Sine wave generator and FuncGen2 is set up as a Triangle wave
generator.
5. Add the two variables SineOut and TriangleOut to the DDR. Set the Frame Period Multiplier to 3, which means a
sample is collected every 120 ms. The base frame period is typically 40 ms. Set the PreTrigger samples to 20 and the
PostTrigger samples to 100, so that the entire capture takes 14.4 seconds.
9. From the View menu, select Trenders to add a new trend and upload the capture buffer.
10. From the Trender window, select Edit and Add Traces to display the Trender - Add Trace Wizard.
11. From the wizard, select Capture Buffer/Dynamic Data Recorder to select the DDR to upload.
Note When the first Produced Page is created, it automatically becomes the default page.
Tip � Any variable defined with $Default as the EGD page name is automatically placed on the currently selected default
page.
➢ To delete a page: from the Tree View, right-click the page to delete and select Delete.
➢ To compress a single page: from the Tree View, right-click the page to compress and select Compress.
➢ To compress all Produced Pages in a component: from the Tree View, right-click Produced Pages and
select Compress All.
Tip � If the variable to be added to the EGD page is already in use on the Software tab, you can add the variable without
using the EGD tab. To add a variable from the Software tab, select the desired variable(s) in the Summary View and set the
EGD Page property using either the Summary View or the Property Editor.
➢ To add a variable to a produced page: from the Tree View, right click a Produced Page and select Add
Variable to display the Select a Variable dialog box.
➢ To delete a variable from an EGD Page: from the Summary View, right-click the variable to delete and select
Delete Selected Row(s).
➢ To copy variable information from an EGD Page to the clipboard: from the Summary View, right-click a
variable and select Copy Selection. The data is copied in .csv format.
Note To edit exchange signatures and configuration time, set the Layout Mode property to Manual. The Layout Mode
property displays when a Produced Page is selected in the Tree View.
3. Review the warning about manual Exchange Signature editing and click OK.
4. Make any desired changes to the signatures and configuration time and click OK.
Filter Toggle defaults to a filtered state. It displays items that have the same name but have a different Producer ID as
the open component.
Delete deletes the selected item(s). If the item(s) were saved as part of the configuration, they can be added again.
The EGD configuration server uses the producer ID to store all the documents for an EGD node.
When a component is saved, the EGD configuration is automatically published to the EGD configuration server. To avoid
unintentional overwriting of data, do not configure more than one .tcw file for a server.
• Compare command compares the component's EGD-produced data configuration with the EGD configuration server’s
content.
• UnConsumed Data command generates a report showing variables produced by this component that are not listed in
any other device’s consumed data file.
Note You can select devices to search against. The individual pages, with just variables, perform the same Compare.
The Referenced Devices item on the EGD tab also has a Compare command that compares the consumed variable
information for the open component against the EGD configuration server’s content.
Note When EGD configurations are edited in remote devices, you must refresh the configuration to ensure that the latest
variable information is used. The configuration is automatically refreshed when a component is opened, and when a Build is
performed in the component.
➢ To refresh the configuration of a referenced device: from the Tree View, right-click the device to be refreshed
and select Refresh.
➢ To create undefined variables for a single or multiple referenced device(s): from the Tree View, right-click
either the device or Referenced Devices and select Create Undefined Variables.
Note Modifying Modbus properties results in a minor difference in the ToolboxST configuration. However, removing all
Modbus points creates a major configuration difference that forces an offline load.
Modbus Properties
Property Description Valid Range
Connection Specifies the time in minutes that the slave remains connected to the master over
1 to 10
Timeout Ethernet when no requests are being received.
Port choices:
Ethernet Port Specifies the Ethernet port to be used for slave-Ethernet communication
502 and 503
Specifies the timeout period expressed as character time X 10. For example, 35
Inter-Character
represents 3.5 character times, or 0.0036 seconds at 9600 baud, 1 start bit, no parity, 1 35 to 1000
Timeout (ICT)
stop bit.
Choices:
None, Odd,
Parity Specifies check character Even,
Mark, and
Space
Response Delay Additional delay time in ms before the slave responds to a master request. 0 to 999
Limits the number of commands processed per second. This is based on commands
Command Limit 0 to 25
that have changed, not commands that are identical to previously received commands.
Data Swapped Changes the transmission order if the data is greater than 16 bits when set to True. True or False
Settings Example
If set to True 32-bit example: 0x01234567 would be transmitted as 0x45 0x67 0x01 0x23
64-bit example: 0x0123456789ABCDEF would be transmitted as 0xCD 0xEF 0x89 0xAB 0x45 0x67
0x01 0x23
If set to False 32-bit example: 0x01234567 would be transmitted as 0x01 0x23 0x45 0x67
64-bit example: 0x0123456789ABCDEF would be transmitted as 0x01 0x23 0x45 0x67 0x89 0xAB 0xCD
0xEF
NAK Code specifies the Negative Acknowledge code to be used if data is requested from a controller that is incapable of
receiving the Modbus request. Possible codes are 4, 6 or None. None is selected only if the Modbus Master needs no reply
when communication fails between the Mark VIe controller and the target processor.
The ToolboxST application allows you to specify the variables on each page using a Data Grid. When you add a variable to a
page, both the Modbus Slave and the selected page are enabled on the controller. As you add and remove variables, the
controller is updated so that only pages containing variables are enabled. To completely disable the Modbus Slave, remove all
variables on all pages or from the Property Editor, select None as the Interface.
When a variable is added, the columns that display are listed in the following table.
Variable Columns
Column Description
Variable that is read or written from the device or the referenced device
Connected Variable
A connected variable must be added before the other columns become active.
Determines the variable data type and the registers used to transmit the variable data over a Modbus
connection as follows:
• BOOL is one bit of a 16-bit word (this is the only option if the connected variable is a BOOL.) All
BOOLs within a word must be set to the same Read or Read/Write direction.
• INT is a signed 16-bit word that takes one register
• UINT is an unsigned 16-bit word that takes one register
Point Data Type • DINT is a signed 32-bit word that takes two registers
• UDINT is an unsigned 32-bit word that takes two registers
• REAL is a signed 32-bit float that takes two registers
• LREAL is a signed 64-bit float that takes four registers
If a Modbus Master talking to a Slave will be writing to Booleans being added to a Holding Register, be
sure that all mapped Booleans are set to Read/Write. If the Master sends a command to change a
Boolean that is Read-only, the Slave will not perform any writes, and will return a Slave Exception.
Specifies the register address
When a variable is created, the address is automatically set to a value adjacent to the highest address
previously on the page, but the automatic value can be modified. Data types that are 32 bits or more
Address (DINT, UDINT, REAL, and LREAL) should be placed on odd addresses. The valid range for addresses
is 1 to 65534. When specifying an address for a BOOL variable, the bit 0-15 within the 16-bit word is
represented by a decimal. For example, 1.00 selects register address 1 and bit 0, and 10423.7 selects
register address 10423 and bit 7.
Raw Min Convert Modbus Slave variable data into engineering units
Raw Max The Raw Min and Raw Max columns control the minimum and maximum for the raw data. The Eng Min
Eng Min 0 and Eng Max columns control the minimum and maximum engineering units to which the raw data will
Eng Max be scaled. (The BOOL data type cannot be scaled.)
Read-only identifier automatically generated from the register page name, the address, and, if
Name
necessary, an added unique number
Note The range of the Modbus variable is determined by the data type and not by the scaling record. Each integer data type
has an implied range. The raw data range in the scale dialog box is only used to compute the gain and offset of the variable
when converting it to a signal.
Note To ensure data coherency, LONG Modbus variables should always start on an odd register number, and the master
should send both registers to the controller in the same Modbus transaction.
To ensure data coherency, FLOAT Modbus variables should always start on an odd register number, and the master should
send both registers to the controller in the same Modbus transaction.
Station ID Function Code … Function Specific Data … CRC-16 MSB CRC-16 LSB
Station ID (follower address) is a number from 1 to 255 that specifies the unit with which to communicate.
Function code specifies the purpose and format of the remaining message portion.
CRC-16 are two bytes that complete every serial Modbus message. These bytes check errors and are calculated to ensure that
no transmission error occurred while the message was in transit. The method for calculating the CRC-16 is a public protocol.
Refer to the Gould Modicon Modbus Protocol Reference Guide for information on calculating a correct Cycle Redundancy
Check (CRC).
The same functions are supported over Ethernet and the serial ports. All Modbus messages are received on the specified
Ethernet port. The Ethernet physical layer provides a CRC-32 check on all transmissions so the Modbus CRC-16 is not
included. Modbus over Ethernet adds the following header to the message formats.
Function Code (01) Start Coil (MSB) Start Coil (LSB) Number of Coils Number of Coils
(MSB) (LSB)
Starting output coil number is two bytes long, and can be any value less than the highest output coil number available in
the output coil table. The starting output coil number is equal to a number one less than the first output coil returned in the
normal response. For example, to get the first output coil, enter 0 for the starting output coil number. The high-order byte of
the starting output coil number field is sent as the first byte. The low-order byte is sent next.
Number of output coils to return is two bytes long, and must be from 1 to 2000, inclusive. It specifies the number of
output coils returned in the normal response. The sum of the starting output coil value and the number of output coils must be
less than or equal to the highest output coil number available in the output coil table. The high-order byte of the number of
output coils field is sent as the first byte. The low-order byte is sent next.
The normal message reply from the controller is formatted as follows:
Byte count is a binary number from 1 to 250. The specified number of data bytes follow.
Data bytes (data field) are the packed output coil status data. Each byte contains eight output coil values. The LSB of the
first byte contains the value of the output coil whose number is equal to the starting output coil number plus one. The value of
the output coils are ordered by number, starting with the LSB of the first byte and ending with the MSB of the last byte. If the
number of output coils is not a multiple of eight, then the last data byte contains zeros in one to seven of its highest order bits.
Function Code (02) Start Coil (MSB) Start Coil (LSB) Number of Coils (MSB) Number of Coils (LSB)
Starting input coil number is two-bytes long and can be any value less than the highest input coil available in the input
coil table. The starting input coil number is equal to one less than the number of the first input coil returned in the normal
response. For example, to get the first input coil, enter zero for the starting input coil number. The high order byte of the
starting input coil field is sent as the first byte. The low order byte is sent next.
Number of input coils to return is two-bytes long and must be from 1 to 2000, inclusive. It specifies the number of input
coils returned in the normal response. The sum of the starting input coil value and the number of input coils must be less than
or equal to the highest input coil available in the input coil table. The high order byte of the number of input coils field is sent
as the first byte. The low order byte is sent next.
The normal message reply from the controller is formatted as follows:
Byte count is a binary number from 1 to 250. The specified number of data bytes follow.
Data bytes (data field) are the packed input coil status data. Each byte contains eight input coil values. The LSB of the first
byte contains the value of the input coil whose number is equal to the starting input coil plus one. The value of the inputs are
ordered by number, starting with the LSB of the first byte and ending with the MSB of the last byte. If the number of input
coils is not a multiple of eight, then the last data byte contains zeros in one to seven of its highest order bits.
Function Code Start Register Start Register Number of Registers Number of Registers
(03) (MSB) (LSB) (MSB) (LSB)
Starting holding register number is two-bytes long and can be any value less than the highest holding register number
available in the holding register table. The starting holding register number is equal to one less than the number of the first
holding register returned in the normal response. For example, to get the first holding register number (holding register
number one) enter zero for the starting holding register number. The high order byte of the starting holding register number
field is sent as the first byte. The low order byte is sent next.
Number of holding registers value is two-bytes long and must be from 1 to 128, inclusive. It specifies the number of
holding registers returned in the normal response. The sum of the starting holding register value and the number of holding
registers must be less than or equal to the highest holding register number available in the holding register table. The high
order byte of the number of holding registers field is sent as the first byte. The low order byte is sent next.
The normal message reply from the controller is formatted as follows:
Function Byte Count First Register First Register … Data Registers Last Register (LSB)
Code (03) (MSB) (LSB) Requested …
Byte count is an even binary number from 2 to 254, or 0. If the byte count is 0, then the master assumes 256 data bytes
follow. Otherwise, the specified number of data bytes follow, not including the two CRC-16 bytes (serial mode).
Holding registers are returned in the data field in numerical order, with the lowest number holding register in the first two
bytes and the highest number holding register in the last two bytes. The number of the first holding register is equal to the
starting holding register number plus one. The high order byte is sent before the low order byte of each holding register.
Function Code (04) Start Register Start Register Number of Registers Number of Registers
(MSB) (LSB) (MSB) (LSB)
Number of input registers value is two-bytes long and must be from 1 to 128, inclusive. It specifies the number of input
registers returned in the normal response. The sum of the starting input register value and the number of input registers must
be less than or equal to the highest input register number available in the input register table. The high order byte of the
number of input registers field is sent as the first byte. The low order byte is sent next.
The normal message reply from the controller is formatted as follows:
Function Code Byte Count First First Register … Data Registers Last Register (LSB)
(04) Register (LSB) Requested …
(MSB)
Byte count is an even binary number from 2 to 254, or 0. If the byte count is 0, then the master assumes 256 data bytes
follow. Otherwise, the specified number of data bytes follow, not including the two CRC-16 bytes (serial mode).
Input registers are returned in the data field in numerical order, with the lowest number input register in the first two bytes
and the highest number input register in the last two bytes of the data field. The number of the first input register in the data
field is equal to the starting input register number plus one. The high order byte is sent before the low order byte.
Function Code (05) Output Coil (MSB) Output Coil (LSB) State (00 or FF) 0
Function code 05 is used to force (or write) a single output coil in the output coil table. The message sent from the master is
formatted as follows:
Output coil number is two-bytes long and can be any value less than the highest output coil number available in the output
coil table. The output coil number is equal to one less than the number of the output coil forced. For example, to change the
first output coil enter 0 for the output coil number. The high order byte of the starting output coil number field is sent as the
first byte. The low order byte is sent next.
State byte is sent by the master with only two possible values. A zero (00h) is sent to turn the specified output coil off (set
false). A value of 255 (FFh) is sent to turn the specified output coil on (set true). The state byte is always followed by a single
byte with value 0.
The format of the normal message reply from the controller is identical to the received message.
Function Code Holding Register Holding Register Register Data (MSB) Register Data (LSB)
(06) (MSB) (LSB)
Holding register number is two-bytes long and can be any value less than the highest holding register number available in
the holding register table. The holding register number is equal to one less than the number of the changed holding register.
For example, to change the first holding register enter 0 for the holding register number. The high order byte of the starting
holding register number field is sent as the first byte. The low order byte is sent next.
Holding register data field is two bytes long and contains the value to which the holding register specified by the holding
register number field is preset. The first byte in the data field contains the high order byte of the preset value. The second byte
in the data field contains the low order byte.
The format of the normal message reply from the controller is identical to the received message.
Data bytes (data field) are the packed output coil status data. The data byte contains eight output coil values. The LSB of
the byte contains the value of output coil number one. The MSB contains the value of output coil number eight.
Function Code Starting Coil Starting Coil Coil Count (MSB) Coil Count Data Bytes … Data …
(15) (MSB) (LSB) (LSB)
Starting coil number is two-bytes long and can be any value less than the highest output coil number available in the
output coil table. The output coil number is equal to one less than the number of the forced output coil. For example, to
change the first output coil, enter zero for the output coil number. The high order byte of the starting output coil number field
is sent as the first byte. The low order byte is sent next.
Coil count is two-bytes long. It specifies the number of output coils to set. The sum of the starting output coil value and the
number of output coils must be less than or equal to the highest output coil number in the output coil table. The high order
byte of the number of output coils field is sent as the first byte. The low order byte is sent next.
Byte count is the number of data bytes to follow.
Data bytes (data field) are the packed output coil data. Each byte contains eight output coil values. The LSB of the first
byte contains the value of the output coil whose number is equal to the starting output coil number plus one. The value of the
output coils are ordered by number, starting with the LSB of the first byte and ending with the MSB of the last byte. If the
number of the holding coils is not a multiple of eight, then the last data byte contains unused data in its highest order bits.
The normal message reply from the controller is formatted as follows:
Function Code (15) Starting Coil (MSB) Starting Coil (LSB) Coil Count (MSB) Coil Count (LSB)
Start register number is two-bytes long and can be any value less than the highest holding register number available in the
holding register table. The holding register number is equal to one less than the number of the changed holding register. For
example, to change the first holding register enter 0 for the holding register number. The high order byte of the starting
holding register number field is sent as the first byte. The low order byte is sent next.
Number of holding registers value is two-bytes long. It specifies the number of holding registers to set. The sum of the
starting holding register value and the number of holding registers must be less than or equal to the highest holding register
number in the holding register table. The high order byte of the number of holding registers field is sent as the first byte. The
low order byte is sent next.
Byte count is the number of data bytes to follow.
Register data field is two-bytes for each holding register to set. The first byte in the data field contains the high order byte
of each preset value. The next byte contains the low order byte.
The normal message reply from the controller is formatted as follows:
Function Code (16) Starting Register Starting Register Register Count (MSB) Register Count
(MSB) (LSB) (LSB)
Note The Modbus diagnostic utility is available with the Mark VIe controller firmware V03.03 or later.
Network Adapter 1 (located in the General tab Tree View) must be enabled, named,
and addressed. Refer to the section Network Adapters.
Attention
• Variable
• Block Pin
• I/O
• Alarm
• GE Rationalization
• Hold
• Event
• NovRAM
• IONet EGD
• I/O Pack Peer-to-Peer
• I/O Diagnostics
• Coding Practices
• FOUNDATION Fieldbus Configuration
• FOUNDATION Fieldbus H1 Field Device
• FOUNDATION Fieldbus Parameter Reconcile
• Auto-Reconfiguration
• Unlinked Programs/User Blocks
• Global variables
• Variable configuration
• Web
• Compressed data log
• EGD point list
• Alias
• Second language
Double-click a Global
Variable to go to where
the variable is defined
in the application code.
Note Intrinsic variables are not defined in the application code configuration. The Where Used tab displays locations in the
configuration where the intrinsic variables have been used.
Note Intrinsic variables are not defined in the application code configuration. The Where Used tab displays locations in the
configuration where the intrinsic variables have been used.
The Web report provides variable name, description, type, alias, second language description, and location in the application
code, as well as where the variable is used and if the variable is written multiple times in the code.
To generate a Variable Web report, Controller Web Pages must be enabled in the
controller Property Editor and the variables must have the Download Info column set
to True for the web report to display the variables.
Attention
1. Generate a Web report.
2. To enter alias names, save the report as a .csv file, enter alias names, then import the data back into the ToolboxST
system.
From the View menu, select Reports, Variable, and Second Language
to generate the Second Language report.
The Software tab displays the program, task, and block in which the pin is used.
Double-click the associated pin to display the connections.
From the variable report, double-click an I/O Variable to display the configuration.
From the View menu, select I/O, then select
to display the I/O Configuration report results.
Alarm Help files are only generated when the Publish Alarm Help property is set to
True in the system Property Editor.
Attention
From the View menu, select Reports, then select IONet EGD
to display the report results.
From the View menu, select Reports, then select I/O Pack Peer-to-Peer.
• Alarm
• Revision
• Communication
• Hardware
From the View menu, select I/O Diagnostics, then select Alarm.
2. Locate an alarm and view the details in the Diagnostic Alarm Viewer.
From the View menu, select I/O Diagnostics, then select Revision.
2. Locate a module in the report and view the details in the Status Viewer.
From the View menu, select Reports, I/O Diagnostics, then select Communication.
From the Hardware tab, right-click the Group, select Create Module Report, then select Communication.
From the View menu, select Reports, I/O Diagnostics, then select Hardware.
From the Hardware tab, select Create Module Report, then select Hardware.
• Unwritten variables
• Multiple writes
• Multiple output assigned variables
• Unused I/O
From the Coding Practices report , double-click a variable to display the configuration.
Note Refer to the section Report Features for a description of common report features.
Note Select All and Clear All works for each parameter in either the Device Value column or the ToolboxST Value column.
Selecting all values in one column will clear any selections in the other column. For example, selecting all Device Values will
clear any selections that have been selected in the ToolboxST Value column.
From the Device Value column or the ToolboxST Value column , select the check box
beside the value(s) to which you want the ToolboxST system and device to be set.
Note: Only one value type can be chosen for each parameter.
5. If there are unresolved parameters, they are indicated as unresolved (unequal) in the report. Refresh the report to display
only the unresolved parameters.
Note Reloading both ToolboxST and FOUNDATION Fieldbus device parameters takes additional time due to the need to
establish communications and read the FOUNDATION Fieldbus parameters from the H1 devices.
Caution
7. After the reconcile operation and report are completed, close the report window.
Note Refer to the section Report Features for a description of common report features.
b. For an H1 device:
• Configuration
• Difference
Note The contents of both types of reports can be exported to a .csv file.
If no differences exist between the ToolboxST configuration and the Auto-Reconfiguration server, the following message
displays.
• Equal displays if there are no differences between the ToolboxST configuration and the Auto-Reconfiguration server.
• Not Equal displays if there are differences between the ToolboxST configuration and the Auto-Reconfiguration server.
• Disabled displays if the Auto-Reconfiguration property is set to False in the General tab Property Editor.
• Downloading displays if a download is occurring.
Status Tab
• Open report
• Save report
• Retrieve (generate) report
• Export report
• Import report
• Print report
• Sort (modify) columns
• Filter
• Refresh
• Zoom
• Find text
• Help
Toolbar Icons
Icon Description
Zoom in
Zoom out
Get help
➢ To save a report
➢ To sort a report column: click any column heading to apply a sort to that column. The first click sorts the column in
ascending order; a second click sorts the column in descending order.
Column
names that
display in
blue cannot
be moved.
Or
2. Select a column header and use the drag-and-drop feature.
If selected,
capitalization
in the test
string must
match the
text in the
report exactly
➢ To apply a report filter: from the Report menu, click Apply Filter to open the Edit Report Filter dialog box.
Available Available
columns comparison
(double-click and Boolean
to add to an operators
equation) (double-click
to add to an
equation)
Click to add
parentheses
Click OK to
accept the
filter equation
Enter filter that displays.
equation to
be used. Click Clear
to delete the
equation.
Click Cancel
to cancel the
equation but
keep the
current
settings.
When using the LIKE operator, you can prefix or suffix a wildcard character, either * or
LIKE
%, to the right-hand value. The wildcard character can stand for any number of
alphanumeric characters, including zero. The wildcard character can only be present
at the beginning or the end of the right-hand value (for example, *value or value* or
*value*)
AND Expressions to the left and right of the AND operator must both be True
OR Either the expression to the left or to the right of the operator must be True
NOT Expression to the right of the operator must be False
You can use as many groups of parentheses as necessary to define an expression.
String values must be enclosed in single quotes , for example 'string'
➢ To remove a report filter: from the Report menu, click Remove Filter. The filter is removed and all available rows
display.
• I/O Variable
• I/O Configuration
• Global Variable
• Block Pin
• Variable Alias
• Second Language
• GE Rationalization
The Variable Alias report and the Second Language report can be imported from either a .csv or an .xml file, but the other
reports can only be imported from a .csv file.
➢ To import an I/O Variable, I/O Configuration, Global Variable, or Block Pin report
1. From the File menu, select Import, then select the desired report.
2. From the Open Report dialog box, select the report and click Open to import the data. Any data that cannot be
modified is highlighted when the report displays.
Note Only the Alias and Second Language properties can be modified.
1. From the File menu, select Import, then select either Variable Alias Report or Second Language Report.
2. From the Open Report dialog box, select either a .csv or an .xml file and click Open to import the data. Any data that
cannot be modified is highlighted when the report displays.
Tip: Change the Save as type to All Files (*.*) so you will
still be able to save the file as a .csv file.
Click Save .
5. Import the file into ToolboxST and verify that all the special characters display correctly.
If you use Microsoft Excel to modify the .csv file, make sure you save the file back to a
.csv file from an .xls file.
If the .csv file contains UTF-8 special characters, to avoid issues with displaying
special characters after import back into ToolboxST open the file with Notepad and
Attention save the file with Encoding set to UTF-8. Refer to the procedure To avoid issues with
second language special characters during import.
Note GE recommends that users modify .csv files with Notepad or Wordpad rather than Microsoft Excel.
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
Warning measures should be strictly enforced in conjunction with this procedure.
➢ To display Forced Variables: from the Component Editor View menu, select Forced Variables.
➢ To force a value or change a previously forced value: from the Forced Variables dialog box, double-click a
value to display the Send Value dialog box.
➢ To remove a single forced value: right-click a forced variable and select Remove Selected Forces.
➢ To remove all forced values: right-click anywhere inside the Forced Variables dialog box and select Remove All
Forces.
➢ To display the Global Variables window: from the Component Editor View menu, select Global Variables.
The Global Variables window allows you to modify a property for multiple variables. For example, to move multiple
variables onto an EGD page, select the rows for the desired variables and change the EGD Page property in the Property
Editor. (Refer to the
section Data Grids.)
Because only existing global variables can be changed, new variables cannot be added from the Global Variables window.
You cannot make any change that affects the name of the global variable (like Name or Global Name Prefix). Most properties
of variables that are instanced from a library can only be modified by using the Overridable Properties feature. (Refer to the
section Overridable Properties.)
Select from the Available Attributes table using the arrows to add them to or remove them from the
Selected Attribute table. Click Export to export alarms for Rationalization.
GE Rationalization is an available selection for export (as displayed in this figure). However, it is only available for
backwards compatibility.
Note The GE Rationalization report contains a column for Parent Alarms and for Child Alarms. A large number of
parent/child relationships can cause these two columns in the .csv file to be incompatible with the Excel application. The
application allows a maximum limit of 32,767 characters in a cell.
When a GE Rationalization report is generated, it can be saved as a .csv file, modified, and then imported back into the
ToolboxST application. For the procedures to export and import GE Rationalization reports, refer to the section Export and
Import Reports.
➢ To import alarms to the library: from the System Editor Tree View, open the Library Container Editor.
The report displays all variables found in the library; variables missing from the library display in red. It is possible to
re-export the report to include all rows not found during the original import.
➢ To import the report back into the controller: from the controller File menu, select Import and GE
Rationalization Report.
The report automatically overrides properties in the controller configuration to change the linked library code.
➢ To open a stand-alone Watch Window: from the Start menu, select All Programs, GE ControlST, ToolboxST,
and Watch Window.
➢ To create a Watch Window: from the System Editor Tree View, right-click the system and select Insert New,
Tool and Watch Window.
Enter a Name,
and a Description
(optional), and
click OK.
Note If this Watch Window is being opened for the first time, the list is empty. Add or import a new Watch Window.
➢ To open an existing Watch Window: from the System Editor Tree View, right-click the system and select Insert
Existing and Watch Window.
➢ To open a Watch Window: from a Component Editor View menu, select Watch Windows.
If you selected
System
Component in the
previous page,
select the desired
component from
the drop-down list
and click Next.
The variables
will display here.
Click Finish .
Once a variable is added to a Watch Window, right-click the variable row header to perform the following actions:
Note When a system component providing signals to a Watch Window is replicated, the Watch Window is replicated as
well.
Forcing of protective functions is never permissible for an operating unit. All safety
Warning measures should be strictly enforced in conjunction with this procedure.
Note The Watch Window tool only exports grid columns necessary to retrieve variable information. For example,
DatasourceName from the exported file is used to retrieve the variable’s remaining properties from the system. User-defined
columns such as User Comment are also included.
➢ To save a Watch Window: from the <Watch Window name> File menu, select Save As to save the Watch Window
as a .watch file in a user-selected location,
or select Save to save the Watch Window as a .watch file in the Tools folder in the system.
6.29 LiveView
The LiveView feature allows you to display a graphical representation of live data from various sources in the system.
LiveViews can be added to a ToolboxST system, to a component, or opened as a standalone editor.
➢ To add an existing LiveView: from the System Editor, right-click the system and select Insert Existing and
LiveView.
➢ To edit a LiveView: from the System Editor, right-click a LiveView and select Edit System Component.
➢ To add a LiveView from a Component Editor: from the View menu, select LiveViews.
Reference point
Select a Bar
Color for the
High Alarm and
High Warning
range above the
reference point
Select a Bar
Color for the
Normal range
above the
reference point
Select a Bar
Color for the
Low Alarm and
Low Warning
range above the
reference point
If the Behavior
property is set to
Momentary and
the On Push
property is set to
False, the state of
the attached
variable is set to
True when the left-
mouse button is
clicked
Locked enables
or disables the
ability to move
and resize objects
Locked Property
Or
Variables display
here. Click
Finish
Note You can also attach a variable by entering the variable name in the Property View.
➢ To display constants
The Reconcile Differences dialog box displays constants with both initial and live values.
• For constants when the ToolboxST initial value was checked, that value is either sent to the controller (where the OK
button is clicked), or a pcode record is created, causing the next online download to change both the initial and live
values.
• For constants when the live value was checked, the ToolboxST initial value is set equal to the controller live value. This
causes a minor revision configuration change to Not Equal. A Build and Download to the controller is required to
complete the reconcile function.
➢ To display I/O values: from the Hardware tab, select an I/O module.
➢ To connect to a controller
1. From the System Editor, open an Mark VIe Component Editor.
2. From the Device menu, select Online or click Go On/Offline.
If you are connecting to a simplex controller, a connection is automatically established with the M1 controller. In a Warm
backup or Dual configuration, a dialog box displays to select either a redundant controller (either M1 or M2) or the controller
currently designated as the supplier of initialization data.
Icons Conditions
All controllers functioning normally.
• Adding the first I/O pack to a controller, removing the last I/O module, or deleting all I/O modules
• Compressing variables
• Compress non-volatile RAM (NovRAM)
• Changing the background blockware period
• Changing frame rate
• Changing controller redundancy
• Changing IONet network redundancy
• Changing the platform type
• Changing any NTP configuration
• Changing any controller Network Adapter IP addresses, subnet mask, gateway IP address, scope, media, or transport
• Delete or rename a Network Adapter that the controller was using
• Adding or redirecting optional block library references
• Changing Frame state timeouts
• Removing last point off Modbus slave
• Marking the first I/O module to be shared or clearing the last I/O module from being shared
• Connecting the first controller-to-controller input or output variable
• If the set index of shared IONet changes
• If the controller was set to multicast mode on IONet but an I/O pack that does not support multicast as added, which
resets the configuration back to broadcast mode
• Adding the first FOUNDATION Fieldbus linking device, removing the last FOUNDATION Fieldbus device, or removing all
FOUNDATION Fieldbus devices
• Removing Wind Condition Top Box Monitor (WCBM)
• Disabling web pages
• Disabling compressed data log
• Disabling Wind Farm Management system
Note When the user certificate expires, refer to the SecurityST* Cyber Security Management System Maintenance Guide
(GEH-6765) for the renewal procedure.
A second server, called a Remote System log (RSyslog), logs all security-related events. To send security-related messages, a
controller must know the IP address of the RSyslog. The RSyslog also receives security-related messages from the
ToolboxST application. Examples of data collected by the RSyslog include:
For dual and TMR configurations, select Go to Secure for each controller.
Attention
Note When the process is in the Authenticated state, the controller is retrieving a certificate revocation list from the CA
Server to verify that the requestor has a valid certificate.
The Component Info View Status tab displays the Security state for each configured controller.
A controller cannot communicate on a network until these controller setup tasks are
completed.
Attention
Prerequisites
Note If using a Shared IONet system, repeat the procedures in this section for both the Mark VIe and VIeS components (or
Mark VIe and MarkStat components).
➢ To change redundancy
1. From the General tab Tree View, select General.
2. From the Property Editor, select Redundancy, and from the drop-down list select the correct option to match the
installed controller hardware (simplex, dual, or TMR). The Summary View displays the set of controllers for the
redundancy selected (one, two, or three).
3. From the Hardware tab, set the Network Redundancy to indicate the number of IONet networks (simplex, dual, or
TMR) that are used with this set of controller(s). Refer to GEH-6721_Vol_I for more information on redundancy options.
4. Click to save the change. From the Component InfoView, the Log tab displays status information.
Note The default IP address is used as an example in this procedure. Because the default IP address assigned to the first
controller is 192.168.101.111, the UDH Ethernet port on the computer running the ToolboxST application must be assigned
an address in the same subnet, or 192.168.101.xxx, where xxx is in the range 002 to 255 (except the addresses used by the
controllers).
1. From the Start menu, select Control Panel and Network and Sharing Center.
Select Change
adapter settings to
display the network
connections for the
computer.
Note Administrator privileges are required to access the Properties dialog box.
From the
Networking
tab, select
Internet
Protocol
Version 4
(TCP/IPv4),
then click
Properties.
In the IP address
field, enter
192.168.101.11,
then confirm the
Subnet mask
255.255.255.0.
3. Set the correct SubnetMask for the site UDH network. The
default subnet mask is 255.255.255.0.
1. From the System Editor, double-click the controller set to open the Component
Editor.
2. From the General tab Tree View, select Network Adapter 0. The Property
Editor displays the Network as UDH, the Host Name for this device on the
network, and the IP Address. The default IP address assigned to the first
controller in the system is 192.168.101.111. For TMR controllers, this address is
assigned to R controller, with 192.168.101.112 assigned to S controller, and
192.168.101.113 assigned to T.
3. Enter the new IP address for the R controller. If using redundant controllers,
their IP addresses are automatically updated along with the change to the R
controller.
• The control system hardware and network cabling have been connected properly
• All system equipment has been successfully powered on
• The controller has been added to the system with the correct redundancy
If this is a new UCSB controller received directly from the factory, or a UCSB that has
not been previously configured, the IP address must be set using a USB flash device.
Skip to step b in this procedure.
Attention
ii. Connect an RJ-45 serial cable adapter from the main board of the controller to a serial port on your computer:
i. Insert a non-encrypted removable USB 2.0 (only) flash device with a 4 GB minimum capacity into the HMI
computer USB port.
ii. Initialize the controller.
iii. Remove the USB flash device from the USB port of the HMI computer, then click Finish.
iv. Remove power from the controller.
v. Insert the USB flash device into the controller. For a UCSB, press and hold in the Backup/Restore button. For
a UCSC, press and hold the PHY PRES button.
Note Refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose Applications System
Manual (GEH-6721_Vol_II), the sections UCSC Restore and UCSB Backup and Restore for these procedures.
i. Apply power to the controller while continuing to press the button until the On LED on the front of the
controller becomes solid green, then release the button. The On LED turns off when the process is complete.
ii. Remove power from the controller, remove the USB flash device, then re-apply power to the controller.
iii. If using redundant controllers, repeat this procedure for the S and T controllers (if TMR) or S (if dual). Be sure
to select the correct Channel.
• The control system hardware and network cabling have been connected properly
• All system equipment has been successfully powered on.
• The controller has been added to the system with the correct redundancy
• The computer that runs the ToolboxST application and the controllers must be configured to be on the same subnet for
UDH Ethernet communication.
Use one of the following methods to configure the TCP/IP address of the UCCA / UCCC / UCSA controller for
communication on the UDH Ethernet network.
ii. Connect a serial cable adapter from the main board of the controller to a serial port on your computer:
iii. Click Next to continue.
iv. The Controller Setup Wizard displays the progress of the connection. When it is complete, click Finish.
v. Disconnect the Ethernet cable from the replacement controller’s COM port, and disconnect the serial adapter
from the engineering workstation.
vi. After the controller has restarted, verify the status of the controller. It should be online, in the controlling state,
with no warnings or errors. If the controller cannot go online, or the replacement controller does not go to the
controlling state, download to the controller.
vii. Configure the replacement controller and/or set of controllers with the site-specific Mark VIe controller
password. Refer to the section Controller Password Change for further instructions.
Note From a Windows 7 computer, run the ToolboxST application as an Administrator to format a CompactFlash card.
6. From the Controller Setup Wizard, click Write to format the CompactFlash.
7. Verify that the CompactFlash download completed successfully message displays, then click Finish.
8. Insert the CompactFlash into the controller.
9. Apply power to the controller ( red boot LED should flash at 1 Hz).
10. If the Mark VIe control interfaces with a SecurityST platform that is utilizing MAC filtering, update the MAC filtering to
account for the new controller core (as appropriate) per SecurityST guidelines and procedures.
11. After the controller has restarted, verify the status of the controller. It should be online, in the controlling state, with no
warnings or errors. If the controller cannot go online, or the replacement controller does not go to the controlling state,
download to the controller.
12. Repeat this procedure for each controller (if using a redundant controller set). Be sure to select the correct Channel that
matches the redundant controller.
The user must change the factory default controller password for a device. The
maximum number of characters for the new password is limited to characters. The
new password cannot be the factory default password. If you do not know the factory
default password, contact the nearest GE Sales or Service Office, or an authorized GE
Sales Representative.
Attention For additional details, refer to Mark VIe and Mark VIeS Control Systems Volume II:
General-purpose Applications, GEH-6721_Vol_II, the chapter Controller Diagnostic
Alarms, alarm 547.
Note For a device configured with redundant controllers, the password applies to all controllers in that device.
Note This password is required for configuring the network address during controller setup.
When the password for the replacement controller is successfully synchronized to the other controller passwords in the set, a
message displays in the Log window.
• Boot Loader starts the operating system for the controller and I/O modules, much like the BIOS on a desktop computer.
Changes to the boot loader are very infrequent.
Note Not all devices have the boot loader. In this case, the boot loader is contained within the base load.
Base Load contains the operating system for the controller and I/O modules. While changes to the base load are more
likely than changes to the boot loader, they still occur infrequently.
• Firmware provides the functionality of the controller and I/O modules. It can be updated over the lifetime of the
controller to incorporate new features and bug fixes.
• Application Code contains the configuration of the controller as created in the ToolboxST application. Whenever a
change is made to the configuration, the application code must be downloaded. There are two types of application code
download: online and offline. An online download (very commonly performed) changes the configuration without
interrupting control and the new configuration takes effect between control frames. An offline download requires a
controller restart (performed less frequently).
• Parameters contain specific configuration for the I/O modules.
Boot loader, base load, firmware, offline application code downloads, and parameter
downloads all require the target device to be restarted. Before downloading new
software to a controller, take the necessary steps to secure the control equipment to
prevent equipment damage and personal injury.
Warning
Note The type of software download needed is determined by which changes have been made to the controller
configuration.
The Download Wizard is used to download software to a Mark VIe component and its distributed I/O modules over an
Ethernet connection. The Download Wizard can automatically examine the system configuration to locate out-of-date
software, or you can manually select individual items to download.
Note Certain conditions do not allow a download, such as an incorrect platform type. Check the Component InfoView for
errors that may prohibit a download.
1. Disable the I/O modules from the configuration. It can be easier to download to the I/O modules after the controller is
successfully online.
From the
Component
Editor Hardware
tab, select all I/O
modules
2. From the toolbar, click the Build icon. From the Component InfoView Log tab, verify that there are no errors or
resolve issues before proceeding.
3. From the Component Editor Device menu, select Download and Download Wizard.
Or, from the toolbar, click the Download icon.
Note You can perform a Download without performing the Build command. However, if you have changed
configuration settings since the last Build operation, a message box indicates that the software is out of date. Click Yes to
build the current configuration.
If a change occurred that requires a restart of the controller, a wizard page displays with a Restart Controller after
Download check box selected.
5. When the download has completed, click Finish.
6. Repeat this procedure as needed until the configurations display as equal from the Build.
7. From the toolbar, click the Go On/Offline icon to go online with the controller.
If the configuration being downloaded contains I/O packs with IDs that are different
from the currently running configuration, incorrect firmware can be installed to some
I/O packs. If this occurs, confirm that the controller is running the new configuration,
restart the entire system, then restart the ToolboxST Download Wizard.
Attention
The APP_STATE block can prohibit a download and restart of the controller.
Attention
If the DOWNLOAD_OK input of the APP_STATE block is set to True, all downloads are allowed. If this value is set to
False, all downloads (except Update DDR and Device Backup) are prohibited. This condition also applies to an attempted
download of an I/O pack from the Hardware tab of the Component Editor. If the download is prohibited, a warning displays in
the Component InfoView, and the Download Mark VIe Controller wizard displays the prohibited download. For additional
information on the APP_State block, refer to the Mark VIe Controller Standard Block Library Instruction Guide
(GEI-100682).
➢ To update the DDR: from the Device menu, select Update Dynamic Data Recorder and follow the instructions
on the ToolboxST windows.
➢ To view and set the controller time: from the Device menu, select View/Set Time... and follow the instructions
on the ToolboxST windows.
➢ To back up files to the controller: from the Device menu, select Download, then select Backup Files to
Controller.
Note The UCSC, as shipped from the factory, does not include the software on the controller to support communication
from the PHY PRES button to the EFA. The user needs to download to the controller at least once (using ToolboxST) to
enable this.
➢ To display Controller Diagnostics: from the View menu, select Diagnostics and Controller Diagnostics.
Message
time stamp
Message
fault code
Message
status
(0=inactive;
1=active)
Message
description
The Controller Advanced Diagnostics View displays additional information from the controller.
➢ To display Advanced Diagnostics: from the View menu, select Diagnostics and Controller Advanced
Diagnostics.
The I/O Diagnostics View displays diagnostic messages for a component’s hardware I/O module. Retrieve these messages to
diagnose problems with hardware I/O.
➢ To open the I/O Diagnostics view: from the View menu, select Diagnostics and I/O Diagnostics.
Note For more information, refer to the section I/O Diagnostic Viewer.
Note Before modifying Totalizer values in a redundant controller, connect to the R controller and make sure all other
redundant controllers are healthy and communicating. (Refer to the section Connect to a Controller.)
Note Totalizer passwords are specific to the connected redundant controller (R, S, or T) and cannot be used on other
controllers.
Note Totalizer passwords are usually valid for 24 hours from time of creation.
2. From the Modify Totalizer Value dialog box, enter the new value and click OK.
3. From the Add SFC dialog box, enter a name for the SFC and click OK.
Mark VIe Sequential Function Chart (SFC) GEH-6700AG User Guide 553
GE Internal
When the SFC is created, the Initial Step is already defined.
From the Logic Editor, you can configure the properties and edit the SFC.
From the Tree View, click the new From the toolbar, click Edit SFC
sfc to display the SFC Logic Editor to make changes to the logic
Note Most SFC property settings can be exported to an .xml file that can be modified in a text editor and imported into other
SFCs. For further details on the import and export options, refer to the section SFC Content Menu.
Mark VIe Sequential Function Chart (SFC) GEH-6700AG User Guide 555
GE Internal
8.1.3 SFC Context Menu
The SFC context menu displays the available editing commands for an SFC.
➢ To display the SFC context menu: right-click anywhere in the SFC diagram.
Note When in editing mode, the Edit SFC button displays as Editing SFC, and additional buttons are displayed on the
toolbar.
SFC Toolbar
Toolbar Buttons
Button Name and Icon Description of Use
Change the orientation and size of the SFC diagram. When printed, the diagram is scaled
Virtual Paper Size and/or rotated to the printer’s paper size.
Mark VIe Sequential Function Chart (SFC) GEH-6700AG User Guide 557
GE Internal
Toolbar Buttons (continued)
Button Name and Icon Description of Use
Note The Active and Finished fields indicate the status of the Action.
Action Qualifiers
Qualifier Description
N The Action runs every frame that the Step is Active.
The Action runs for a specific number of ms while the Step is Active, indicated by the Time value, then
L
stops running.
The Action does not run until the number of ms indicated by the Time value has been reached, after
D
which the Action runs every frame the Step is Active.
P The Action runs only once and is triggered by a rising edge on the Action’s Pulse Input.
L and D Action Qualifiers: a Time value, either a reference variable or an immediate value, must be specified in the Time
column for the Action.
P Action Qualifier: a Pulse Input Boolean value must be specified in the Pulse Input column for the Action.
By default, a PERMIT block is automatically created in a new Transition. The output of the PERMIT is connected to the
Transition_Condition_Value, and any conditions for the Transition can be connected to the PERMIT’s inputs.
The PERMIT standardizes the Transition conditions so that HMI screens have a common method to display information about
Transitions.
Mark VIe Sequential Function Chart (SFC) GEH-6700AG User Guide 559
GE Internal
➢ To define an Action’s logic: from the SFC toolbar, click the Selection Tool and double-click a step.
An Action can be authored in Terms of Blockware in the logic sheet.
Note Always connect the Action_Finished local variable to a Boolean expression. The Action_Finished variable enables the
Actions of Interest feature to know that the Action has finished its operation. This is recommended even if the application
does not use Actions of Interest.
➢ To define a Transition’s condition logic: from the toolbar, click the Selection Tool and double-click a
Transition.
A Transition Condition can be authored in Terms of Blockware.
Note Always connect the Transition_Condition_Value local variable to the result of the Transition Condition Boolean
expression. The Transition_Condition_Value variable enables the SFC to progress if the Transition Condition Value evaluates
True when the Transition is Active.
➢ To use a Step’s Action of Interest status in a Transition condition: from the toolbar, click the Selection Tool
and double-click a Transition.
Using a Transition condition’s Boolean expression, such as defining whether or not the configured Actions of Interest for the
Initial Step have been completed, add a Move block whose source (SRC) pin is the MySFC.Initial_Actions_Of_Interest_
Status global variable and whose destination (DEST) pin is the Transition_Condition_Value local variable.
A Step’s Action of Interest Status is referenced from a Transition Condition.
Mark VIe Sequential Function Chart (SFC) GEH-6700AG User Guide 561
GE Internal
8.1.8 Add End Transition
➢ To add an End Transition
1. From the toolbar, click End SFC Transition Drawing Tool.
2. Move the cursor to the SFC logic sheet to place the End Transition. Enter a name and click OK.
Mark VIe Sequential Function Chart (SFC) GEH-6700AG User Guide 563
GE Internal
8.1.9 Variable Connections
There are several required variable connections when defining SFCs in the ToolboxST application. For example:
• When defining a Transition’s Transition Condition, always connect the Boolean expression’s output to the Transition_
Condition_Value local variable. This enables the Transition to progress.
• When defining a Step’s Action Logic, always connect a Boolean expression to the Action_Finished local variable. This
enables Actions of Interest Control to be used in the SFC by having the Action state when it has finished. This is
recommended even if Actions of Interest Control is not being used in the application. It makes using the Actions of
Interest Control feature in the application much easier later in development if needed.
3. In the property grid, enter the free-form text and configure the properties for the text shape:
Note Text shapes can also by created by pasting text from another application such as Microsoft Word or Excel.
3. In the property grid, configure the Geometric Shape properties for the shape:
Mark VIe Sequential Function Chart (SFC) GEH-6700AG User Guide 565
GE Internal
• Fill Color: select the fill color for the shape.
• Geometric Shape: select a shape (Rectangle, Ellipse,
or Line)
• Is Filled: set to True to fill the shape with color, or
False for no fill color.
• Line Color: select a color for the shape line.
• Line Thickness: select the line thickness.
Unlike a free-form text shape, the Description text’s position is relative to the Step or Transition to which it is linked, and
moves with it. However, you can resize or move the text relative to the Step or Transition, and adjust the font and colors.
When the Description text is selected, a tooltip hint identifies the link.
Mark VIe Sequential Function Chart (SFC) GEH-6700AG User Guide 567
GE Internal
8.1.14 Display Transition Condition Logic in Description
The Description property of a Transition can be set to include a substitution string, {TransitionCondition}, that will be
replaced with a descriptive textual representation (equation) of the transition condition logic in that transition. For example, a
transition driven by a Rung block as follows:
Not all Transition Condition logic can be displayed as text. The equation strings are limited to four block types that can drive
the transition condition:
• LOGIC_BUILDER
• LOGIC_BUILDER_SC
• RUNG
• MOVE
• PERMIT
All other blocks will display (custom logic) in the equation.
Inputs (to the supported block types) must be Named variables. For example, in the illustration used for a transition driven by
a Rung block above, the D input of the Rung is connected to an unnamed pin, AND_1.OUT, so (custom logic) is displayed for
that input in the description equation.
Since the description substitutes the {TransitionCondition}, you can build up more descriptive strings. For example, Wait for
the tank to fill ({TransitionCondition}) would display as Wait for the tank to fill (TankFull OR TankFillFailed).
➢ To select the virtual paper size: from the SFC toolbar, click the Virtual Paper Size icon and select the size from
the drop-down menu (check mark displays next to the selected item).
Mark VIe Sequential Function Chart (SFC) GEH-6700AG User Guide 569
GE Internal
8.2 Online Operations
➢ To run an SFC in a controller from the ToolboxST application
1. From the Mark VIe Component Editor, go online with the controller.
2. From the Software tab Tree View, select the SFC item to open the logic sheet.
3. From the tool bar, click Run the SFC.
4. To pause the SFC, click Pause to display the Pause SFC dialog box and click OK.
➢ To reset an SFC back to its Initial Step: from the toolbar, click Reset to display the Reset SFC dialog box and
click OK. The reset Initial Step displays green.
Attention
Note When the SFC is placed into Single Step Mode, all Implicit Holds are removed from Transitions, and previously set
Operator Holds are restored.
2. To remove an Operator Hold, right-click on Transition and select Remove HOLD from Transition.
➢ To acknowledge a HOLD applied to a Transition: from the logic sheet, right-click the Transition that has a
HOLD applied and select Acknowledge Hold.
Note If the Transition Condition for Trans1 was set to True at the time the HOLD was acknowledged, the SFC would
continue.
➢ To apply a FORCE to a Transition: from the logic sheet, right-click the Transition and select Force Transition.
Mark VIe Sequential Function Chart (SFC) GEH-6700AG User Guide 571
GE Internal
8.3 Publish SFC on EGD Page
An SFC’s Control and Monitor interface, which can be placed on an EGD page, includes:
• Run
• Reset
• Transition Hold
• Transition Hold Acknowledge
• Transition Force variables
In addition, the SFC’s Step Active Flags, Transition Active Flags, and Transition Condition Value are placed onto EGD
automatically.
You have the option to place items from the SFC Monitor Interface on EGD. These items include Action of Interest Status,
Transition Progression Status, and Step Active Times variables. By default, the Step Active Times are automatically placed on
EGD in the ToolboxST application.
➢ To place an SFC and its Control Interface on EGD: from the Software tab Tree View, select an SFC.
To remove the
SFC from EGD,
from the drop-
down list, select
the blank entry
Mark VIe Sequential Function Chart (SFC) GEH-6700AG User Guide 573
GE Internal
Notes
Note For additional information, refer to the Mark VIe Control FOUNDATION Fieldbus Interface Application Guide
(GEH-6761), the section System Parameters.
Note A major difference occurs when adding the first linking device and requires a restart-required load. Any linking device
added after that is a minor difference and only requires an online load. A major difference also occurs when removing the last
linking device and requires a restart-required load. Any linking device removed other than the last one is a minor difference
and only requires an online load.
Note The Physical Device (PD) tag is a unique, configurable, system dependent name for the device.
Tip � The DeviceID can be entered directly or searched for by using the ellipsis (…) mechanism.
9. In the Configure Device section, from the HW Form drop-down list, leave the default as H1B or select H1A for LDEvR
(Simplex). Repeat for LDevS for a HotBackup configuration.
10. From the LAN Port drop-down list, leave the default as IONet1 or select IONet2 for LDEvR (Simplex). Repeat for
LDevS for a HotBackup configuration (default is IONet 2).
11. From the Position drop-down list, leave the default position as 24 (ToolboxST) or enter another position number for
LDEvR (Simplex). Repeat for LDevS for a HotBackup configuration (default ToolboxST Position is 231).
12. Click Next to continue.
13. Review the configuration summary, then click Finish to add the module.
Port Properties
Property Description
Identification
Name Name of the selected port
Port Number Number of the port
Port Type Type of port
4. From the Tree View, right-click the Port and select Attach Segment from the shortcut menu.
➢ To configure an attached segment macrocycle: from the System Editor Tree View, double-click the Mark
VIe component (such as FF3) to display the Component Editor.
Note The desired macrocycle time must be in multiples of the controller’s frame rate to which the segment’s linking device
belongs.
• A generic fieldbus function block is assigned to a fieldbus device placeholder in the segment.
• An assigned fieldbus function block is unassigned from a fieldbus device placeholder in the segment.
The ToolboxST application updates the selected macrocycle time when the desired macrocycle time is updated.
When running at a 320 microsecond macrocycle, input health may be impacted under certain instances. Any failure that
results in the secondary PFFA switching to the primary PFFA may result in missed data for up to and including three
macrocycles. During this period of time, the status can go to UNCERTAIN. This should be accounted for in the application
design when using 320 microsecond macrocycle segments. Events that cause the PFFA to switch are as follows:
• View which assigned fieldbus function blocks will execute at what time during the macrocycle.
• View time allotted during the unscheduled portion of the macrocycle for the reading of views of assigned fieldbus
function blocks configured for placement on EGD.
• Refresh the macrocycle timeline view by invoking a method which recalculates the macrocycle timeline calculation
algorithm.
• Switch to view a different segment’s macrocycle timeline.
• Print the displayed macrocycle view
• Summary
• Link Settings
• Link Master Information
• System Management Information
➢ To display the attached segment Summary View: from the ToolboxST System Editor Tree View, double-click
the Mark VIe component (FF3) to display the Component Editor.
The Summary tab displays the linking device, attached segment, and any attached H1 devices. The parameters displayed on
the other tabs provide additional configuration options for the linking device and the segments attached to it.
Note All devices connected to a segment must be deleted before a segment can be detached.
Tip � A linking device can be deleted from the Hardware tab Tree View. This causes all segments to detach under the linking
device.
➢ To restore segment defaults: from the ToolboxST System Editor Tree View, double click the Mark VIe
component (such as FF3) to display the Component Editor.
Click Close .
Note The .cff file determines which DD files (.ffo, .ff5, .sym, or .sy5) for a device are imported.
Imported DD files can be viewed in the ToolboxST application’s System Editor and in the controller Component Editor from
the View menu using the FOUNDATION Fieldbus DD Manager. They also display during the Add H1 Field Device process which
uses the FOUNDATION Fieldbus DD Manager. The FOUNDATION Fieldbus DD Manager displays the DD files in the DD Importer
dialog box.
If you delete an H1 device that has associated blockware, perform a build of the
controller before you insert a new H1 device on the segment. This build will result in
errors if there are any function blocks on the Software tab that were assigned to the
H1 device that was deleted. These function blocks either need to be deleted or
unassigned and re-assigned to another H1 device block on that segment before a
successful build will occur. If these blocks are not unassigned and re-assigned, then
Attention there is a possibility that an inserted H1 device will generate the PDTags necessary for
the blockware to assume that the original H1 device is present and it will not rebuild
the macrocycle. This could potentially lead to build and download errors.
➢ To instance a fieldbus device placeholder: from the ToolboxST System Editor Tree View, double-click the
Mark VIe component (such as FF3) to display the Component Editor.
Click Next .
Click Next .
Click Finish.
– If the fieldbus device is not in the Live List, a red X ( ) displays, the fieldbus
device is not online
Note When a fieldbus device is added to a system, it acts as a placeholder until it is commissioned. The commissioning
process makes the fieldbus device live and active in the system.
The ToolboxST application classifies a fieldbus device in one of the following states:
• Uninitialized State
− Fieldbus device does not have a PD_TAG
− Fieldbus device does not have a permanent node address
– Overlay symbol:
• Initialized State
− Fieldbus device has a PD_TAG
− Fieldbus device does not have a permanent node address
− Fieldbus device revisions match placeholder revisions
– Overlay symbol:
• Commissioned State
− Fieldbus device has a PD_TAG
− Fieldbus device has a permanent node address
– Overlay symbol:
• Mismatch State
− Fieldbus device revisions have not been obtained. Check for a communications failure diagnostic to determine if
there is a problem or if it is just taking a while to update.
− Fieldbus device revisions do not match the placeholder revisions. Re-add the placeholder using a DD file matching
the revisions.
− Fieldbus device has a node address collision with a fieldbus device placeholder of a different type
− Fieldbus device has a node address that does not exist in the ToolboxST configuration
− No DD files are available for the fieldbus device in the ToolboxST DD file database
– Overlay symbol:
From the Hardware tab Tree View , select the fieldbus device placeholder
[3051 (PFFA-21_1_20 )] to display the device in the Summary View .
• XD_CAL_DATE
• XD_CAL_LOC
• XD_CAL_WHO
• (Manufacturer-specific calibration values)
Note A host that conforms to a specification level that precedes the addition of this capability will likely ignore this
capability and may download parameters that are listed in the no_download collection. Such a host may support a
non-FF-standard mechanism to prevent download of certain parameters.
➢ To view or edit device level blocks: from the ToolboxST System Editor Tree View, double-click the Mark VIe
component (such as FF3) to display the Component Editor.
Context menu It is typically a root menu that pops up on the right-click of the device tree node or block node under the
device.
• Graphs
A graph is used to display a data set that is stored in a device. The main user interface elements of a graph are the X and Y
axis, the waveforms, and the legends.
• Charts
A chart is used to display continuous data values from the device. The main user interface elements of a chart are the X and Y
axis, the waveforms, and the legends.
• Image
The image displays the graphic image on the Menu window.
• Method
A method defines a set of actions to be performed by the host. Methods are a collection of statements that come as scripts in
the DD file given by the device developer. The execution of methods can lead to offline configuration changes or online
parameter value changes. The method wizard in the host application UI allows the user to run the methods step-by-step and
also allows the user to see the messages being sent out by the device to the host. The wizard also has the option of logging all
the messages that were sent back by the device.
Click OK .
2. The Hardware tab Tree View is updated, along with the internal data model, removing the instantiated block.
• Resource block
• Transducer blocks by block tag
• Function blocks by profile ID then by block tag
Note The ToolboxST application ensures that all tag names are mutually exclusive throughout a Mark VIe component,
which means all PD tags and block tags are mutually exclusive of each other as well.
➢ To create a Special Fieldbus Task in a Mark VIe component: from the ToolboxST System Editor Tree View,
double-click the Mark VIe component (such as FF3) to display the Component Editor.
Click OK .
While creating a special fieldbus task inside a library, the following can be performed:
➢ To instance a generic fieldbus function block into a special fieldbus task: from the ToolboxST System
Editor Tree View: double-click the Mark VIe component (such as FF3) to display the Component Editor.
Arithmetic FF_AR
Integrator FF_IT
Multiple Analog
FF_MAI
Input
Multiple Analog
FF_MAO
Output
Multiple Discrete
FF_MDI
Input
Multiple Discrete
FF_MDO
Output
P, PD Controller FF_PD
Signal
FF_SC
Characterizer
Setpoint Ramp
FF_SPG
Generator
Timer FF_TMR
Unassigned Unassigned
➢ To assign a generic fieldbus function block to a fieldbus device placeholder: from the ToolboxST System
Editor Tree View, double-click the Mark VIe component (FF3) to display the Component Editor.
From the Software tab Tree View , expand and select a task ( Fieldbus),
the attached blocks display in the Tree View and Summary View .
Tip � The ToolboxST application only displays linking devices, attached segments, and fieldbus device placeholders which
contain the same type of generic fieldbus function block (AO in this example) trying to be assigned, to filter the selection
paths for the user.
Tip � Only the set of parameters that exist in both the previous generic fieldbus function block and the newly assigned
fieldbus function block retain their configured values when being changed from a generic fieldbus function block to an
assigned fieldbus function block.
• The PD tag of the fieldbus device placeholder that the block was assigned to displays (in blue) in the Software tab
Summary View with the fieldbus function block.
• An operational icon (such as ) replaces the question mark icon ( ) in the upper right-hand corner of the
fieldbus function block display.
• The fieldbus task’s execution rate is updated and displays in the Software tab Property Editor.
• The ToolboxST application updates the object model to indicate the current fieldbus task is associated with the segment
that owns the newly assigned fieldbus function block.
➢ To unassign a fieldbus function block from a fieldbus device placeholder: from the ToolboxST System
Editor Tree View, double-click the Mark VIe component (such as FF3) to display the Component Editor.
The block is
unassigned .
• The PD tag of the fieldbus device placeholder which the block was assigned to is replaced with Unassigned in black.
• The operational icon (such as ) is replaced with the question mark icon
( ).
• The fieldbus task’s execution rate is updated and displays in the Software tab Property Editor.
• The ToolboxST application updates the object model to indicate the fieldbus task is no longer associated with the
segment that owns the unassigned fieldbus function block.
connected) by using the standard wiring tool ( ) or the drag-and-drop features that exist in the ToolboxST application.
The following are examples of connections in a fieldbus task:
Fieldbus Function Block to Mark VIe Function Block to Fieldbus Function Block Connection
➢ To place a fieldbus function block on EGD: from the ToolboxST System Editor Tree View, double-click the
Mark VIe component (FF3) to display the Component Editor.
Fieldbus Alarm Parameters (ending with _ALM) Properties in Software Tab Property Editor
Section Property Description
The value assigned when the alarm is in the active state. Used for filtering and
display in the WorkstationST Alarm Viewer. Valid range is 1-1000 where 1 is the
Active Severity
least severe. The range and usage is defined by OPC® for use in OPC AE
clients and servers.
For a Boolean variable, select the Alarmed string to make the variable an alarm.
Alarm
For an analog variable, select an alarm definition.
Alarm Class Select a System Configured Alarm Class
Alarm Inhibit Group Select the Alarm Inhibit Group for the alarm variable
Alarm On Zero Set to True to cause the alarm on a 1 to 0 transition. Requires Alarm = True
Alarms and Events Event Set to True to enable the variable as an Event.
Hold Set to True to enable the variable as a Hold.
The value assigned when the alarm is in the normal state. Used for filtering and
display in the WorkstationST Alarm Viewer. Valid range is 1-1000 where 1 is the
Normal Severity
least severe. Range and usage are defined by OPC for use in OPC AE clients
and servers.
Used to group variables into logical plant groupings for display in the
Plant Area WorkstationST Alarm Viewer. This is used instead of the HMI Resource due to
string length limitations.
SOE Description Description used for SOE.
Note The tabs are vendor-dependent, so not all of these tabs may display for a device.
• Acknowledge
• Silence and Unsilence
• Lock
• Unlock
• Reset
• Filtering
− By fieldbus and non-fieldbus
− By fieldbus process alarm versus fieldbus device alert
− By device
− By plant area
Note Unacknowledged behavior is not supported because the state machine inside fieldbus devices does not support this
function.
Note Fieldbus Device Alerts (unlike ControlST Boolean alarms, Analog Alarms, Events, and Holds) are not available in
application code, meaning application code cannot be triggered to run when a Fieldbus Device Alert occurs. The Fieldbus
Device Alerts are available for online view and interaction from HMIs, Maintenance Workstations, and third-party software
through OPC AE Server, GSM Server, and WorkstationST Alarm Viewer.
Note To display or otherwise configure the FOUNDATION fieldbus alerts, they must be enabled in the H1 device.
To use the device alerts they must be added to the application code (FOUNDATION fieldbus task).
4. From the tool bar, click the Download button to download the controller and the H1 device.
Note Downloading directly to the H1 device is not allowed (different from an I/O pack).
• Device
• Library Container
• Watch Window
• Live View
• FF Configuration
• Global Variable Report
• Block Pin Report
• Programs
• Trender Data
• Primary and Second Language Descriptions
After the import:
• The Unknown icon displays for any fieldbus device placeholder for which DD files cannot be found.
• A previously assigned fieldbus function block in a fieldbus task becomes unassigned if the fieldbus device placeholder is
not found
Note The imported device does not bring along the DD files it referenced.
Note This feature currently supports a one-to-multiple import; however, the user has to multi-select the individual target H1
devices for import. This is currently limited to a per-segment multi-select function.
Note All parameters in a FOUNDATION fieldbus H1 device have a default value. Currently, the only parameters included in the
exported .xml template file are parameters that have had their default values changed. Any exported parameters with a default
value on the H1 device will not be written into target H1 devices upon import.
For example:
FOUNDATION fieldbus Device 1, TAG_DESCRIPTION = “ ”
FOUNDATION fieldbus Device 2, TAG_DESCRIPTION = “FF Device 2 Tag”
FOUNDATION fieldbus Device 1 (device being exported) did not change the default value of parameter TAG_DESCRIPTION
from “ ”. FOUNDATION fieldbus Device 2 imports the template file from FOUNDATION fieldbus Device 1. FOUNDATION fieldbus
Device 2 still has TAG_DESCRIPTION = “FOUNDATION fieldbus Device 2 Tag” because the TAG_DESCRIPTION parameter
for FOUNDATION fieldbus Device 1 was still the default value, and, as a result, was not exported to the template .xml file.
Any changes made to the default values are written to the template .xml file.
2. Name and save the template .xml files to the default location at the system level.
Note The default naming convention is FOUNDATION fieldbus Device Name_FOUNDATION fieldbus Device Type_
DeviceRevision; however, this name can be changed to provide more detail to the contents of the template .xml file.
2. Import the H1 device template from the default location containing the template XML file is at the system level.
Note The Info tab indicates import status and notifies the user when import is complete or if errors occurred.
Example Log Message — Successful Import, Matching Devices Types, Matching Device Revisions
Example Log Message — Successful Import, Matching Devices Types, Different Device Revisions
• All fieldbus parameters import the HelpText using the language codes for the Primary Language from the DD files (if
available).
• All fieldbus parameters import the alternate HelpText using the language codes for the second language from the DD
files (if available).
• If an item in the DD files only gives one string with no language code, it is assumed to be English. In this case the
alternate HelpText remains blank.
Note The primary and second language descriptions are user-editable text. These fields are not filled out from the DD files.
Note For further details, refer to the ControlST Software Suite How-to Guides (GEH-6808), the section, How to Qualify a
FOUNDATION Fieldbus Field Device.
• Linking device
− Schedule
− General configuration
− IP address
• Fieldbus device
− Parameter configuration
− VCRs to publish and subscribe data
− Node address
− Block tags
− Capability level
• Mark VIe controller
− Control data publish and subscribe information
− Fieldbus function blocks on EGD
− Alarm and diagnostic configuration
− Application code
− DHCP client table
− NTP configuration file
PFFAs are not capable of online interaction while the controller is not in the Inputs
Enabled or Controlling state. After reboot, if the controller is delayed (such as with a
Frame synchronization delay) in achieving the Inputs Enabled state, the PFFA will be
offline until the Inputs Enabled state is achieved. This differs from all other I/O packs,
which can achieve online communications before the Inputs Enabled state is achieved
Attention by a controller.
If a fieldbus device placeholder is emitting a device alert or process alarm, active block alerts display an icon ( ) in the
Tree View at the block level and the following locations:
• The Fieldbus Block inside the Fieldbus Device Placeholder emitting the Device Alert or Process Alarm
• Fieldbus Device Placeholder which contains the emitting Function Block
• Linking device H1 Segment which contains the emitting Fieldbus Device Placeholder
• Linking device which contains the emitting linking device H1 Segment
The ToolboxST application classifies a fieldbus device in one of four states:
• Uninitialized ( )
• Initialized ( )
• Commissioned ( )
• Mismatch ( )
Decommissioned devices display in the Hardware tab as follows:
• From the Tree View under a linking device’s attached segment in an expandable item for decommissioned devices
• A warning icon on the attached segment’s icon
• A warning icon on the linking device’s icon to which the attached segment belongs
Note Refer to the section Fieldbus Device Placeholders for additional information, including fieldbus device state
transitions.
If an H1 Device is received from the factory with an already assigned permanent node address, it is possible that it will not
display in the decommissioned list of the ToolboxST application's Hardware View. The following background information
and procedure should be used to clear this condition and allow the user to commission H1 devices.
Normally, H1 devices come from the factory without a permanent node address assigned. This allows the Link Active
Scheduler (LAS) to assign one of the FOUNDATION fieldbus specified four default addresses (248, 249, 250, or 251) so they can
be added to the live list and then commissioned by the host system.
The H1 Datalink Layer addresses are defined as follows:
FUN to FUN+Number of Unpolled Nodes Range of unused addresses defined in ToolboxST Link Settings. H1 devices
(NUN=210 default) in this range will not be in the live list.
The ToolboxST application (by default) has link settings configured to optimize the communications with commissioned
devices on each H1 segment. This means that the First Unpolled Node (FUN) is set to be the highest node address that the
ToolboxST application assigns during the commissioning process (FUN = 37). It follows that the Number of Unpolled Nodes
(NUN) is set to the default value of 210.
In this way the default ToolboxST application's link settings with FUN=37 and NUN=210 makes it so that any H1 device with
a previously assigned permanent node address between the values of 37-247 will not be added to the live list and therefore
will not be displayed in the decommissioned list.
To change this the link settings can be modified so that the range of unpolled node addresses is set to zero until after the H1
device with the previously assigned permanent address has been cleared and is then displayed in the live list with one of the
default addresses (248, 249, 250, or 251).
➢ To clear a device
After it is cleared, the device can be commissioned using the normal commissioning process for H1 devices.
Note Commissioning a new device follows the same procedure except the new device is selected instead of one from the
Decommissioned Devices list.
Note Devices configured for use with FOUNDATION fieldbus cannot display actual device and DD revision information until
they have been commissioned in the ToolboxST application. Therefore, all available placeholders by the same manufacturer
display in the H1 Device Commissioning Wizard. Verify the correct revisions before selecting the placeholder to ensure the
correct one is selected.
• To move a commissioned H1 device to the uninitialized state, the ToolboxST application clears the commissioned
H1 device.
• If something fails, the status column displays a red error icon and failure text.
5. Click Close. (The Close button displays on the Wizard whether the decommissioning succeeds or fails.)
When a device is decommissioned:
If the linking device or the field device associated with the block (by block assignment) is not present, then the live value of
the output has a Bad status such as 24 (NOT_LIMITED-NO_COMM_WITH_NO_USABLE_VALUE-BAD) as displayed in
the following figure:
To simulate a good value on the output pin, add a VARSIM block to the field device. Two connections must be made with a
VARSIM block: one for the value and one for the status. For the value, connect an output of the VARSIM block to the global
variable created previously in the FOUNDATION fieldbus block. For the status, connect to the same global variable but add .
Status to the end of the variable name.
Example: To simulate a value of 17 with good status (128) for the FF_AI block discussed previously, create a VARSIM block
as displayed in the following figure:
Tip � Trender signals which are not of interest can be removed. For additional information, refer to the Trender Instruction
Guide (GEI-100795).
Custom Block Drawings are supported in the Software tab for fieldbus function blocks which provide the following
indicators:
PFFAs are not capable of online interaction while the controller is not in the Inputs
Enabled or Controlling state. After reboot, if the controller is delayed (such as with a
Frame synchronization delay) in achieving the Inputs Enabled state, the PFFA will be
offline until the Inputs Enabled state is achieved. This differs from all other I/O packs,
which can achieve online communications before the Inputs Enabled state is achieved
Attention by a controller.
When a user performs a download for FOUNDATION fieldbus devices using the Download Wizard, they can select from one of
the following download options:
• Incremental Parameter Download runs a system comparison and identifies which parameters were modified and
downloads only the parameters that were changed.
• Full Parameter Download performs a full system device download of all parameters for the device.
Note Users can run a Reconcile report to run a system comparison and determine if a full download is needed.
• PFFA Schedule Download performs a full parameter download to a PFFA (including all segments and H1 devices
configured on the PFFA) and ignores any non-commissioned H1 device placeholders. This download can be used when
scheduled communication (Software tab) issues are encountered. This option will clear and reset the PFFA schedule links
and any H1 device communications from the PFFA will be interrupted during the download.
Note The options selected on the FOUNDATION Fieldbus Download Options dialog window are stored locally. The next
FOUNDATION Fieldbus download will retain the previous download selections.
Additionally, users have the option to select the number (1-5) of PFFA modules that will be downloaded in groups at one time
(in parallel). Downloading multiple PFFA modules at one time reduces the total time of the download process. However, the
amount of time an individual PFFA module takes to download can take longer than a serial download. In a parallel download,
all PFFA modules share the unused bandwidth on the H1 network for the download, in a serial download the PFFA module
being downloaded has access to all of the unused bandwidth on the H1 network for the download.
The Download Wizard does the following:
• Displays linking devices that need to be downloaded using the orange not equal sign
• Displays linking devices that do not need to be downloaded using the green equal sign
• Displays fieldbus devices that need to be downloaded using the orange not equal sign
• Displays fieldbus devices that do not need to be downloaded using the green equal sign
• Displays the status of the download
• Updates the download log as the download progresses
• Scans for differences in the ToolboxST configuration versus the actual configuration
• Places appropriate fieldbus resource, transducer, and function blocks OOS and then places them back in service as part of
the download procedure
• Displays red X icons on H1 device placeholders, listed by PD_TAG, that do not display on the live list as
commissioned to indicate it cannot find a matching commissioned H1 device
• Downloads multiple H1 devices in a download batch
• Instantiate blocks during the block instantiation phase of download
Note It is possible for a database differences analysis to show that no downloads are necessary; however the controller
I/O Equality may show as Not Equal. There are certain cases in which when a change is made to a block, which results in
flagging the device's Resource Block as Needs to be Downloaded, and the change is undone. A Download scan will
display nothing to be downloaded but the Needs to be Downloaded flag does not get cleared by the undo action.
Performing a forced download to the device or reconciling parameters using a Parameter Reconcile report can establish
controller equality again.
Note If the download options are changed on the FOUNDATION Fieldbus Download Options dialog window of the Download
Wizard, after the download is completed, the Save icon is enabled. If the user does not save the system and tries to perform
another download, the system notifies the user that the system has not been saved from the previous download. The user must
save before they are able to proceed with another download. Changes made on the FOUNDATION Fieldbus Download Options
dialog window will be remembered for the next download.
• PD_TAG
• Link information
• Write the NTP MIB object with the correct time server IP address based on the configured redundancy information. The
following rules are used to determine the correct NTP time server:
− If the linking device is simplex then give the IONet addresses of whatever is on that IONet. (Example: if TMR
controllers and a simplex linking device are on T IONet, assign 192.168.3.10 and 192.168.3.9 or 8.)
− If a simplex controller and simplex linking device are on the IONet assign 192.168.1.8 and 192.168.2.8. Port
forwarding the linking devices can actually get to the different subnets, but if possible it makes sense to give the
address on the same subnet trying to span across multiple controllers to give redundancy.
• Write the transmission delay time
• Write the redundancy message configuration
• Write the optimized T3 timer and set the FF T3 timer=0
Note The CIT tool kit does not download the T3 timer so it has to be written to using FMS writes.
• Download the first unpolled node ID (FUN) and number of unpolled node ID's (NUN) based on the number of existing
nodes per segment if the user enters 0 for both of these settings.
Linking devices must be fully assigned (downloads complete) before fieldbus devices on H1 segments can be commissioned
and display live in the ToolboxST application. Using the Download Wizard, the rest of the linking device download occurs as
part of the download process to send schedule information.
• Parameters download each time they are changed by the user and whenever the defaults read from the DD files are not
null or empty.
− Always set LIM_NOTIFY = MAX_NOTIFY unless it is less than 3. Then set LIM_NOTIFY=3
− Always set REPORTS to enabled in the FEATURE_SEL parameter.
− Always set CONFIRM_TIME = 640000.
Note The FOUNDATION fieldbus Alarm Confirm Time option is set in the system settings for the Mark VIe control.
Refer to the section Controller Settings.
• The wait stops when the linking device is found in the appropriate live list.
• The wait can be cancelled by the user.
9.3.5 Upload
The ToolboxST application is used to perform the upload of a controller’s configuration that contains fieldbus function blocks
and fieldbus devices. If the ToolboxST application does not have the DD files for a specified fieldbus device inside the
placeholder, the following happens:
If a fieldbus device placeholder is emitting a device alert or process alarm, active block alerts display an icon ( ) in the
Tree View at the block level and the following locations:
Attached segment
Fieldbus device
Block
Tip � When device alerts display in the Alarm Viewer they are time stamped (synched). The only time they are not synched
is when a download has been done to a device and they have not yet resynched. At that time they display a 1972 time stamp.
• The Hardware and Software tabs’ Summary View, in the Parameter tabs
• Trender
• Watch Window
• The Software tab’s Summary View, in the diagram editing space
Double-clicking on a live value when online displays the Change Live Value dialog box.
The following operations are performed from the Change Live Value dialog box:
Note If the fieldbus parameter cannot be written (for example, because of the fieldbus function block’s current
mode), the response displays from the fieldbus device to which the write was attempted.
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
Warning measures should be strictly enforced in conjunction with this procedure.
The following figure gives a visual indication of which items can be forced:
• Indicate the PD tag of the device to which the fieldbus function block is assigned
• Display the description of the assigned fieldbus function block
• Display the assigned fieldbus function block’s View 1 parameters over EGD
• Write to an assigned fieldbus function block’s View 1 parameters over EGD using Command Message Protocol (CMP)
which can be written to indicated by the DD files. (This is how HMIs write values over EGD to Mark VIe Controllers
through CIMPLICITY Screens.)
• Perform the Goto Logic Function
• Print macro cycle viewer: A view similar to the macro cycle viewer display area spread across multiple pages with
selected macrocycle, block execution, publish/subscribe duration, and so forth are printed.
• Dynamic help documentation for each supported block type when the Info tab is selected while targeting a FOUNDATION
fieldbus resource, transducer, or function block in both standard and enhanced forms
• Dynamic help for FOUNDATION fieldbus parameters
− Descriptions from DD files
− Other help from DD files
• Documentation on DD attributes in block and parameter displays as well as conditional expressions. DD attributes
include:
− Validity
− Handling
− MIN_VALUE, MAX_VALUE
− DISPLAY_FORMAT
− EDIT_FORMAT
− Enumeration / Bit Enumeration Lists
The ToolboxST application monitors the calibration permissive and calibration command. If the permissive is lost, all
calibration and verification buttons on the dialog box are disabled. If the calibration command cannot be activated or is lost,
all calibration and verification buttons, with the exception of the Calibration Mode button, are disabled.
Refer to the Mark VIe and Mark VIeS Control Systems Volume II: General-purpose Applications, the sections:
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 679
GE Internal
➢ To calibrate valve circuits
1. From the Component Editor, select the Hardware tab.
2. From the Tree View, select the desired PSVO, PSVP, PCAA, or PMVE with an attached MVRA or MVRF.
3. From the Summary View, select the Variables tab, then click Go On/Offline.
4. In the Variables tab, scroll to CalibEnab# and double-click it in the row header.
5. Change the value to True.
Note Only enable one valve for calibration at one time. When the procedure is repeated, set the previously calibrated valve
to False.
6. From the Summary View, click the Regulators tab and enable the desired regulator. Select the appropriate regulator
type from the drop-down list.
7. Verity that the Enable check box is selected.
Do not make any changes to the regulator configuration during valve calibration.
Each calibration command is monitored by the ToolboxST application to verify
performance.
Attention
8. Click Calibrate to display the Calibrate Valve dialog box.
The following figure displays the calibration of ratiometric LVDTs for an LMPosition regulator on a simplex PMVE MVRA
I/O module. Different regulator types, redundancies, and servo I/O modules will display slightly different results.
9. From the dialog box, click Calibration Mode to enable all command buttons and start the calibration command in each
I/O module. A Trender window displays dynamic signals. For further details, refer to the Trender Instruction Guide
(GEI-100795).
LVDT voltages are the values that represent the minimum and maximum actuator positions stored in the I/O module. These
values are not live data. They display after a Save command is performed.
10. If you are performing auto-calibration, complete the following steps in this sequence:
a. Click Minimum End and wait for the actuator to reach its minimum end position.
b. Click Fix Minimum End to collect the voltage value at the minimum end position.
c. Click Maximum End and wait for the actuator to reach its maximum end position.
d. Click Fix Maximum End to collect the voltage value at the maximum end position.
e. Click Calibrate to apply the minimum and maximum values collected.
f. Click Save to save the calculated values. The calculated values are saved for each servo module.
Note Voltage minimum and maximum values are saved for all servo modules. The PSVO and PSVP modules also save
RCoilOpen and RCoilShort thresholds on the Servo tab. The PCAA module saves ExcitMonCal values on the LVDT tab.
Note Only one command state can be active at any one time.
11. After calibrating the LVDTs, complete the following in any order to verify servo performance.
a. Click Position to apply open loop current steps to the valve actuator, and monitor the position as the actuator moves
from Min to Max and back to Min.
b. Click Current to apply a closed loop position ramp to drive the valve actuator, and monitor the current as the
actuator moves from Min to Max and back to Min.
c. Click Manual to enable closed loop position steps. Input a position in the SetPoint text box, click Send, and
monitor the position feedback as it moves to the SetPoint.
d. Click OFF to exit verification mode.
12. When calibration is complete, click the X in the upper right corner. Click OK to save the calibration trend, which is saved
in the system directory in the Tools folder for the applicable controller. The calibration window then closes.
Repeat this procedure for each associated servo valve.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 681
GE Internal
10.2 PGEN Power Load Unbalance (PLU) Configuration
The power load unbalance (PLU) function requires a multicast connection between a Turbine-Generator Monitor (PGEN) I/O
module and a Discrete Output (PDOA) I/O module on the same IONet.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 683
GE Internal
10.3 HART Device Configuration
10.3.1 Module Configuration for HART Devices
The following modules support HART devices:
• PHRA (Simplex)
• YHRA (Simplex)
• PUAA (Simplex)
• YSIL (TMR)
1. From the Hardware tab Tree View, right-click Distributed I/O, select Add Group, make sure the Group Type
Cabinet is selected from the Type drop-down menu, then click OK.
Attention
➢ To upload HART device IDs: from the Tree View, right-click the I/O module and select Upload HART IDs.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 685
GE Internal
10.3.2 HART Process Variables and Extended Status Bytes I/O
Configuration
Note This does feature does not apply to the YSIL module.
By default, HART inputs and outputs do not display the HART process variables and extended status bytes. The user must
configure a number greater than zero (0) in the HART Control Variables column and the Status Variables column, per point,
for the I/O channel configuration to display the HART variables in the connected variable grid.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 687
GE Internal
Example of Configured HART Extended Status Byte Inputs
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 689
GE Internal
10.4 PPRF PROFIBUS Communications Configuration
The PROFIBUS master gateway (PPRF) is a PROFIBUS DP-V0 or DP-V1, Class 1 master that maps I/O from PROFIBUS
slave devices to Mark VIe controllers on the I/O Ethernet. Only one I/O pack can be actively communicating with its
associated PROFIBUS network. PPRF can be configured in the following redundancies:
Note The GSD Manager is not available until a PPRF module has been added.
2. From the Hardware tab Tree View, right-click Distributed I/O and select GSD Manager.
3. From the Device view, insert the slave device in the network by selecting and dragging the device to the purple-colored
line in the PROFIBUS Network view.
To begin configuration,
double-click the slave device
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 691
GE Internal
10.4.2 Configure PROFIBUS Slave Device
Note Groups and DPV2 are not supported by the PPRF. Signal Configuration is not required.
The slave device opens with the Modules view displayed. Click the Help button on each page for detailed configuration
information. Configuration pages include the following:
• Modules Page
• General Page
• Parameters Page
• DPV1 Page
Select
General.
Note The default time interval before fail-safe mode for a DP device is 200 ms. For a PROFIBUS PA device, the setting
should be 5000 ms.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 693
GE Internal
10.4.2.3 Parameters Page
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 695
GE Internal
10.4.2.5 DPV1 Page
If DPV1 is supported by this device, the following screen displays. The PPRF must be an H1B (BPPC) I/O pack.
Select the Enable DPB1 check Click Help for configuration information.
box for each DPV1 device. Click OK to return to the Hardware tab.
Click OK to return to
the Hardware tab.
Click OK to return to
the Hardware tab.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 697
GE Internal
10.4.3 Configure PPRF Master Device
➢ To configure the master device
Bus Parameters
displays
PROFIBUS
network
properties.
Bus Monitoring
displays how
the PROFIBUS
network is
monitored by
the gateway.
Attention
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 699
GE Internal
10.4.5 Display PROFIBUS Network
➢ To display the PROFIBUS network overview
The Variables data grid displays the PROFIBUS configuration, which is defined as a number of module input and output
bytes or words. By default, slave inputs are followed by slave outputs. Successive rows may be grouped as necessary to create
actual point values that span multiple rows. Packed Boolean values are expanded into a separate data grid so that Boolean
Mark VIe variables can be attached to the individual bits.
Variables Tab Columns
Column Description
Connected Variable Displays the connection to other defined variables in the ToolboxST application
Displays the data type of the variable configured in the Mark VIe component
Var Data Type Space can be reserved for unused inputs and outputs, enabling subsequent online
loads when variables are added.
Displays the data type of the slave device I/O point
If the size of the point spans multiple rows of input or output bytes or words, subsequent
Fieldbus Point Data Type
rows display Continued. The default byte data type for rows associated with
configuration bytes must be changed to a supported data type.
Raw Min, Raw Max, Eng Min, Eng Values used to calculate scaling from raw units (the PROFIBUS point) to engineering
Max units (the Mark VIe variable)
Transfers are expanded into individual bits and displayed in the Booleans tab below the
Boolean
Variables tab
If set to True, enables input event scanning on a Boolean transfer
An input event is similar to an SOE, but has a 10 ms resolution.
Input Event Enabled
Any field except Var Data Type and Fieldbus Point Data Type It can be modified without
restarting the controller or I/O pack.
Note The Direction, Module, and Fieldbus Point Offset columns are Read-only.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 701
GE Internal
Supported Fieldbus Point Data Types
PROFIBUS Point Data Type Mark VIe Variable Data Type Scaling
Boolean Boolean —
Integer
Integer16
Float √
Double integer
Integer32
Float √
Unsigned integer
Unsigned16
Float √
Unsigned double integer
Unsigned32
Float √
Floating point (32 bits) Float √
If any PROFIBUS device generates a non-status only diagnostic, the ProfibusDiag variable has a value of True. For
applications that require diagnostic presence indication, attach a defined BOOL-type variable to ProfibusDiag.
Non-status diagnostics are ones that indicate problems. Status-only diagnostics contain only the standard portion (the first six
octets). These, in addition to the master address and identification number, have one or more of the following diagnostics
values set.
Note The connected variable may be added, changed, or removed and loaded without restarting the controller or I/O pack.
➢ To display additional tabs: from the Tree View, select a slave device to display tabs in the Summary View.
1. From the Tree View, select a slave device.
2. From the Summary View, select the Standard Diagnostics tab.
3. In the Connected Variables column, add desired variables. Entries in all columns are read-only.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 703
GE Internal
Identifier Diagnostics Tab
The Identifier Diagnostics tab, which is initially empty, is used to connect variables to bits within the Identifier-related portion
of a diagnostic message. Each bit, which corresponds to a module in the slave device, is set to True to indicate a problem. The
data type for a connected variable must be a BOOL. The Identifier Number range is 0 to 495.
Note If lines are added or removed from the Data Grid, the I/O pack must be restarted after being downloaded.
Existing Data Grid modifications (adding, removing, or changing connected variables, changing the Identifier Number and
such) can be downloaded without restarting the controller or the I/O pack.
To add a line without specifying the connected variable, you must enter a space in the Connected Variable field to enable the
other fields for data entry.
Note The system must be running, and the ToolboxST application must be able to connect to the Mark VIe component.
➢ To display advanced diagnostics: from the Tree View, right-click PPRF and select Troubleshoot Module and
Advanced Diagnostics.
To avoid configuration conflicts and corruption of data, do not edit exported files
outside the ToolboxST application.
Attention
➢ To export a PPRF configuration: from the Hardware tab Tree View, right-click the existing PPRF with network
devices already defined and select Export Configuration.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 705
GE Internal
From the Browse
for Folder
window, either
select an empty
folder or click
Make New Folder
to create a folder
to export the
configuration to.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 707
GE Internal
10.4.11 Advanced Import
The Advanced Import option provides an additional dialogue box during an import, and allows different GSD versions to be
used during an import when multiple versions are available. It also allows exported devices to be skipped during the import.
After you select the export folder, the following dialog box displays. To enable the Advanced Import option, Show Advanced
Importer Screen must be set to True in the controller settings dialog box.
Note The GSD file must be imported into the configuration for that selection to display in the DTM Device column.
A main feature is selecting a specific GSD from the DTM column. This is useful when the Device Type ID or Ident Number
is identical for multiple versions of a specific device. If two revisions of a device have the same device ID, the same revision
will be selected for both devices being imported. You can select the appropriate GSD in the DTM Device column for each
device.
An additional feature is the capability to skip the import of a device that was exported.
Note For Creation Mode, use the Use Hilscher generic DTMs if available default selection only.
Note Refer to Mark VIe and Mark VIeS Control Systems Volume II: General-purpose Applications (GEH-6721_Vol_II).
The CANopen I/O pack (PCNO) is a network management master that maps I/O from CANopen devices to Mark* VIe
controllers on the IONet.
Only the following devices are currently supported on the PCNO CANopen network:
Attention
➢ To add a PCNO I/O module and devices: from the Component Editor Hardware tab, right-click Distributed
I/O and select Add Module.
Select
PCNO and
click Next.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 709
GE Internal
From the drop-down list,
select the module version.
Devices 1-25
and 125 are
configurable
The selected baud rate affects the number and type of devices that can exist on the CANbus. Refer to the Mark VIe and Mark
VIeS Control Systems Volume II: General-purpose Applications System Guide (GEH-6721_Vol_II) for a list of supported
devices per network.
Note The Woodward Dual DVP can only be used with the PCNOH1B version.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 711
GE Internal
Right-click a device (1-25), select Attach,
and select the desired device from the list.
The Variables tab contains a list of counters that provide an indication of CANopen message transmission and reception. Each
time the I/O pack sends a message to a slave device, the corresponding RPDO count is incremented. Each time the I/O pack
receives a message from a slave device, the corresponding TPDO count is incremented. In the case of the GE Sensing DPS
pressure sensors, RPDOs are not supported so they do not display in the Variables tab.
A connected variable can be changed with an online load. Adding or removing CANopen devices requires an offline load.
➢ To display external CANopen device configuration details: from the Tree View, select PCNO and press F1.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 713
GE Internal
➢ To go online with PCNO without an attached device
Configure the I/ O
module information
and click Next.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 715
GE Internal
Note: If the Location Code (Host name) is modified in either the Add Module
Wizard or the Property Editor for the PMVE module , ToolboxST requires
that the value include a minimum of one alpha (letter) character, and no
more than 24 characters.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 717
GE Internal
Details for the configured
board display in the
Summary View in tab format
Note To add additional boards, select another Port item and follow the same procedure.
Click Next to
continue. The
next wizard page
displays the
progress of the
connection.
When it is
complete, click
Finish.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 719
GE Internal
10.7 PAMC I/O Module Configuration
➢ To add a PAMC I/O module: from the Hardware tab Tree View, right-click Distributed I/O and select Add
Module to display the Add Module Wizard.
Click Release
Notes to display
additional
information about
the currently
selected module
version.
Click Next to
confirm the
configuration,
then click Finish.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 721
GE Internal
10.7.1 Add SAMB Terminal Board
➢ To add a SAMB
The bar code is located underneath the cover plate over the JB4 connector if no BAPA is plugged into this connector. If a
BAPA is plugged into JB4, remove this BAPA to view the bar code or retrieve the bar code as displayed above.
Note Using the CompactFlash reader is the preferred method for IONet setup, however, a serial cable and adapter for COM1
can also be used.
The PAMC must be configured with a TCP/IP address prior to connecting to the IONet Ethernet. Use a CompactFlash card
reader for initial setup of the UCSA (PAMC) IP address.
3. Insert the CompactFlash into the card reader, then plug the card reader into the USB port of the computer running the
ToolboxST application.
Note To format the CompactFlash requires the ToolboxST application running as administrator. If the user to the computer
running ToolboxST application does not have an Administrator account to the computer, then this must be setup prior to
formatting the CompactFlash.
4. Close the ToolboxST application (if currently running). Launch the ToolboxST application by right-clicking the
TooboxST icon and selecting Run As Administrator.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 723
GE Internal
5. From the System Editor, double-click the Mark VIe controller to open the Component Editor.
If the configuration being downloaded contains I/O packs with different module IDs
than the configuration currently running, the download may install incorrect
firmware to some I/O packs. If this occurs, make sure the controller is running the
new configuration, restart the entire system, and then start the ToolboxST* Download
Attention Wizard again.
Note Refer to Mark VIe and Mark VIeS Control Systems Volume II: General-purpose Applications System Guide
(GEH-6721_Vol_II), the section PSCA Serial Communication Module.
The Serial Communication Input/Output (PSCA) module provides the electrical interface between one or two I/O Ethernet
networks and a serial communications terminal board.
Select PSCA
and click Next.
2. From the wizard page, select configuration information and click Next.
3. Confirm the configuration and click Finish.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 725
GE Internal
➢ To attach a device: from the Tree View, expand the PSCA to display the seven ports.
Note Refer to the Mark VIe Control PSCH Specialized Serial Communication Module Instruction Guide (GEH-6763) to
configure parameters and variables.
The Specialized Serial Communication (PSCH) I/O module provides the electrical interface between one or two I/O Ethernet
networks and an SSCA serial communications terminal board.
➢ To add a PSCH I/O module: from the Hardware tab Tree View, right-click Distributed I/O and select Add
Module.
Note FTI, FTD, and GPS communication devices operate in simplex mode only.
Select
PSCH and
click Next
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 727
GE Internal
Click Release Notes to display
Use the drop-down list to additional information about the
select an I/O module version. currently selected I/O module version.
If the Module
Required check
box is selected
the I/O module
must be present
and functioning
for the controller
to go online.
Click Next to
review, then
click Finish
Right-click a port,
then select
Attach and the
desired device
A different dialog
box displays for
each device
3. From the Modify dialog box, make selections based on the attached communication device, enter a port description, and
click OK.
For information on configuring I/O points, refer to the Mark VIe Control PSCH Specialized Serial Communication Module
Instruction Guide (GEH-6763)
Attached devices
display in the
Tree View
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 729
GE Internal
Attached devices also display in
the Summary View.
Note Communication devices that display in the Summary View have a fixed set of variables.
Terms
ASK Automatic Station Keeping
BOP Blowout Preventer
ERA Electronic Riser Angle
FTD Flow Totalizer Display
FTI Flow Totalizer Input
GPS Global Positioning System
LanModule GE distributed I/O control module
LMRP Lower Marine Riser Package
POD Mechanic vessel assembly containing subsea hydraulic/electrical BOP control components (subsea
control module)
PodBus Modified version of Modbus for GE Drilling
SEM Subsea Electronics Module
Submodule GE Drilling device attached to a PSCH
UPS Uninterruptible Power Supply
Configure the
terminal board.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 731
GE Internal
From the Tree View, select From the Summary View, select
the PIOA I/O module ARCNET as the Network Type
➢ To add a PPNG module: refer to the chapter Mark VIe Component Editor and the section Add Modules.
Note For further details on the PPNG, refer to the Mark VIe and Mark VIeS Control Systems Guide (GEH-6721_Vol_II), the
chapter, PPNG PROFINET Module.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 733
GE Internal
10.11.1 PPNG Network Address Configuration
Before you begin, verify the following:
• Control system hardware is fully functional and IONet cabling is connected to the
PPNG as specified when the module was added in ToolboxST.
Note The UCSC, as shipped from the factory, does not include the software on the controller to support communication
from the PHY PRES button to the EFA. The user needs to download to the controller at least once (using ToolboxST) to
enable this.
Note The UCSB controller must first be configured with a network address prior to connecting to the IONet
Ethernet. Install and configure a serial connection to the COM port on the controller. An RJ-45 to DB9 adapter is
required along with an Ethernet cable for the serial connection.
If this step is not completed, the Identify PROFINET I/O Devices operation will fail.
Attention
7. With the Mark VIe controller online, select the PPNG Variables tab and confirm that the I/O Live Values are green.
The PPNG has been successfully initialized and it is ready to be configured for the PROFINET devices.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 735
GE Internal
➢ To set the embedded PPNG controller module network address
1. Perform a Build of the component.
2. When the Build is complete, right-click PPNG and select Setup to display the Setup Wizard.
3. When the Setup Wizard Welcome window displays, click Next to select a configuration method.
4. For an embedded PPNG controller module, the only configuration method available is to re-initialize and transfer the
configuration from the ToolboxST application to the PPNG hardware using a USB device. This procedure is used to
configure the network address but it is only necessary if the location code has changed.
To re-initialize the embedded PPNG for a UCSCH1A controller, select Initialize USB from the Setup Wizard, click
Next and perform the following steps:
a. Insert a non-encrypted USB 2.0 (only) flash device with a 4 GB minimum capacity into the HMI computer USB
port.
b. Click Scan, select the flash drive, and click Write.
c. Click Next.
d. Remove the flash device from the computer.
e. Power down the PPNG.
f. Insert the flash device into the UCSC controller containing the embedded PPNG and perform the restore procedure
using the PHY PRES button located on the UCSC controller. For detailed instructions, refer to the Mark VIe and
Mark VIes Control Systems Volume II: General-purpose Applications System Manual (GEH-6721_Vol_II), the
section UCSC Restore.
g. When the configuration completes successfully, remove the flash device.
If this step is not completed, the Identify PROFINET I/O Devices operation will fail.
Attention
7. With the Mark VIe controller online, select the PPNG Variables tab and confirm that the I/O Live Values are green.
The PPNG has been successfully initialized and it is ready to be configured for the PROFINET devices.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 737
GE Internal
10.11.2 Add PROFINET I/O Device to Local Area Network (LAN)
When a PPNG I/O module is added in the ToolboxST application, a PROFINET Local Area Network (LAN) is automatically
created. Perform the following procedure to add PROFINET I/O devices to the PROFINET network (VersaMax* PROFINET
device is used as an example).
Select the desired I/O device and click Add Device, then click Close.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 739
GE Internal
10.11.3 Change GSDML Version
The Change GSDML feature enables the user to upgrade or downgrade the GSDML file that defines a PROFINET I/O
device assigned to a PPNG.
Back up or record PROFINET I/O device configuration before changing the version
of the GSDML file.
Caution
If the system configuration files are on the CMS Server, check out the system from the
CMS Repository to access the Change GSDML feature and make changes.
Attention
➢ To change the version of the GSDML file
Note Any discrepancies between the new GSDML file and the existing PROFINET I/O device configuration are reported to
the user.
During the change, the following apply:
1.) Existing I/O points, parameters, and/or parameter Groups not provided by the new GSDML file will be deleted.
2.) New I/O points, parameters, and/or parameter Groups provided by the new GSDML file will be added.
3.) Device settings and/or parameters may be altered by the new GSDML file.
The Change GSDML Version procedure is complete after the user performs a
point-by-point review of the new PROFINET I/O device configuration. Failure to do
this could result in damage to or destruction of equipment.
Caution
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 741
GE Internal
10.11.4 Delete Third-party GSDML Files
Any third-party GSDML files that are imported using the GSDML Manager can be deleted.
From the PROFINET GSDML Manager window, select the GSDML file name and
click Delete GSDML.
A delete confirmation dialog box displays. Click Yes to proceed with the delete
operation.
Note If any configured I/O device GSDML file is deleted, the ToolboxST application will log an error during the Build
operation.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 743
GE Internal
➢ To add a PROFINET I/O module to the PROFINET I/O device
1. From the Tree View, expand the PPNG module and select the PROFINET I/O device.
2. From the Summary View, select the Slot Configuration tab and select modules to add.
Note Refer to the Mark VIe and Mark VIe Control Systems Volume II: General-purpose Applications System Manual
(GEH-6721_Vol_II) for a list of supported PROFINET I/O modules.
Drag-and-drop or double-click
desired modules to add slot and
sub-slot locations.
➢ To delete an I/O module from the PROFINET I/O device: select the I/O module and press the Delete key.
Note The Host Name entered for the PROFINET I/O device must be the configured Host Name. The PROFINET DCP Tool
feature in the ToolboxST application can be used to update this information.
Refer to the following section Identify and Assign PROFINET I/O Device Names for the procedure to configure the Host
Name.
From the Hardware tab Tree View, right-click the PPNG module and
select Identify PROFINET Devices... to display the PROFINET DCP Tool.
The tool scans through the PROFINET network and the PROFINET DCP Tool dialog box displays all PROFINET I/O slave
devices found on the network.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 745
GE Internal
Identified PROFINET I/O Slave Devices
➢ To factory reset the PROFINET I/O device: from the PROFINET DCP Tool dialog box, click Reset for an I/O
device to restore all parameters for that I/O device to factory defaults.
Clicking Reset removes the PROFINET slave I/O device configuration and resets it to
factory settings. It is not used for remote reboot.
Attention
➢ To set the network address for a PROFINET I/O device: from the PROFINET DCP Tool dialog box, click Set IP
and enter a unique location code.
Note The Set IP button is only enabled when a device is selected in the Configured Device column and the selected device
network address (Configured Device IP value) is unique across all identified I/O devices.
The Set IP button is disabled if the configured device network address is already assigned to another device in the list.
Note When the configured device is already mapped with the identified device available on the network, the Configured
Name is automatically highlighted.
Click Set Name, enter the name for the PROFINET I/ O device, and click OK.
Note The PROFINET DCP Tool logs errors if the I/O devices have a duplicate network address or a duplicate name and
displays a warning if the name or an network address is empty.
5. Click Apply to update the PPNG configuration and apply the configured Device Names to the ToolboxST
configuration.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 747
GE Internal
10.11.7 Compare Device to Hardware PROFINET I/O Device
➢ To compare the configured device against the hardware PROFINET I/O device
From the Hardware tab, right-click the PROFINET I/O Device and
select Compare to hardware IO device...
Note The hardware I/O device configuration is retrieved only if the device ID, vendor ID, and network address of the
hardware I/O device match the selected ToolboxST I/O device.
The comparison tool also provides the Identification and Maintenance (I & M) information of the hardware module or
sub-module.
➢ To export the I & M information of all modules or sub-modules to a .csv file: click Export to CSV.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 749
GE Internal
10.11.8 Build and Download Configuration
The ToolboxST application is used to configure both a Mark VIe component and its distributed I/O devices. Both the
component and the I/O devices have three items of software that can be downloaded:
• Base Load
• Firmware
• Application Code
Note The boot loader, base load, firmware, offline application, and parameter software downloads all require the target
device to be restarted. In addition, any change in the PPNG is an offline download and will cause a restart of the PPNG I/O
module. Refer to the section Download to Controller.
Click OK.
Online download of the PPNG configuration is supported only when the change of
configuration is restricted to Raw Min, Raw Max, Eng Min, and Eng Max properties
of the I/O points for the PROFINET I/O device, I/O module, or I/O sub-module.
Any other change in the PPNG I/O module configuration requires an offline download
Attention and a PPNG I/O module restart is required.
4. Click Next through the remaining Wizard pages until the download is complete, then click Close. The controller and the
I/O devices will restart.
5. From the Device menu, select Online. Verify that the controller and all devices are online and the Status tab displays
Controlling – Equal.
Note If any issues occur during the Download operation, refer to Mark VIe and Mark VIeS Control Systems Volume I: System
Guide (GEH-6721_Vol_I), the section Troubleshooting.
Note After restart, when the PPNG I/O module is connecting to PROFINET I/O devices for the first time, a device
communication error may occur. This will become inactive after the connection is established with the I/O devices. When the
Mark VIe controller reaches the Controlling state, the user is required to reset these diagnostics in the PPNG I/O module
Diagnostic tab to clear them.
Note PPNG configuration specific changes, such as changing the update rate of device, device phase, or host name, result in
an online download to the controller as well.
Import GSDML files from version 1.0 to 2.31 and configure the PROFINET I/O
devices (only supports versions from 1.0 to 2.30 in ControlST V05.04).
Attention
➢ To add third-party devices
1. From the Hardware tab Tree View, right-click the PPNG and select Add PROFINET IO Device.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 751
GE Internal
2. From the PROFINET GSDML Manager , click Browse and Import.
3. Provide a path to either the zipped file or the extracted .xml file and click OK. The device is added to the configuration.
The necessary parameters are extracted from the GSDML file, and the data available for editing within the ToolboxST
application. If multiple devices are supported by the added GSDML, all devices will be automatically added to the
GSDML Manager.
2. Select the appropriate Input/Output tab based on the Input/Output I/O device selected
When online, the grid displays the current live values for the channels available. When the modules provide channel health
information, it is displayed as the first entry and selecting the specific Channel health row displays its sub-point’s status as
follows:
Note Refer to PROFINET Point Description for specific Channel details for the module. For further details on how to
configure the application logic, refer to the chapters Software and Blockware Diagram Editor.
• Connected Variable displays the connection to other defined variables in the ToolboxST application code in the
Software tab.
• Var Data Type displays the data type of the variable configured in the Mark VIe component.
• Raw Min, Raw Max, Eng Min, and Eng Max are values used to calculate scaling from raw units (the
PROFINET point) to engineering units (Mark VIe variable).
3. Configure the Connected Variables for the Output and Input channels for the modules required, and add the logic to
drive the signal as required.
4. Download the changes made to the Application code and go online to view the application logic driving the signals.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 753
GE Internal
10.11.12 Flexible PROFINET I/O
The Flexible PROFINET I/O feature allows the user to use the I/O points as individual bits or bytes, or a combination of
bytes. This flexibility is configured using the Split Type drop-down menu on the I/O points window. The Split Type property
default value is Byte for I/O points with the following PROFINET complex data types:
• Octet String
• VisibleString
• TimeOfDayWithDateIndication
• TimeDifferenceWithDateIndication
• NetworkTime
• NetworkTimeDifference
• Unsigned8_Unsigned8
• Float32_Unsigned8
• F_MessageTrailer4Byte
• F_MessageTrailer5Byte
Beginning with ControlST V05.04, any PROFINET configuration with these complex
data types can only be configured with ControlST V05.04. Any later ControlST
version will not support them and you will need to change the Split Type to Bit or
Byte. If ControlST is upgraded to a version higher than V05.04, these complex data
types will generate Build errors. To resolve these errors, change the Split Type to Bit
Attention or Byte.
Note For all I/O points with the Used As Bits property set to True in the GSDML file the Split Type property default is Bit.
From the Hardware tab Split Type property menu , select Byte .
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 755
GE Internal
2. All child points for the I/O point are now data type Integer8, representing individual bytes. This enables you to combine
2/4 points into various 2, 4–byte data types (such as Integer16, Integer32, Unsigned16, Unsigned32, Float32) using the
data type Continued.
To combine two bytes into an Unsigned16 I/O point, modify the PROFINET I/O Point Data Type
value for the first point to Unsigned16 and select Continued for the second point.
Note While the Flexible PROFINET I/O feature provides flexibility in interpreting the data per user needs, the data will only
be valid if the format of the data being read matches the format of the data in which the PROFINET I/O device sends the data.
For example, two bytes of data can be interpreted as either one UINT16 or two UINT8 variables. If the I/O device sends the
data in the UINT16 format, the user must read it in the UINT16 format. If the user reads them as two UINT8 variables, the
data may not be valid.
To change a sub point to a different data type, the user must first select Integer8 for the sub point. Once a sub point is set to
Integer8, any Continued sub points will be reset to Integer8, and all of the available data types are displayed in the
drop-down list.
The following example describes how to change the PROFINET IO Point Data Type back to Integer8 to display the full list of
other available data types:
The first row in the following figure displays Integer32 data type and the three following rows have a Continued data type to
equal the entire 32 bits. You cannot attach variables to rows where the PROFINET IO Point Data Type is Continued.
To change those first four rows to a different data type, Integer32 on the first row must be changed back to Integer8 before a
different data type can be selected.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 757
GE Internal
Example of Data Type Changed Back to Integer8
When this is done, all four rows are automatically changed back to Integer8. Now any data type can be selected in place of
Integer8 as needed.
When a different data type is selected, the Var Data Type automatically defaults to an appropriate value. For example, if
Integer32 is selected from the drop-down list, the Var Data Type defaults to DINT. When a Boolean data type is selected,
new points for each bit in the byte are created.
Note Only change the first point. Continued points will automatically revert to Integer8.
Boolean points created for this byte will be removed.
Data types that require more than one sub point will automatically display the necessary Continued data points in the
drop-down list. For example, if the PROFINET IO Point Data Type for Input-0001_3 has been changed to Integer32, the
necessary Continued sub points are automatically configured.
If more points are required than are available to store the requested data size, you will receive an error. In this case, you must
change more sub points to Integer8 or choose a different size.
Not Enough Sub Points to Support Requested Data Type Error Message
If a sub point was not set to Integer8 when ToolboxST tried to convert it to Continued, the following error message is
displayed.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 759
GE Internal
Another available PROFINET IO Point Data Type selection for a Byte Point Split Type is a Boolean variable. When Boolean
is selected, the current Integer8 point is split into eight Boolean sub points. This allows a combination of Boolean points with
other data types on a single parent variable. As illustrated in the previous figure, when Input-0001_1 is selected as a
Boolean, eight Boolean (_B) points are displayed. The additional _B points for the original parent point cannot be
configured; their data type follows the _B0 point.
If a Boolean PROFINET IO Point Data Type needs to be changed to another data type, all of the Boolean points generated
from the point that was originally split must be reclaimed. To change from a Boolean point type, the _B0 point needs to be
changed from Bool to Integer8. This will remove all of the associated Boolean points and revert the sub point to an Integer8
data type.
Note The PROFINET standard is to use big-endian for the Byte order when converting data types. Two’s compliment is
used to express negative numbers.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 761
GE Internal
10.11.15 PROFINET Network
➢ To display the PROFINET network
1. From the Hardware tab Tree View, select a PPNG I/O module.
2. From the Summary View, select the PROFINET Network tab to display the diagram representation of the
PROFINET I/O devices and the slot information.
PROFINET diagnostic alarms that are generated by the PROFINET I/O device configured for the PPNG I/O module are
displayed in the PROFINET Diagnostics tab of the respective Distributed I/O PPNG tree node. The PPNG generates an I/O
pack diagnostic alarm when at least one PROFINET alarm is raised by any of the PROFINET I/O devices connected to it.
Reset the PROFINET alarms before resetting the PPNG diagnostic alarm.
The PROFINET Diagnostics tab provides the following features to assist the user with viewing and resetting PROFINET
alarms.
PROFINET Diagnostics Features
Column Description
Displays the PROFINET alarm type. An Alarm Type value of 0 indicates an alarm that was generated
Alarm Type internally by the PPNG I/O module rather than any of its PROFINET I/O devices.
The user can filter by alarm type.
Description Reason the diagnostic alarm was generated
Reset All Alarms Resets all PROFINET alarms in the PPNG I/O module
Auto Update When selected, updates the PROFINET Diagnostics tab every 5,000 milliseconds
Refresh Refreshes the PROFINET alarms to display the most current list of PPNG alarms
Alarm Type Filter Enables the filtering of PROFINET alarms displayed in the Alarm Viewer
+ (plus symbol) Expands the alarm row to display additional alarm information provided by the PROFINET I/O device
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 763
GE Internal
➢ To filter alarms: from the Alarm Type column, select the Filter icon.
From the Alarm Type drop -down list, select all or specific alarm types .
The Alarm Viewer updates and displays the alarms .
The PROFINET Diagnostics tab updates and displays the filtered alarms .
Note The PROFINET Alarm History report does not contain the PPNG I/O module diagnostic information. This detail is
displayed from the Diagnostics Tab.
From the PROFINET I/O device, right-click and select Create Report,
then select PROFINET Alarm History.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 765
GE Internal
Example PROFINET Alarm History Report
Note For more information on the GSDML file, refer to the section Add Third-party Devices to LAN.
The full text description of the diagnostic is viewed from the PPNG PROFINET Diagnostics tab.
When all of the diagnostics have cleared, the I/O Live Value for the Connected Variable returns to 0 (healthy).
When more than one diagnostic exists on a channel, only the last active value is assigned to the connected variable.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 767
GE Internal
10.12 PUAA I/O Configuration
The Universal Analog (PUAA) I/O module can be configured to function like any I/O pack (such as PAIC, PAOC, PRTD,
PTCC, and so forth) or a combination of I/O modules. There are 16 available channels (I/O points) that can be configured in
various modes through the ToolboxST application. For further details on PUAA, refer to the Mark VIe and Mark VIeS Control
Systems Guide (GEH-6721_Vol_II).
Note The PUAA I/O module does not have to be rebooted after configuration, with one exception. A reboot is required the
first time HART is enabled on any point, 1-8 or 9-16. For example, using points 1-8, if you enable HART on point 1, a reboot
is required. Enabling HART on any subsequent point in group 1-8 would not require a reboot. Using the same scenario for
points 9-16, if you enable HART on point 9, a reboot is required again. If HART is enabled on any subsequent points in group
9-16 would not require a reboot.
Furthermore, a reboot is required if the last point with HART enabled in either group 1-8 or 9-16 is disabled, meaning there
are no longer any HART enabled points within a group of points (group 1-8 or group 9-16). For example, if points 1 and 2
have HART enabled, disabling HART on point 2 would not require a reboot. However, disabling point 1, which is the last
point with HART enabled in group 1-8, would require a reboot.
• Unused
• Current Input
• Voltage Input
• Digital Input
• Pulse Accumulator
• RTD
• Current Output
• Thermocouple
Note Current Inputs and Current Outputs support HART devices. For a list of I/O modules that support HART devices, refer
to the section HART Device Configuration.
Digital Inputs support SOEs.
When the channels are configured (a mode other than Unused is selected for a channel), Summary View displays
configuration tabs for the selected modes.
Note The PUAA I/O module must be added within a Hardware Cabinet Group. If a Cabinet Group already exists, skip step 1
in this procedure. For additional information on Groups, refer to the section Organize Modules.
1. Add a Group to contain the module. From the Hardware tab Tree View, right-click Distributed I/O, select Add
Group, make sure the Group Type Cabinet is selected from the Type drop-down menu, then click OK.
2. Add a PUAA I/O module. Right-click the Cabinet Group and select Add Module.
3. From the Module Redundancy drop-down menu, select the appropriate redundancy.
4. From the Select Type list, select the PUAA module and click Next.
5. In the Terminal Board Position column, enter the cabinet position value(s) (for example, 1A1A) and click Next.
6. Review the module configuration, then click Finish to add the PUAA I/O module.
The Summary tab displays the PUAA I/O module and indicates that channels (1/O points 1–16) are not yet configured
(Unused mode is the default).
7. To configure the I/O points, select an I/O mode that corresponds to the desired functionality.
From the Hardware Configuration tab, place your cursor in the Mode column
in the row for an I/O point. From the drop-down menu, select the appropriate
mode (CurrentInput is selected for this example).
To modify an I/O point mode after initial configuration the following procedure must
be performed to prevent damage to hardware during transition between I/O point
modes:
a.) Set the mode to Unused and perform a successful Build and Download.
b.) Change the field wiring to match the new I/O point mode.
Caution c.) Once the wiring is completed, select the appropriate mode from the drop-down list
and perform a successful Build and Download.
If the Unused mode is not selected first, and successfully built and downloaded, the
new configuration will not be accepted and a diagnostic will be generated.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 769
GE Internal
The ToolboxST application displays a mode tab for each selected mode type, and lists the I/O points that are configured with
that mode.
Tip � Double-clicking on a row in the Configuration tab Summary View displays the specific I/O point mode tab.
8. To view all I/O points that are configured for a specific I/O point mode, select a mode tab.
The Current Input tab contains the selected Current Input points on the I/O module terminal board that can be individually
configured. Additionally, variables can be connected to the I/O points and associated with the blockware application code.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 771
GE Internal
10.13 Universal I/O Shared IONet Configuration
All Universal I/O packs (such as PUAA) support sharing inputs using the Shared IONet feature. Just as changing a point
mode on a Universal I/O pack will clear the minor revision of the owning device, the consuming device will also have a
cleared minor revision. The consuming device will also be marked dirty, requiring a Save the next time it is opened in the
ToolboxST application. Any connected variables attached to a shared point on the consuming device will be removed when a
change is made to the point mode. A warning displays in the Log window to notify the user which variables were removed.
Note For further details on Shared IONet, refer to the Mark Controllers Shared IONet User Guide (GEH-6812).
Note Analog Alarms cannot be configured on the Local I/O data grid. If an Analog Alarm is required, create a program
variable and connect the local I/O point to that Program variable, then configure the Analog Alarm from within that program
variable, as displayed in the following figure.
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 773
GE Internal
➢ To enable local I/O
1. From the System Editor, open the Mark VIe controller.
2. From the General tab Property Editor, select Platform.
3. Configure the controller with a UCPA platform type, as follows:
Mark VIe and Mark VIeS Advanced I/O Functions GEH-6700AG User Guide 775
GE Internal
Notes
Note To perform the platform upgrade, you must have a Mark VI product installed. From the Setup - ControlST Software
Suite dialog box, select the option to install the eTCSS Runtime Products.
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 777
GE Internal
From the drop-down list,
select the Rack redundancy:
Simplex (one rack) Select the PCMI
TMR (three racks) module version.
Click Release
Notes to display
additional
information about
the currently
selected module
version
The number of
slots is
determined by
the number of
VME board slots
in the rack you
are configuring
(3, 7, or 21)
Note To help with identification and version management, each I/O board has both an I/O and a configuration compatibility
code. These codes identify the I/O map layout and the configuration area for a board. For each compatibility code set, there
are multiple hardware forms used to identify physical characteristics of the board. Each I/O board that can be added to a Mark
VI rack is identified by both its hardware form factor and its compatibility codes.
PCMI
terminal
board
position
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 779
GE Internal
Review the configuration summary
Click Back to make changes or click Finish
Enter further
information in the
optional Notes field
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 781
GE Internal
11.1.2 Modify PCMI Board
➢ To modify a PCMI board: from the Tree View, double-click the PCMI board or right-click the board and click
Modify.
HW Form
ENET1 Port
ENET2 Port
Bar Code
Position
Make changes
and click OK.
The only
terminal board
value that is
modifable is
Position
(terminal board
location)
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 783
GE Internal
The channel selection
From the drop-down drop-down list is
list, select a Mark VI available if Simplex is
I/O board redundancy selected and the
(Simplex or TMR) redundancy is TMR
Select the
desired board
and click Next
Simplex boards can be added to specific channels in a TMR rack. The following boards are not supported:
Optional
notes can
be added
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 785
GE Internal
The Type column displays the From the HW Form drop-down list, select In the Position column , enter the
terminal board hardware type . the terminal board hardware forms. location of the terminal board.
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 787
GE Internal
11.3 Modify Mark VI Board
➢ To modify an existing board: from the Tree View , right-click the board and select Modify to display the Modify
[board name] dialog box.
Optional
notes can
be added
The following
board values
can be
modified:
Type
HW Form
Position
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 789
GE Internal
11.3.1 Modify Terminal Board
➢ To modify a terminal board: from the Tree View , double-click a terminal board to display the Modify Mark VI
[name] Terminal Board dialog box.
Terminal
board
position can
be modified
Optional
notes can
be added
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 791
GE Internal
11.4.1.2 PCMI Board View
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 793
GE Internal
11.4.1.4 VSVO Board View
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 795
GE Internal
11.4.2 Parameters Tab
The Parameters tab allows you to configure all board-specific parameters. After a parameter is changed, updated pseudo-code
files must be downloaded to the I/O boards, but the download operation is done online and does not require a restart of either
the controller or the I/O board(s). Parameters are determined by board type.
Active
alarms
Inactive
alarms
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 797
GE Internal
11.4.5 Status Tab
The Status tab allows you to compare the I/O board version with the ToolboxST application version.
Revision
difference
Configuration
difference
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 799
GE Internal
11.5 Calibrate VSVO/VSVA Valve
VSVO and VSVA valve calibration allows you to configure the valve circuits of a board. The Calibrate Valve dialog box
provides an automated auto-calibrate sequence, as well as the capability for verifying and saving values for each valve circuit.
4. From the Summary View, select the Regulators tab, and from the drop-down list, select the desired regulator.
Note To display a regulator, the previously numbered regulator must be enabled. For example, to display Regulator 3,
Regulator 2 must be enabled.
Note Do not make any changes to the regulator configuration during valve calibration. Each calibration command is
monitored by the ToolboxST application to verify performance.
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 801
GE Internal
• Click Manual to enable manual movement of the actuator (used in conjunction with the Send button)
• Click Send to send the value in the Setpoint text box to the VME board.
• Click OFF to exit the verification mode.
Note LVDT voltages are the values that represent the minimum and maximum actuator positions stored in the VME board.
These values are not live data. They display after the Send button is selected.
Module parameters directly affect the operation of the controller and associated I/O
modules. To reduce the risk of improper operation or damage to the unit, always
check the Compare Parameters dialog box before downloading new parameter values
to a component.
Caution
➢ To download parameters to a board
Select check
boxes for values
to be compared
then click OK
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 803
GE Internal
11.8 Report Board Data
There are three dynamic board reports available for the platform upgrade function.
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 805
GE Internal
The Hardware report contains the following information:
Mark VI to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 807
GE Internal
Notes
Note For additional information on CE3000–I hardware and upgrade, refer to the ALSPA DCS Retrofit Solution CE300
Integration into Mark VIe Controls Platform Instruction Guide (GEH-6803).
CE3000-I to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 809
GE Internal
12.1 Add CE3000-I Rack with PCEG Module
➢ To add a CE3000-I rack and PCEG module to a Mark VIe component configuration
Note Each PCEG module has both an I/O and configuration compatibility code. These codes identify the I/O map layout and
the configuration area for a board. For each compatibility code set, there are multiple hardware forms used to identify
physical characteristics of the board.
Note Only ENET1 Port is available for the PCEG. ENET2 port is designated for communication with the UT160 in the
CE3000-I rack.
CE3000-I to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 811
GE Internal
Review the configuration summary.
From the Hardware tab Tree View, double-click the CE3000-I rack, or
right-click the rack and select Modify.
CE3000-I to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 813
GE Internal
12.3 Modify PCEG I/O Module
➢ To modify a PCEG module
• HW Form
• ENET1 Port
• Bar Code
• Position
CE3000-I to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 815
GE Internal
From the Available Slots drop-down
list, select the appropriate slot number.
CE3000-I to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 817
GE Internal
Review the configuration summary.
CE3000-I to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 819
GE Internal
From the Available Slots drop-down list,
select a free slot to move the board to.
CE3000-I to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 821
GE Internal
12.7 View CE3000-I Status and Configuration
12.7.1 PCEG Module Status
Selecting a PCEG module from the Hardware tab Tree View provides additional PCEG configuration and information tabs in
the Summary View: Summary, All Ports, Variables, Slots, Diagnostics, and Status.
In the following example, the Status tab shows all of the PCODE as equal. If any of the modules are unequal, download the
PCEG application code using the Download Wizard.
CE3000-I to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 823
GE Internal
12.7.2.2 AH115 Terminal Board Summary Tab
When a terminal board is selected from the Hardware tab Tree View, the Summary tab displays an overview of the terminal
board configuration that identifies which points are on the board, including a logical view of where the variables are
connected to the existing points. When the controller is online, live values are displayed.
CE3000-I to Mark VIe Control Platform Upgrade GEH-6700AG User Guide 825
GE Internal
Notes
➢ To create a component: from the System Editor Tree View, right-click the system and select Insert New,
Controller, and Mark VIeS Controller.
Tree View
lists the items
that can be
configured.
The list
changes when
a different tab
is selected.
Property
Editor
allows you to
edit the item
currently
selected in
the Tree
View.
Component
InfoView
displays
information
about the
currently
selected item.
➢ To edit the component: select an item in the Tree View. The configuration information for that item displays in the
Summary View and Property Editor.
➢ To import an existing component: from the Tree View, right-click a parent component and select Insert Existing
and select Device. Select the Device.xml file for the component to be imported and click Open.
Note If no button displays, edit the value directly in the corresponding text box on the right side of the Property Editor.
➢ To edit a property in the Property Editor: select an item by clicking its value 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.
Log Tip � If there is a build problem, the error is listed on the Log tab. Double-click the error. The input focus goes
to the location in the component configuration where the error occurred.
Status Displays operating state and equality information about the component
Keeps a navigation history for each user session and allows you to return to different places in the
History 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.
Finds all uses of a variable within a Library Container
The write icon at the beginning of some lines indicates that the variable is being written at that location.
Where 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.
Each time a Build is performed, a message displays that allows you to view the Change log.
When Errors or Warnings are present, the Log tab notifies the user by displaying the current count, as well as a description.
Click each button to hide the corresponding item. For example, click Warning to hide the warnings listed in the Log tab;
Click Warnings again to display the warnings in the Log tab.
Note Some Data Grids, especially those without an Append Row, may not support all available features.
Quickly set a property to the Left-click the row header for the first row to be edited. Then, while pressing the CTRL key,
same value for multiple rows left-click added row headers. After selecting all desired rows, use the Property Editor to
change properties for all selected rows. (Some properties are omitted when a group of rows is
selected, and properties with conflicting values will display no value in the property editor.)
To... Do this:
Resize a column Drag the vertical bar on the right of the column header to a new location.
Quickly remove a single column Right-click the column header and select Hide Column.
Move a column to a different location Drag the column header to a new location.
Sort by a column Click a column header. The column sorts in ascending order. To sort in descending
order, click the column header again.
Reset columns to the original Right-click any column header and select Default Column Organization.
configuration
Add or remove columns Right-click any column header and select Organize Columns to display the
Organize Columns dialog box.
Select a
column name
and use the up
arrow to move
it to the left-
most side of
the Data Grid.
in the destination grid and select Paste Row(s) to insert the row into its new
location.
Copy and paste multiple rows Left-click the row header for the first source row. Then, while pressing the CTRL key,
left-click added row headers. After selecting all desired rows, continue to hold down the
CTRL key and right-click any selected header. From the shortcut menu, select Copy
Selected/Current Rows to place the rows on the clipboard. Then, right-click the header
for the append row in the destination grid and select Paste Row(s) to insert the rows into
their new location.
Copy and paste a range of two or Click the top left cell of the desired range and drag to the bottom right cell. Right-click the
more cells selected region and select Copy Selected/Current Rows to place the cells on the
clipboard. Then, click the top left cell of the destination range and drag to select the
same number of columns and rows that were copied to the clipboard. Right-click inside
the destination region and select Paste Row(s).
Move rows between data grids Arrange windows on screen so both the source and destination grid are visible. (An
entry in a Tree View is acceptable as a destination). Left click the row header for the first
row. Then, while pressing CTRL, click any added row headers to be moved. Release the
CTRL key and drag a row header to the new data grid.
Add a variable to a block diagram, Arrange windows on screen so both the source grid and a destination block diagram,
Trender window or Watch Window Trender window or Watch Window are visible. Then, drag the row header for the variable
from a data grid 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.
➢ To open the Settings dialog box: from the Component Editor, select the Options menu, then select Settings.
Property Description
Controller Parallel Online When set to True, allows you to download application code to redundant controllers in
Download parallel
Show Boot Loader Displays the boot loader in the Download Wizard when it does not have to be downloaded
Enable I/O diagnostic Alarm When set to True, makes available I/O diagnostic alarm events for automatic updates in
Events the I/O Diagnostic Viewer.
When set to True, displays diagnostic icons in the Tree View and serves as a permissive to
Show Diagnostic Icons
show more enhanced diagnostic icons in both the Tree View and the Summary View.
Show More Enhanced Diagnostic When set to True, displays enhanced diagnostic icons in the Tree View and the Summary
Icons View (Show Diagnostic Icons must be set to True for this option to be enabled).
Access Rights
Access Rights Description
Allows you to set Modify Data and Modify Design access rights to pre-defined user roles. Once roles
Access Roles
have been assigned to a protected object, only users with those roles can access the object.
Allows you to make changes to data values associated with an object without changing how it works.
Modify Data 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.
Allows you to change the way a protected object works. For example, this protects block creation and
Modify Design 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.
Note Passwords are case-sensitive – secret and Secret are not considered to be the same password.
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.
➢ To clear all passwords and protect the component: from the Device menu, select Restore Password
Protection.
Protection Properties
Property Description
Access Roles Allows you to set modifying data and design rights to previously defined user roles
Allows you to modify data values and forcing of variables
➢ To upgrade a component
Redundant Safety I/O packs mounted on the same terminal board must all be the
same hardware form, and running the same firmware version.
Do not attempt this replacement unless you have enough I/O packs with the newer
hardware form available, including spares.
Attention It is recommended that you back up the ToolboxST .tcw file prior to upgrading the
system.
After a component has been upgraded, you cannot undo the upgrade. You also cannot
upgrade a component to its current or a previous version.
Attention
1. Install the latest version of the ToolboxST application.
2. Open the ToolboxST application, open the system .tcw file, and double-click a component.
3. From the File menu, select Upgrade.
4. Select the component(s) and appropriate I/O modules to upgrade.
In the Version Upgrade dialog box, the New column defaults to the highest compatible version that supports the existing
I/O module hardware.
If any version does not support the hardware of the existing I/O module, a Caution
symbol is displayed in the New column. This notifies the user that they should only
upgrade the version if the intent is to replace the existing I/O module with supported
hardware.
Attention
When any of the I/O modules are selected for upgrade to a version
that does not support the hardware , a Warning dialog box displays
requesting user confirmation to proceed . If you select Yes , the
selected I/O modules will be upgraded .
5. From the Version Upgrade dialog box, click OK to upgrade the component.
Variable generates a list of all global or configuration variables. You can also
generate a Web variable report, a Compressed Data Log variable report, an
EGD variable list report, Alias report, or a Second Language report.
Block Pin generates a list of all block pins in the controller software.
Coding Practices opens the Options for Coding Practice Report dialog box.
Generate a list of both control constants and undriven variables (refer to the
Constants
section Constants).
Diagnostics Display regular and advanced controller diagnostics, as well as I/O status.
IO CheckOut Open the IO CheckOut dialog box
Display state exchange voting and output disagreements for the dual and
Disagreements
TMR controllers
Export Alarms for
Compare alarm criteria in plant alarm philosophy
Rationalization
Note The first time you attempt a password-protected function, the Enter Password dialog box displays. All protected
functions performed during the remainder of the ToolboxST session do not require re-entering the password.
Attributes Columns
Column Description
Name Unique identifier for the attribute
Description Stores added comments about the attribute
Value Displays and modifies the current attribute value
➢ To open the Attribute Value Editor: from an attribute Data Grid, click a Value Cell and click the Ellipsis button.
Name of the
attribute
being
modified
If selected, the
attribute values
are restricted to
an enumeration
(a predefined
set of allowable
values).
Note The first time you attempt a password-protected function, the Enter Password dialog box displays. All protected
functions performed during the remainder of the ToolboxST session do not require re-entering the password.
➢ To change the network redundancy: from the Hardware tab Tree View, select the Distributed I/O item.
With TMR
selected,
select the
YSIL I/O pack
and click Next
Note The YSIL I/O module cannot be selected unless the module redundancy is TMR.
Click Next
The Summary tab displays a graphic representation of the YSIL I/O module.
Bar Code
Position
Physical Position
Position
Bar Code
ENET1 Port
ENET2 Port
• Alarm
• Revision
• Communication
• Hardware
Click to toggle
between layout
mode and
group mode
➢ To create a Group: from the Hardware tab Tree View, right-click Distributed I/O and select Add Group.
Enter a
Description
(optional).
2. When the cursor changes to a symbol, release the mouse button to move the module.
Modifiable properties
include:
Terminal Board Type
Bar Code
Position
TB Connector
Summary View
displays I/O modules in
either group or network
layout. Click the folder
icon to toggle between
the two views
When you select a module from the Tree View, the Summary View provides tabs. The tabs that display vary according to the
I/O module. Tabs that display for all I/O modules include:
• Summary
• Variables
• Diagnostics
• Status
The Summary View toolbar is as follows:
The I/O module in this example is a YAIC. The Summary tab displays a graphical overview of the selected module,
including any diagnostics.
Note Some infrequently used parameters are classified as Advanced, and are hidden by default. To display Advanced
parameters, click the Show/Hide Advanced button on the toolbar.
Note For some I/O modules, these tabs are split into more module-specific input/output tabs that better define their function.
The Variables tab displays available variables from the I/O module that have no physical endpoint. These variables exist
only internally in the I/O module, and can be connected to another variable for use in code.
The Extra Circuits tab contains input/output variables found on the I/O module terminal boards, which can be associated
with the application software. For some I/O modules, these tabs are split into more I/O module-specific input/output tabs that
better define their function.
The Input and Output tabs contain input/output variables found on the I/O module terminal boards, which can be
associated with the application software.
The Diagnostics tab allows you to check Alarms and errors on I/O packs. Each I/O pack has a unique set of diagnostic
signals that can be monitored.
Inactive Alarm(s)
Active Alarm(s)
Note For more information about the fault codes used in an I/O pack, refer to the Mark VIe and Mark VIeS Control Systems
Guide (GEH-6721_Vol_III).
Note A software item (program, tasks, and such) must be defined in the Software tab before this feature can be performed.
➢ To attach a software variable to an I/O variable: from the Data Grid, select the Variables tab.
You can also attach a variable by entering the variable name in the Connected Variable column and pressing Enter. If the
variable name entered is a defined variable, it continues to display and the cursor moves to the next field. If the variable name
entered is undefined, click Yes when the Undefined Variable window displays.
Note To upgrade multiple I/O modules simultaneously, refer to the section Upgrade Component and I/O Modules.
➢ To upgrade a module: from the Tree View, right-click the module and select Upgrade.
Normal
Inactive Alarm(s)
Active Alarm(s)
Link broken
Link error
Link warning
Link information
Note Place the mouse over the icon to display Tool Tips.
➢ To download parameters to a module: from the Hardware tab Tree View, right-click the module to be
downloaded and select Download Parameters.
Module parameters directly affect the operation of the controller and associated I/O
modules. To reduce the risk of improper operation or damage to the unit, always
check the Compare Parameters dialog box before downloading new parameter values
to a component.
Caution
➢ To open the Compare Parameters dialog box: from the Hardware tab Tree View, right-click a module to
compare and select Compare Parameters.
Note The first time you attempt a password-protected function, the Enter Password dialog box displays. All protected
functions performed during the remainder of the ToolboxST session do not require re-entering the password.
If adding a
program group,
enter a name
and click OK
Note The Add Existing Program command reads an .xml file from another system or controller into the current controller.
➢ To add a task: from the Tree View, right-click the name of an embedded or unlinked program and select Add Task.
Enter a Name to
insert an
embedded task
or
select the Select
Library Block
check box to insert
a linked task.
Select a
category and a
definition from
that category.
Enter a name
for the linked
task.
Click All to
display all
categories and
definitions.
Click None to
clear all
categories.
When the controller is online, double-click the live value of the variable _Enable for the task, select True to enable the task
or False to disable the task, then click Send & Close.
Disabled
Task Disabled
• Function block libraries describe software that is part of the controller firmware
• User block libraries combine these function blocks into user blocks
The Instance All command creates a new copy of all linked user blocks from the referenced user block libraries. In addition to
updating the user blocks, this command causes the instance scripts and text substitutions to run.
The Protection
property defines
access rights to
the properties list.
➢ To instance a user block: from the Tree View, right-click a user block and select Instance.
Note Variables can also be added in the Summary View by directly editing the append row of the variable grid.
User block attributes only display on linked or unlinked user blocks whose user block definition contained attributes in the
library. They can be modified so that when their parent user block is instanced, the modified attributes are used in the scripts
and text substitutions that access them.
Note Linked tasks and user blocks can also be unlinked permanently.
➢ To unlink a program: from the Tree View, right-click a program item and select Unlink Permanently.
The linked icon next to the item in the Tree View changes and the program is unlinked from the library.
➢ To add a variable to a program: from the Software tab, expand the Programs item.
Note Variables can also be added in the Summary View by directly editing the last row of the variable grid.
Variables can be edited both in the Data Grid and the Property Editor. The Data Grid is used to view or edit variable
definitions, and can be configured to display a subset of the variable properties.
From the
Summary View,
select a variable.
From the Type
drop-down list,
select the
variable type.
Or:
from the
Property
Editor,
select Type
and the
variable type
Note When the first Produced Page is created, it automatically becomes the default page.
Tip � Any variable defined with $Default as the EGD page name is automatically placed on the currently selected default
page.
➢ To delete a page: from the Tree View, right-click the page to delete and select Delete.
➢ To compress a single page: from the Tree View, right-click the page to compress and select Compress.
➢ To compress all Produced Pages in a component: from the Tree View, right-click Produced Pages and
select Compress All.
Tip � If the variable to be added to the EGD page is already in use on the Software tab, you can add the variable without
using the EGD tab. To add a variable from the Software tab, select the desired variable(s) in the Summary View and set the
EGD Page property using either the Summary View or the Property Editor.
➢ To add a variable to a produced page: from the Tree View, right click a Produced Page and select Add
Variable to display the Select a Variable dialog box.
➢ To delete a variable from an EGD Page: from the Summary View, right-click the variable to delete and select
Delete Selected Row(s).
➢ To copy variable information from an EGD Page to the clipboard: from the Summary View, right-click a
variable and select Copy Selection. The data is copied in .csv format.
Note To edit exchange signatures and configuration time, set the Layout Mode property to Manual. The Layout Mode
property displays when a Produced Page is selected in the Tree View.
3. Review the warning about manual Exchange Signature editing and click OK.
4. Make any desired changes to the signatures and configuration time and click OK.
Filter Toggle defaults to a filtered state. It displays items that have the same name but have a different Producer ID as
the open component.
Delete deletes the selected item(s). If the item(s) were saved as part of the configuration, they can be added again.
The EGD configuration server uses the producer ID to store all the documents for an EGD node.
When a component is saved, the EGD configuration is automatically published to the EGD configuration server. To avoid
unintentional overwriting of data, do not configure more than one .tcw file for a server.
• Compare command compares the component's EGD-produced data configuration with the EGD configuration server’s
content.
• UnConsumed Data command generates a report showing variables produced by this component that are not listed in
any other device’s consumed data file.
Note You can select devices to search against. The individual pages, with just variables, perform the same Compare.
The Referenced Devices item on the EGD tab also has a Compare command that compares the consumed variable
information for the open component against the EGD configuration server’s content.
Note When EGD configurations are edited in remote devices, you must refresh the configuration to ensure that the latest
variable information is used. The configuration is automatically refreshed when a component is opened, and when a Build is
performed in the component.
➢ To refresh the configuration of a referenced device: from the Tree View, right-click the device to be refreshed
and select Refresh.
➢ To create undefined variables for a single or multiple referenced device(s): from the Tree View, right-click
either the device or Referenced Devices and select Create Undefined Variables.
Note Modifying Modbus properties results in a minor difference in the ToolboxST configuration. However, removing all
Modbus points creates a major configuration difference that forces an offline load.
Modbus Properties
Property Description Valid Range
Specifies the time in minutes that the slave remains connected to the master over
Connection Timeout 1 to 10
Ethernet when no requests are being received.
Port choices:
Ethernet Port Specifies the Ethernet port to be used for slave-Ethernet communication
502 and 503
Specifies the timeout period expressed as character time X 10. For example, 35
Inter-Character Timeout
represents 3.5 character times, or 0.0036 seconds at 9600 baud, 1 start bit, no 35 to 1000
(ICT)
parity, 1 stop bit.
Choices:
None, Odd,
Parity Specifies check character Even,
Mark, and
Space
Response Delay Additional delay time in ms before the slave responds to a master request. 0 to 999
Limits the number of commands processed per second. This is based on commands
Command Limit that have changed, not commands that are identical to previously received 0 to 25
commands.
Data Swapped Changes the transmission order if the data is greater than 16 bits when set to True. True or False
Settings Example
If set to True 32-bit example: 0x01234567 would be transmitted as 0x45 0x67 0x01 0x23
64-bit example: 0x0123456789ABCDEF would be transmitted as 0xCD 0xEF 0x89 0xAB 0x45 0x67
0x01 0x23
If set to False 32-bit example: 0x01234567 would be transmitted as 0x01 0x23 0x45 0x67
64-bit example: 0x0123456789ABCDEF would be transmitted as 0x01 0x23 0x45 0x67 0x89 0xAB
0xCD 0xEF
NAK Code specifies the Negative Acknowledge code to be used if data is requested from a controller that is incapable of
receiving the Modbus request. Possible codes are 4, 6 or None. None is selected only if the Modbus Master needs no reply
when communication fails between the Mark VIeS Safety controller and the target processor.
The ToolboxST application allows you to specify the variables on each page using a Data Grid. When you add a variable to a
page, both the Modbus Slave and the selected page are enabled on the controller. As you add and remove variables, the
controller is updated so that only pages containing variables are enabled. To completely disable the Modbus Slave, remove all
variables on all pages or from the Property Editor, select None as the Interface.
When a variable is added, the columns that display are listed in the following table.
Variable Columns
Column Description
Variable that is read or written from the device or the referenced device
Connected Variable
A connected variable must be added before the other columns become active.
Determines the variable data type and the registers used to transmit the variable data over a Modbus
connection as follows:
• BOOL is one bit of a 16-bit word (this is the only option if the connected variable is a BOOL.) All
BOOLs within a word must be set to the same Read direction.
• INT is a signed 16-bit word that takes one register
Point Data Type
• UINT is an unsigned 16-bit word that takes one register
• DINT is a signed 32-bit word that takes two registers
• UDINT is an unsigned 32-bit word that takes two registers
• REAL is a signed 32-bit float that takes two registers
• LREAL is a signed 64-bit float that takes four registers
Specifies the register address
When a variable is created, the address is automatically set to a value adjacent to the highest address
previously on the page, but the automatic value can be modified. Data types that are 32 bits or more
Address (DINT, UDINT, REAL, and LREAL) should be placed on odd addresses. The valid range for addresses
is 1 to 65534. When specifying an address for a BOOL variable, the bit 0-15 within the 16-bit word is
represented by a decimal. For example, 1.00 selects register address 1 and bit 0, and 10423.7 selects
register address 10423 and bit 7.
Raw Min Convert Modbus Slave variable data into engineering units
Raw Max The Raw Min and Raw Max columns control the minimum and maximum for the raw data. The Eng Min
Eng Min 0 and Eng Max columns control the minimum and maximum engineering units to which the raw data will
Eng Max be scaled. (The BOOL data type cannot be scaled.)
Read-only identifier automatically generated from the register page name, the address, and, if
Name
necessary, an added unique number
Note The range of the Modbus variable is determined by the data type and not by the scaling record. Each integer data type
has an implied range. The raw data range in the scale dialog box is only used to compute the gain and offset of the variable
when converting it to a signal.
Note To ensure data coherency, LONG Modbus variables should always start on an odd register number, and the master
should send both registers to the controller in the same Modbus transaction.
To ensure data coherency, FLOAT Modbus variables should always start on an odd register number, and the master should
send both registers to the controller in the same Modbus transaction.
Station ID Function Code … Function Specific Data … CRC-16 MSB CRC-16 LSB
Station ID (follower address) is a number from 1 to 255 that specifies the unit with which to communicate.
Function code specifies the purpose and format of the remaining message portion.
CRC-16 are two bytes that complete every serial Modbus message. These bytes check errors and are calculated to ensure that
no transmission error occurred while the message was in transit. The method for calculating the CRC-16 is a public protocol.
Refer to the Gould Modicon Modbus Protocol Reference Guide for information on calculating a correct Cycle Redundancy
Check (CRC).
The same functions are supported over Ethernet and the serial ports. All Modbus messages are received on the specified
Ethernet port. The Ethernet physical layer provides a CRC-32 check on all transmissions so the Modbus CRC-16 is not
included. Modbus over Ethernet adds the following header to the message formats.
Function Code (01) Start Coil (MSB) Start Coil (LSB) Number of Coils Number of Coils
(MSB) (LSB)
Starting output coil number is two bytes long, and can be any value less than the highest output coil number available in
the output coil table. The starting output coil number is equal to a number one less than the first output coil returned in the
normal response. For example, to get the first output coil, enter 0 for the starting output coil number. The high-order byte of
the starting output coil number field is sent as the first byte. The low-order byte is sent next.
Number of output coils to return is two bytes long, and must be from 1 to 2000, inclusive. It specifies the number of
output coils returned in the normal response. The sum of the starting output coil value and the number of output coils must be
less than or equal to the highest output coil number available in the output coil table. The high-order byte of the number of
output coils field is sent as the first byte. The low-order byte is sent next.
The normal message reply from the controller is formatted as follows:
Byte count is a binary number from 1 to 250. The specified number of data bytes follow.
Data bytes (data field) are the packed output coil status data. Each byte contains eight output coil values. The LSB of the
first byte contains the value of the output coil whose number is equal to the starting output coil number plus one. The value of
the output coils are ordered by number, starting with the LSB of the first byte and ending with the MSB of the last byte. If the
number of output coils is not a multiple of eight, then the last data byte contains zeros in one to seven of its highest order bits.
Function Code (02) Start Coil (MSB) Start Coil (LSB) Number of Coils (MSB) Number of Coils (LSB)
Starting input coil number is two-bytes long and can be any value less than the highest input coil available in the input
coil table. The starting input coil number is equal to one less than the number of the first input coil returned in the normal
response. For example, to get the first input coil, enter zero for the starting input coil number. The high order byte of the
starting input coil field is sent as the first byte. The low order byte is sent next.
Number of input coils to return is two-bytes long and must be from 1 to 2000, inclusive. It specifies the number of input
coils returned in the normal response. The sum of the starting input coil value and the number of input coils must be less than
or equal to the highest input coil available in the input coil table. The high order byte of the number of input coils field is sent
as the first byte. The low order byte is sent next.
The normal message reply from the controller is formatted as follows:
Byte count is a binary number from 1 to 250. The specified number of data bytes follow.
Data bytes (data field) are the packed input coil status data. Each byte contains eight input coil values. The LSB of the first
byte contains the value of the input coil whose number is equal to the starting input coil plus one. The value of the inputs are
ordered by number, starting with the LSB of the first byte and ending with the MSB of the last byte. If the number of input
coils is not a multiple of eight, then the last data byte contains zeros in one to seven of its highest order bits.
Function Code Start Register Start Register Number of Registers Number of Registers
(03) (MSB) (LSB) (MSB) (LSB)
Starting holding register number is two-bytes long and can be any value less than the highest holding register number
available in the holding register table. The starting holding register number is equal to one less than the number of the first
holding register returned in the normal response. For example, to get the first holding register number (holding register
number one) enter zero for the starting holding register number. The high order byte of the starting holding register number
field is sent as the first byte. The low order byte is sent next.
Number of holding registers value is two-bytes long and must be from 1 to 128, inclusive. It specifies the number of
holding registers returned in the normal response. The sum of the starting holding register value and the number of holding
registers must be less than or equal to the highest holding register number available in the holding register table. The high
order byte of the number of holding registers field is sent as the first byte. The low order byte is sent next.
The normal message reply from the controller is formatted as follows:
Function Byte Count First Register First Register … Data Registers Last Register (LSB)
Code (03) (MSB) (LSB) Requested …
Byte count is an even binary number from 2 to 254, or 0. If the byte count is 0, then the master assumes 256 data bytes
follow. Otherwise, the specified number of data bytes follow, not including the two CRC-16 bytes (serial mode).
Holding registers are returned in the data field in numerical order, with the lowest number holding register in the first two
bytes and the highest number holding register in the last two bytes. The number of the first holding register is equal to the
starting holding register number plus one. The high order byte is sent before the low order byte of each holding register.
Function Code (04) Start Register Start Register Number of Registers Number of Registers
(MSB) (LSB) (MSB) (LSB)
Number of input registers value is two-bytes long and must be from 1 to 128, inclusive. It specifies the number of input
registers returned in the normal response. The sum of the starting input register value and the number of input registers must
be less than or equal to the highest input register number available in the input register table. The high order byte of the
number of input registers field is sent as the first byte. The low order byte is sent next.
The normal message reply from the controller is formatted as follows:
Function Code Byte Count First First Register … Data Registers Last Register (LSB)
(04) Register (LSB) Requested …
(MSB)
Byte count is an even binary number from 2 to 254, or 0. If the byte count is 0, then the master assumes 256 data bytes
follow. Otherwise, the specified number of data bytes follow, not including the two CRC-16 bytes (serial mode).
Input registers are returned in the data field in numerical order, with the lowest number input register in the first two bytes
and the highest number input register in the last two bytes of the data field. The number of the first input register in the data
field is equal to the starting input register number plus one. The high order byte is sent before the low order byte.
Data bytes (data field) are the packed output coil status data. The data byte contains eight output coil values. The LSB of
the byte contains the value of output coil number one. The MSB contains the value of output coil number eight.
• Variable
• Block Pin
• I/O
• Alarm
• GE Rationalization
• Hold
• Event
• NovRAM
• IONet EGD
• I/O Diagnostics
• Coding Practices
• Unlinked Programs/User Blocks
• Global variables
• Variable configuration
• Web
• Compressed data log
• EGD point list
• Alias
• Second language
Double-click a Global
Variable to go to where
the variable is defined
in the application code.
Note Intrinsic variables are not defined in the application code configuration. The Where Used tab displays locations in the
configuration where the intrinsic variables have been used.
Double-click a variable
to go to where the
variable is configured
in the application code.
Note Intrinsic variables are not defined in the application code configuration. The Where Used tab displays locations in the
configuration where the intrinsic variables have been used.
The Web report provides variable name, description, type, alias, second language description, and location in the application
code, as well as where the variable is used and if the variable is written multiple times in the code.
To generate a Variable Web report, Controller Web Pages must be enabled and the
variables must have the Download Info column set to True.
Attention
1. Generate a Web report.
Double-click a variable to go
to where the variable is used
in the application code.
2. To enter alias names, save the report as a .csv file, enter alias names, then import the data back into the ToolboxST
system.
From the View menu, select Reports, Variable, and Second Language.
The Software tab displays the program, task, and block in which the pin is used.
Double-click the associated pin to display the connections.
From the View menu, select I/O, then select
to display the report results.
From the variable report, double-click an I/O variable to display the configuration.
The Alarm report provides a list of all alarms in the current configuration and the aspects associated with them. Users can
view the module(s) associated with the alarms in the Alarm Viewer for alarm troubleshooting.
Alarm help files are only generated when the Publish Alarm Help property is set to
True in the system Property Editor.
Attention
The Hold report identifies all steam turbine variables marked as Holds for troubleshooting and information reference.
The NovRAM report lists all configured variables that are downloaded and used in the RAM and marked as non-volatile.
NovRAM variable values are saved so in the event of power loss or if you power down and power up, the controller restores
the last stored values.
• Alarm
• Revision
• Communication
• Hardware
From the View menu, select Reports, I/O Diagnostics, and Alarm.
From the Group Level, select Create Module Report, and Alarm.
From the View menu, select Reports, I/O Diagnostics, and Revision.
From the Group Level, select Create Module Report, and Revision.
2. Locate a module in the report and view the details in the Status Viewer.
From the View menu, select Reports, I/O Diagnostics, and Communication.
From the Group Level, select Create Module Report, and Communication.
From the View menu, select Reports, I/O Diagnostics, and Hardware.
From the Group Level, select Create Module Report, and Hardware.
• Unwritten variables
• Multiple writes
• Multiple output assigned variables
• Unused I/O
From the Coding Practices report , double-click a variable to display the configuration.
• Open report
• Save report
• Retrieve (generate) report
• Print report
• Sort (modify) columns
• Filter
• Refresh
• Zoom
• Find text
• Help
Toolbar Icons
Icon Description
Zoom in
Zoom out
Get help
➢ To save a report
ToolboxST system.
➢ To sort a report column: click any column heading to apply a sort to that column. The first click sorts the column in
ascending order; a second click sorts the column in descending order.
Column
names that
display in
blue cannot
be moved.
➢ To apply a report filter: from the Report menu, click Apply Filter to open the Edit Report Filter dialog box.
Available Available
columns comparison
(double-click and Boolean
to add to an operators
equation) (double-click
to add to an
equation)
Click to add
parentheses
Click OK to
accept the
filter equation
Enter filter that displays.
equation to
be used. Click Clear
to delete the
equation.
Click Cancel
to cancel the
equation but
keep the
current
settings.
When using the LIKE operator, you can prefix or suffix a wildcard character, either * or
LIKE
%, to the right-hand value. The wildcard character can stand for any number of
alphanumeric characters, including zero. The wildcard character can only be present
at the beginning or the end of the right-hand value (for example, *value or value* or
*value*)
AND Expressions to the left and right of the AND operator must both be True
OR Either the expression to the left or to the right of the operator must be True
NOT Expression to the right of the operator must be False
You can use as many groups of parentheses as necessary to define an expression.
String values must be enclosed in single quotes , for example 'string'
➢ To remove a report filter: from the Report menu, click Remove Filter. The filter is removed and all available rows
display.
➢ To save a filtered report: from the File menu, click Save Report.
➢ To search for text within a report: from the Report menu, click Find to display the Find dialog box.
If selected,
capitalization
in the test
string must
match the
text in the
report exactly
• I/O Variable
• I/O Configuration
• Global Variable
• Block Pin
• Variable Alias
• Second Language
• GE Rationalization
Only the Alias and Second Language properties can be modified. The Variable Alias report and the Second Language report
can be imported from either a .csv or an .xml file. The other reports can only be imported from a .csv file.
➢ To import an I/O Variable, I/O Configuration, Global Variable, or Block Pin report
1. From the File menu, select Import and the desired report.
2. From the Open Report dialog box, select the report and click Open to import the data. Any data that cannot be
modified is highlighted when the report displays.
Tip: Change the Save as type to All Files (*.*) so you will
still be able to save the file as a .csv file.
Click Save .
5. Import the file into ToolboxST and verify that all the special characters display correctly.
If you use Microsoft Excel to modify the .csv file, make sure you save the file back to a
.csv file from an .xls file.
If the .csv file contains UTF-8 special characters, to avoid issues with displaying
special characters after import back into ToolboxST open the file with Notepad and
Attention save the file with Encoding set to UTF-8. Refer to the procedure To avoid issues with
second language special characters during import.
➢ To open a stand-alone Watch Window: from the Start menu, select All Programs, GE ControlST, ToolboxST,
and Watch Window.
➢ To create a Watch Window: from the System Editor Tree View, right-click the system and select Insert New,
Tool and Watch Window.
Enter a Name,
and a Description
(optional), and
click OK.
Note If this Watch Window is being opened for the first time, the list is empty. Add or import a new Watch Window.
➢ To open an existing Watch Window: from the System Editor Tree View, right-click the system and select Insert
Existing and Watch Window.
➢ To open a Watch Window: from a Component Editor View menu, select Watch Windows.
If you selected
System
Component in the
previous page,
select the desired
component from
the drop-down list
and click Next.
The variables
will display here.
Click Finish .
Once a variable is added to a Watch Window, right-click the variable row header to perform the following actions:
Note When a system component providing signals to a Watch Window is replicated, the Watch Window is replicated as
well.
Forcing of protective functions is never permissible for an operating unit. All safety
Warning measures should be strictly enforced in conjunction with this procedure.
Note The Watch Window tool only exports grid columns necessary to retrieve variable information. For example,
DatasourceName from the exported file is used to retrieve the variable’s remaining properties from the system. User-defined
columns such as User Comment are also included.
➢ To save a Watch Window: from the <Watch Window name> File menu, select Save As to save the Watch Window
as a .watch file in a user-selected location,
or select Save to save the Watch Window as a .watch file in the Tools folder in the system.
13.22 LiveView
The LiveView feature allows you to display a graphical representation of live data from various sources in the system.
LiveViews can be added to a ToolboxST system, to a component, or opened as a standalone editor.
➢ To add an existing LiveView: from the System Editor, right-click the system and select Insert Existing and
LiveView.
➢ To edit a LiveView: from the System Editor, right-click a LiveView and select Edit System Component.
➢ To add a LiveView from a Component Editor: from the View menu, select LiveViews.
Reference point
Select a Bar
Color for the
High Alarm and
High Warning
range above the
reference point
Select a Bar
Color for the
Normal range
above the
reference point
Select a Bar
Color for the
Low Alarm and
Low Warning
range above the
reference point
If the Behavior
property is set to
Momentary and
the On Push
property is set to
False, the state of
the attached
variable is set to
True when the left-
mouse button is
clicked
Locked enables
or disables the
ability to move
and resize objects
Locked Property
Or
Variables display
here. Click
Finish
Note You can also attach a variable by entering the variable name in the Property View.
➢ To display constants
➢ To display constants
The Reconcile Differences dialog box displays constants with both initial and live values.
• For constants when the ToolboxST initial value was checked, that value is either sent to the controller (where the OK
button is clicked), or a pcode record is created, causing the next online download to change both the initial and live
values.
• For constants when the live value was checked, the ToolboxST initial value is set equal to the controller live value. This
causes a minor revision configuration change to Not Equal. A Build and Download to the controller is required to
complete the reconcile function.
➢ To display I/O values: from the Hardware tab, select an I/O module.
Click Unlock
and Close
The Locked attribute shows the status as Yes or No for the controllers.
• From the Device menu, select the Brand command. Or, from the toolbar, click the Brand icon. The Brand
attribute shows the cyclic redundancy check (CRC) values for the controllers, which verifies the integrity of the data.
Color Conditions
All controllers functioning normally.
- Control state is controlling
- Controller and DDR Equality equal
One or more of the following:
- Control state not controlling
- Controller and DDR Equality not equal
- Idle or Frame Idle Time < 20%
One or more of the following:
- Control state is failed
- Controller Equality has a major difference
Major difference
• Compressing variables
• Changing frame rate
• Changing the background blockware period
• Adding the first I/O pack to a controller
• Changing redundancy type
• Changing the platform type, which changes the number of Ethernets
• Changing any NTP configuration on a controller
State Description
Powerup Power up controller
Master initialization Controller is loading its own configuration
Designated controller determination Determine which controller is designated in a redundant controller configuration
Perform initialization of non-designated controllers with NVRAM, command variables,
Data initialization
and constants
Inputs enabled Wait in this state for all required I/O packs to start transmitting inputs
Input voting Check voting inputs prior to execution of application code
Exchange initialization Populate redundant controllers with dc state variables prior to voting
Exchange state variables so that a controller joining a running system won’t have a
Exchanging
step in its initial calculations
Turn on the application code and execute each task at least once before driving
Sequencing
outputs
Controlling Turn on outputs
Loading Online load is in progress
Load complete Online load has finished. Wait for re-synchronization of redundant controllers
Fail Failure has occurred
Note This feature is available if it is supported by your version of the Mark VIeS control.
The ToolboxST application can be used to increase security protection for controllers. Controllers can be run in either of two
states: Open or Secure. When the controller is in the Open state, it processes all commands received. In the Secure state,
certificates are used to verify both the identity of the user accessing the controller and the actions that the user is allowed to
perform.
The Secure state requires that certificates be assigned to both the controller and the user accessing the controller. Certificates
are issued by a Certificate Authority (CA) Server.
Controllers request certificates directly from the CA Server using the IP address and CA name that was configured in the
system. The CA Server must be available when the controller requests a certificate and switches from the Open to the Secure
state. When the controller certificate expires, a new one is obtained by taking the controller from Secure to Open state and
back again.
The user certificate is also issued from the CA Server and stored in the user certificate store. The ToolboxST application
retrieves the certificate from the store, and uses it to establish a secure connection to the controller. User access levels are
defined in the certificate. The controller uses this information to determine which user commands to accept and which to
reject.
Note When the user certificate expires, refer to the SecurityST* Cyber Security Management System Maintenance Guide
(GEH-6765) for the renewal procedure.
A second server, called a Remote System log (RSyslog), logs all security-related events. To send security-related messages, a
controller must know the IP address of the RSyslog. The RSyslog also receives security-related messages from the
ToolboxST application. Examples of data collected by the RSyslog include:
For dual and TMR configurations, select Go to Secure for each controller.
Attention
Note When the process is in the Authenticated state, the controller is retrieving a certificate revocation list from the CA
Server to verify that the requestor has a valid certificate.
The Component Info View Status tab displays the Security state for each configured controller.
A controller cannot communicate on a network until these controller setup tasks are
completed.
Attention
Prerequisites
Note If using a Shared IONet system, repeat the procedures in this section for both the Mark VIe and VIeS components (or
Mark VIe and Mark Stat components).
• The control system hardware and network cabling have been connected properly
• All system equipment has been successfully powered on.
• The controller has been added to the system with the correct redundancy
If this is a new UCSB controller received directly from the factory, or a UCSB that has
not been previously configured, the IP address must be set using a USB flash device.
Skip to step b in this procedure.
Attention
i. Enter the device password and select a COM port and the appropriate Channel.
ii. Connect an RJ-45 serial cable adapter from the main board of the controller to a serial port on your computer:
Note Refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose Applications System
Manual (GEH-6721_Vol_II), the sections UCSC Restore and UCSB Backup and Restore for these procedures.
i. Apply power to the controller while continuing to press the button until the On LED on the front of the
controller becomes solid green, then release the button. The On LED turns off when the process is complete.
ii. Remove power from the controller, remove the USB flash device, then re-apply power to the controller.
iii. If using redundant controllers, repeat this procedure for the S and T controllers (if TMR) or S (if dual). Be sure
to select the correct Channel.
• The control system hardware and network cabling have been connected properly
• All system equipment has been successfully powered on.
• The controller has been added to the system with the correct redundancy
• The computer that runs the ToolboxST application and the controllers must be configured to be on the same subnet for
UDH Ethernet communication.
ii. Connect a serial cable adapter from the main board of the controller to a serial port on your computer:
iii. Click Next to continue.
iv. The Controller Setup Wizard displays the progress of the connection. When it is complete, click Finish.
v. Disconnect the Ethernet cable from the replacement controller’s COM port, and disconnect the serial adapter
from the engineering workstation.
vi. After the controller has restarted, verify the status of the controller. It should be online, in the controlling state,
with no warnings or errors. If the controller cannot go online, or the replacement controller does not go to the
controlling state, download to the controller.
vii. Configure the replacement controller and/or set of controllers with the site-specific Mark VIeS controller
password. Refer to the section Controller Password Change for further instructions.
i. Insert a non-encrypted removable USB 2.0–compliant flash device with a 4 GB minimum capacity into the HMI
computer USB port.
Note If the controller is configured as either simplex or dual, some channels may not be available.
iii. Remove the USB from the computer and load it into the controller, then click Finish.
The user must change the factory default controller password for a device. The
maximum number of characters for the new password is limited to characters. The
new password cannot be the factory default password. If you do not know the factory
default password, contact the nearest GE Sales or Service Office, or an authorized GE
Sales Representative.
Attention For additional details, refer to Mark VIe and Mark VIeS Control Systems Volume II:
General-purpose Applications, GEH-6721_Vol_II, the chapter Controller Diagnostic
Alarms, alarm 547.
Note For a device configured with redundant controllers, the password applies to all controllers in that device.
Note This password is required for configuring the network address during controller setup.
When the password for the replacement controller is successfully synchronized to the other controller passwords in the set, a
message displays in the Log window.
• Boot Loader starts the operating system for the controller and I/O modules, much like the BIOS on a desktop computer.
Changes to the boot loader are very infrequent.
Note Not all devices have the boot loader. In this case, the boot loader is contained within the base load.
Base Load contains the operating system for the controller and I/O modules. While changes to the base load are more
likely than changes to the boot loader, they still occur infrequently.
• Firmware provides the functionality of the controller and I/O modules. It can be updated over the lifetime of the
controller to incorporate new features and bug fixes.
• Application Code contains the configuration of the controller as created in the ToolboxST application. Whenever a
change is made to the configuration, the application code must be downloaded. There are two types of application code
download: online and offline. An online download (very commonly performed) changes the configuration without
interrupting control and the new configuration takes effect between control frames. An offline download requires a
controller restart (performed less frequently).
• Parameters contain specific configuration for the I/O modules.
Boot loader, base load, firmware, offline application code downloads, and parameter
downloads all require the target device to be restarted. Before downloading new
software to a controller, take the necessary steps to secure the control equipment to
prevent equipment damage and personal injury.
Warning
Note The type of software download needed is determined by which changes have been made to the controller
configuration.
The Download Wizard is used to download software to a Mark VIeS component and its distributed I/O modules over an
Ethernet connection. The Download Wizard can automatically examine the system configuration to locate out-of-date
software, or you can manually select individual items to download.
Note Certain conditions do not allow a download, such as an incorrect platform type. Check the Component InfoView for
errors that would prohibit a download.
1. From the Component Editor Device menu, select Download and Download Wizard.
Note If the controller is in Unlock mode, the download continues. If it is locked, refer to the section Safety Controller
Operations.
2. If you have changed configuration settings since the last Build operation, a message box displays indicating that the
software is out of date. Click Yes to build the current configuration.
3. When the welcome page displays, click Next.
Select Show
All to display
all software to
be downloaded
Click Next
4. Click Next when the following message displays: Downloading application code offline will shut the selected
controller(s) down. This will result in a process trip if running. I/O outputs will change during this
operation. Ensure that the process is secure prior to continuing.
5. When the Controller Download Status dialog box displays a completed download, click Close.
6. When the download is complete, click Finish. The Component InfoView Log tab displays any warnings or errors
that occurred during the download.
➢ To view and set the controller time: from the Device menu, select View/Set Time... and follow the instructions
on the ToolboxST windows.
➢ To replace an I/O module: from the Component Editor Device menu, select Upload. When the welcome page
displays, click Next.
Note The UCSC, as shipped from the factory, does not include the software on the controller to support communication
from the PHY PRES button to the EFA. The user needs to download to the controller at least once (using ToolboxST) to
enable this.
➢ To open the Controller Diagnostic view: from the View menu, select Diagnostics and Controller
Diagnostics.
In a TMR or dual
configuration,
select from the
drop-down list the
desired
redundancy
component from
which to retrieve
diagnostic
messages.
Displays
message:
• Timestamps
• Fault codes
• Status
(0=inactive
• 1=active)
• Human-
readable
descriptions
The I/O diagnostic view displays diagnostic messages for a component hardware I/O module. Retrieve these messages to
diagnose problems with hardware I/O.
➢ To open I/O diagnostic view: from the View menu, select Diagnostics and I/O Diagnostics.
• Causes that trigger an Effect are located in the rows on the left side of the Cause and Effect Matrix; the control system
detects these issues.
• Effects of the Causes are located in the column rows; these are the result if even one of the undesirable Causes occurs).
• The Intersection between a Cause and Effect indicates which Causes are tied to which Effects; an X indicates the Effect
is Active and a red X indicates the Effect is triggered.
Note The Virtual Mark VIeS controller also supports the Cause and Effect Matrix.
A Cause and Effect Matrix can support up to 32 Causes and 32 Effects. There is no limit to the number of Cause and Effect
Matrices a user can add to the application code.
Multiple Causes can be associated with an Effect and multiple Effects can be associated with a Cause (many-to-many
relationship). The Causes that correspond to an Effect are OR-ed to get the value of the Effect. This means that even if one
Cause for an Effect is True the Effect is active and triggered, which is indicated by a red X at the Intersection of the Cause
row and the Effect column. Any one Cause can result in the Effect if they intersect and are active. For example, if a user has
configured an Effect to shut off a pump, there could be six different Causes that result in this one Effect.
The ToolboxST application is used to configure the Cause and Effect Matrix and download the configured application to a
Mark VIeS controller or a Mark VIeS Virtual Controller. Each Cause can have up to six inputs (connected variables) and the
Cause is the result of logical operations configured for those six variables within the Cause row. Users can configure the
number of Cause inputs that trigger the Effect.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1025
GE Internal
The Cause and Effect Matrix features include:
• Causes
• Effects
• Intersection of Causes and Effects
• Tool Bar operations
• Variables and Pin connections
• Time Delay
• Bypass
• Cause set-point and hysteresis for Analog variables
• Latching
Note To display block help in ToolboxST, right-click the block and select Block Help or select the ToolboxST Info tab.
• Must have a system .tcw file with a Mark VIeS or Virtual Mark VIeS controller installed
• At least one program must be available to add the Special Task Cause and Effect
3. Repeat steps 1 and 2 to add multiple Cause and Effect tasks within the same program. Each task contains one Cause and
Effect Matrix, with one Cause and one Effect.
Note Users can also add also multiple programs and add Cause and Effect tasks to each program.
4. From the Tree View, select the task to display the Cause and Effect Matrix in the Summary View.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1027
GE Internal
Cause and Effect Matrix
Note By default, when a Cause and Effect Matrix is added, the Intersection of the Cause and Effect is active (indicated by an
X). Refer to the section Intersection of Causes and Effects for further details.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1029
GE Internal
15.4 Property Editor
The following table lists the Cause and Effect Matrix properties displayed in the Property Editor.
OR
From the Property Editor, select the
Show Description drop-down menu
and select True.
The description is displayed in the upper left corner of the block, beneath the block name.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1031
GE Internal
➢ To hide the block description from the Summary View
OR
From the Property Editor, select the
Show Description drop-down menu
and select False.
Note By default, when a Cause and Effect Matrix is added the Intersection is active.
➢ To display the Intersection association details between Cause and Effect: select the Intersection to highlight
it and view the association details in the Property Editor.
The Property Editor displays the Cause number, Effect number, if the intersection is active or inactive, and the intersection
number.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1033
GE Internal
➢ To activate or deactivate an Intersection: select the intersection to highlight it and select the box to activate (X) or
deactivate (no X) the Intersection.
Ac No
ti v
e t Ac
tiv
e
Tr
ig ge
re
d
• Add Cause
• Add Effect
• Delete Cause
• Delete Effect
• Add Cause Input Group
• Remove Cause Input Group
• Hide a Column
• Unhide All Columns
• Zoom In
• Zoom Out
• Print Cause and Effect Matrix
➢ To add a Cause: from the Cause and Effect Matrix tool bar, click the Add Cause icon.
One Cause is added to the block, with the corresponding variables for the newly added Cause and Intersection. Select the
Variables tree item for the block to view the variables.
Note The total number of Causes for one Cause and Effect Matrix cannot exceed 32.
➢ To add an Effect: from the Cause and Effect Matrix tool bar, click the Add Effect icon.
Note The total number of Effects for one Cause and Effect Matrix cannot exceed 32.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1035
GE Internal
➢ To delete a Cause: from the Cause and Effect Matrix tool bar, click the Delete Cause icon.
The deleted Cause, the intersections in the same row as that Cause, and any assigned variables are removed from the block.
The Causes in the row below the deleted Cause are renamed and the pin names (if variable is unassigned) for that row are
updated.
➢ To delete an Effect: from the Cause and Effect Matrix tool bar, click the Delete Effect icon.
2. From the Cause and Effect Matrix tool bar, click the Add Cause Input Group icon.
Note Up to six inputs can be added. After adding six inputs, the Add Cause Input Group icon is disabled.
The input is removed from the Inputs cell in the row of the selected Cause.
Note The Remove Cause Input Group icon is disabled if only one cause input is present.
Column Selected
2. From the Cause and Effect Matrix tool bar, click the Hide Selected Column icon.
➢ To zoom in on the Cause and Effect Matrix: from the Cause and Effect Matrix tool bar, click the Zoom In icon.
➢ To zoom out on the Cause and Effect Matrix: from the Cause and Effect Matrix tool bar, click the Zoom Out
icon.
Note Make sure you have a printer connected to your machine. Your local printer is used to print the Cause and Effect
Matrix.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1039
GE Internal
15.7 Configuration
In the basic configuration of a Cause and Effect Matrix, each Cause can have up to six configured inputs (connected
variables) that are displayed individually within the Cause row, and each Effect supports only one output (connected
variables). The Summary View displays the live values of the Cause inputs, the Cause output (True/False), the Effect outputs,
the state of Effect outputs (True/False) and the intersections (active/triggered/inactive). Connected variables can be:
Note For block help in ToolboxST, right-click the block and select Block Help or refer to the Mark VIeS Safety Controller
(SIL) Block Library (GEI-100691) for additional block information and block pin variables.
Note _OUTPUT and _LATCHED variables for each Cause and Effect and _INTERSECTION_VALUE for each Intersection
are placed on the EGD default page.
From the Tree View, select Variables for a Cause and Effect block to display all variables
for that block in the Summary View.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1041
GE Internal
Refer to the ToolboxST for a complete list of block variables.
Note If the user attaches a Global Analog variable to a Cause input, the corresponding Cause input’s Set Point and Compare
Function variables will be displayed just below the input.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1043
GE Internal
➢ To edit block pin connections and add/remove Cause inputs from pin connections
1. Place your cursor in a Cause row, Effect column, or Intersection and double click,
or right-click the Cause/Effect/Intersection and select Edit Pins from the menu.
The Edit Block Pin Connections — [pin] dialog box displays the pins for the selected Cause/Effect/Intersection.
Connected Variables
2. Enter or modify the Description field for the selected Cause/Effect/Intersection.
3. For a Cause, set the Inputs Count value (1-6) (enabled for Causes only) to add or remove inputs.
The Cause input, set-points, and hysteresis variables are added or removed as per the inputs count.
Note For an Effect and Intersection the Inputs Count field is disabled.
Each time a pin value is changed, perform a Build and Download the application code to display the expected results.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1045
GE Internal
15.7.2 Time Delay
A Time Delay can be configured to determine how long the Cause and Effect Matrix will wait in milliseconds (ms) to
transition the Cause output from False to True or True to False. It is used to filter spikes in the inputs (input goes from True to
False to True to False); the logic waits for the set amount of delay time (in ms) before the Effect is triggered. Specifically,
Causes and Effects support an ON time delay and an OFF time delay before an Effect is triggered.
The Time Delay variables are:
• Pickup Delay: occurs when the Cause or Effect transitions from False to True
− CAUSE#_PU_DELAY
− EFFECT#_PU_DELAY
• Drop Out Delay: occurs when the Cause or Effect transitions from True to False
− CAUSE#_DO_DELAY
− EFFECT#_DO_DELAY
Note Each time an Immediate Value is changed, you must perform a Build and Download the application code to see the
expected results.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1047
GE Internal
➢ To set an input value
1. Place the cursor in the input row and double-click to display the Send Value dialog box.
2. Enter a value in the Next Value Next field and click Send & Close, then click Close.
Note If the Bypass Limit value is zero, the bypass is not active.
Note When a Bypass is active, the Intersection displays as active and triggered (red X) but the Effect will remain False.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1049
GE Internal
➢ To enable a bypass value
1. Double-click the CAUSE#_ BYPASS_ENABLE pin to display the Send Value dialog box.
2. Select True or False for the value and click Send & Close, then click Close.
The operations that can be applied to Cause inputs are AND, OR, or VOTED. If the inputs are Analog, the resulting Boolean
condition after set-point and hysteresis comparisons is used for this operation. There can only be one operator type used for
all of the Cause inputs. The health of the input is considered for Cause output calculation. An unhealthy input is a vote to trip
(true). The operator type drives the health of the input as follows:
• If the operator is OR, the Cause output becomes True if any Cause input is unhealthy.
• If the operator is AND, the Cause output becomes True if all inputs are healthy.
• If the operator is VOTED, the Cause output becomes True if the number of unhealthy inputs is greater than or equal to
the configured input count number for the VOTED option ( (majority, such as 2-out-of-3 ratio), plus the number of
healthy inputs that are true. The user selects the Input Count (1-6) to set how many inputs have to be unsafe before the
Effect is triggered (meaning how many variables are True before it is tripped). The user configures the Initial Value for
the inputs, which is the number of input counts the user wants to trigger the Effect (trip).
Note The number of inputs (Input Count) has to be configured to use the VOTED operation.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1051
GE Internal
➢ To configure a set-point for hysteresis comparison
1. Associate the variable CAUSE#_INPUT1 with a Global Analog variable to give a safe signal for use in determining if a
trip condition exists. For this example, an Analog variable is selected, which prompts the user to add a set-point and a
compare function (GT or LT).
2. Set a compare high and a compare low by setting the CAUSE#_COMPARE_FUNC# variable Immediate Value.
3. For a Cause input, set a high and low value for hysteresis by selecting the controller value for the CAUSE#_
HYSTERESIS# variable as LT or GT.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1053
GE Internal
Cause Input Value Set Greater Than Set-point Value
6. Select the Variables Tree View item, confirm that the Cause input Type is INT.
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1055
GE Internal
15.7.5 Latching
Causes and Effects support latching. The user enables latching on a per Cause or Effect basis. The Cause or Effect allows
resetting the latch using a variable in the application logic. The user can latch the Cause, the Effect, or both. Once an Effect is
triggered, the user has to reset the latch, which unlatches the Cause and allows the Effect to reset. If a Cause or Effect is
latched, it will not rest until the user unlatches it. The user must set the variable LATCH_RESET to True to reset the Latch and
the output will return to False. To enable a Latch for an input, the variable CAUSE#_LATCH_ENABLE must be set to True
first. To disable the Latch, first set CAUSE#_LATCH_ENABLE to False.
Do not latch an Effect if you have latched the Cause(s) for that Effect.
Attention
➢ To configure a Latch
1. Set LATCH_ENABLE to True.
2. Set LATCH_RESET to Variable.
Latched Effect
Mark VIeS Cause and Effect Matrix GEH-6700AG User Guide 1057
GE Internal
Notes
➢ To create a component: from the System Editor Tree View, right-click the system name and select Insert New
and WorkstationST.
Tree View
lists all
major items
in the
component.
The list
changes
when a
different tab
is selected
Property
Editor
allows you
to edit the
item
selected in
the Tree
View
Component
InfoView
displays
specific
feedback
information
about the
currently
selected tab
➢ To edit the component: select an item in the Tree View. The configuration information for that item displays in the
Summary View and Property Editor.
➢ To edit a property in the Property Editor: select an item by clicking its value 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.
Note If no button displays, edit the value directly in the corresponding text box on the right side of the Property Editor.
Log Tip � If there is a build problem, the error is listed on the Log tab. Double-click the error. The input focus goes
to the location in the component configuration where the error occurred.
Status Displays operating state and equality information about the component
Keeps a navigation history for each user session and allows you to return to different places in the
History 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.
Finds all uses of a variable within a Library Container
The write icon at the beginning of some lines indicates that the variable is being written at that location.
Where 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.
Each time a Build is performed, a message displays that allows you to view the Change log.
When Errors or Warnings are present, the Log tab notifies the user by displaying the current count, as well as a description.
Click each button to hide the corresponding item. For example, click Warning to hide the warnings listed in the Log tab;
Click Warnings again to display the warnings in the Log tab.
Note Some Data Grids, especially those without an Append Row, may not support all features described in this chapter.
Data Grids are used to view or edit many of the configuration properties available in ToolboxST component editors. While
each Data Grid contains different columns and properties, several features are common to all Data Grids, including column
resizing, clipboard operations, and multi-row editing.
Quickly set a property to the Left-click the row header for the first row to be edited. Then, while pressing the CTRL key,
same value for multiple rows left-click added row headers. After selecting all desired rows, use the Property Editor to
change properties for all selected rows. (Some properties are omitted when a group of rows is
selected, and properties with conflicting values will display no value in the property editor.)
To... Do this:
Resize a column Drag the vertical bar on the right of the column header to a new location.
Quickly remove a single column Right-click the column header and select Hide Column.
Move a column to a different location Drag the column header to a new location.
Sort by a column Click a column header. The column sorts in ascending order. To sort in descending
order, click the column header again.
Reset columns to the original Right-click any column header and select Default Column Organization.
configuration
Add or remove columns Right-click any column header and select Organize Columns to display the
Organize Columns dialog box.
Select a
column name
and use the up
arrow to move
it to the left-
most side of
the Data Grid
in the destination grid and select Paste Row(s) to insert the row into its new
location.
Copy and paste multiple rows Left-click the row header for the first source row. Then, while pressing the CTRL key,
left-click added row headers. After selecting all desired rows, continue to hold down the
CTRL key and right-click any selected header. From the shortcut menu, select Copy
Selected/Current Rows to place the rows on the clipboard. Then, right-click the header
for the append row in the destination grid and select Paste Row(s) to insert the
rows into their new location.
Copy and paste a range of two or Click the top left cell of the desired range and drag to the bottom right cell. Right-click the
more cells selected region and select Copy Selected/Current Rows to place the cells on the
clipboard. Then, click the top left cell of the destination range and drag to select the
same number of columns and rows that were copied to the clipboard. Right-click inside
the destination region and select Paste Row(s).
Move rows between data grids Arrange windows on screen so both the source and destination grid are visible. (An
entry in a Tree View is acceptable as a destination). Left click the row header for the first
row. Then, while pressing CTRL, click any added row headers to be moved. Release the
CTRL key and drag a row header to the new data grid.
Add a variable to a block diagram, Arrange windows on screen so both the source grid and a destination block diagram,
Trender window or Watch Window Trender window or watch window are visible. Then, drag the row header for the variable
from a data grid 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.
Access Rights
Access Rights Description
Allows you to set Modify Data and Modify Design access rights to pre-defined user roles. Once roles
Access Roles
have been assigned to a protected object, only users with those roles can access the object.
Allows you to make changes to data values associated with an object without changing how it works.
Modify Data 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.
Allows you to change the way a protected object works. For example, this protects block creation and
Modify Design 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.
Note Passwords are case-sensitive – secret and Secret are not considered to be the same password.
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.
➢ To clear all passwords and protect the component: from the Device menu, select Restore Password
Protection.
Protection Properties
Property Description
Access Roles Allows you to set modifying data and design rights to previously defined user roles
Allows you to modify data values and forcing of variables
Note For the procedure to enter the CA Server Thumb Print property, refer to the section CA Server Thumb Print.
The Security Servers properties must be filled out for a system to operate in Secure mode. If these properties are filled out, the
system is secure. If these properties are blank, the system is open (does not support Secure mode).
The OPC Server only requires a certificate if the system is Secure and the 3rd party product ExperTune is used. The certificate
must be assigned to the LocalMachine location, My substore, and the certificate name must be GeCssOpcServer.
The Device Manager Gateway only requires a certificate if the system is Secure. The certificate must be assigned to the
LocalMachine location, My substore, and the certificate name must be GeCssDeviceManagerGateway.
Note Certificates must be created for each feature and added to the LocalMachine location, My substore, and the certificates
must be named as indicated in this section for each computer with these features enabled.
Note The OPC DA Server only requires a certificate if it is commanded to alter variables that are only accessible using
SDI messages, such as when used with the ExperTune product. This is rare, as most systems limit writes to variables that
are exposed on EGD pages, which does not require a certificate.
6. Create a certificate for the Device Manager Gateway for each workstation with this feature enabled only in Secure
systems.
The WorkstationST Status Monitor is configured to start when you log on to Windows, and then runs as a tray icon .
When a error occurs with the WorkstationST Service (or any configured feature), an error icon displays .
➢ To monitor and configure WorkstationST features: from the toolbar, click Launch Toolbox.
➢ To start or stop WorkstationST features: from the toolbar, click Start or Stop. Or right-click the feature, then
select Start or Stop from the shortcut menu. Start and stop requests are sent to the WorkstationST Service.
A service control manager is used to start the WorkstationST Service.
Note When the WorkstationST Service starts, it attempts to start all configured features, and to keep the features running. If
a feature is stopped from the Status Monitor, WorkstationST Service will not attempt to restart it. If the feature is started again
from the Status Monitor (or WorkstationST Service is restarted), the feature starts again.
Information displays for each configured feature. The WorkstationST Service runs a System Data Interface (SDI) server. The
Status Monitor uses an SDI client to obtain the information displayed. Information is not available when the WorkstationST
Service is not running.
Right-click
Alarm Server
and select
View Alarm
Server Status.
➢ To view certificates
1. Launch the WorkstationST Status Monitor from the tray icon.
2. Open the WorkstationST Certificate Manager.
From the WorkstationST Certificate Manager window, select the Feature Certificates
tab to display the data grid of configured certificates.
Note The Feature Certificate window is Read-only and cannot be used to import or export certificates.
Note If the Feature Certificates list is empty, the GeCssOpcServer and Device Manager Gateway feature’s certificates have
not been configured.
➢ To configure a WorkstationST component: open the Component Editor and select the General tab.
Time Card
allows you to
select the type
of time card
installed in the
WorkstationST
computer
Time Card
NTP Properties
Property Description
Overrides the system NTP settings, and uses local WorkstationST component settings
Configuration Manual Override
only
Selects the supported NTP configuration option to start on the WorkstationST
computer:
• Time Client
Configuration Option
• Primary Time Master
• Secondary Time Master
• Disabled
Disable NTP Broadcasts Disables or enables NTP broadcasts
Enable or disable NTP Server debug logging to file. This setting should only be enabled
NTP Server debug log enable during troubleshooting an NTP Server issue, then disabled as soon as debugging is
complete.
Specifies if WorkstationST will synchronize to a site time source and user determines
which option is used:
Site Time Reference Option • Broadcast
• Unicast
• None
➢ To schedule a task
From the
Recurrence
Pattern
options,
specify how
the task
should run.
If No Start
Time is
selected, the
Recurrence
Pattern
selections
are used.
If desired,
specify an
end time
(optional)
Scheduled Tasks
Right-click WorkstationST Service and select View WorkstationST Scheduled Tasks Information.
Attention
Select the checkbox to authorize the configured scheduled task to run.
The Status for the authorized Scheduled Task confirms the authorization with an displays as OK.
The following table describes the properties displayed in the Property Editor when a Network Adapter item is selected in the
Tree View.
Network Adapters Properties
Property Description
Adapter Settings
Enabled If set to False, disables the selected network adapter. Set to True to enable the network adapter.
Host Name Internet Protocol (IP) host name for the selected network adapter
IP Address Internet Protocol address for the selected network adapter
Wire Speed Speed of the network to which the selected adapter connects
Network Settings
Sets the network connected to the selected adapter (available networks are determined in the System
Network
Editor)
Controls the significant portions of the IP address
Subnet Mask 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.
Note A Remote Dry Low NO x (DLN) tuning contract provides for periodic tuning for ambient conditions, fuel conditions,
and normal component wear.
When the Features items is selected from the General tab and the AM Gateway feature is set to True, the AM Gateway Config
Path property displays in the Property Editor. This property provides the full path to the main configuration file that defines
items such as which turbine units are enabled for remote tuning.
➢ To enable OSM
1. From the WorkstationST General tab Tree View, select Features.
2. From the drop-down list, select True to enable the On Site Monitor. The OSM Interface tab displays.
Note Changes to the network switch connections will not be available for computers in a system running WorkstationST
V04.06 and earlier until they are upgraded.
With the release of ControlST V04.07, the ToolboxST application allows you to edit switch port connections using the
Network Switch Component Editor, rather than editing each component’s network adaptor. The component network adapter
information is imported into each switch’s configuration when the switch is first edited in V04.07. While it will no longer be
possible to view or edit the network adapter switch connections from each component editor, connections configured before
the upgrade will remain available for any WorkstationST computer that has not been upgraded. All upgraded WorkstationST
computers will use the new switch-centric information.
The data acquisition rate parameters allow the level of SNMP network traffic to be adjusted based on network bandwidth
rather than display update rate needs. The switch data request rate is separate from the device SNMP data because the amount
of SNMP data exchanged with the switches is very large compared to the data retrieved from the devices. Specifying a fast
device scan rate allows for fast detection of a device going online or offline, while fast switch data rates detect an unknown
device being added to the network or a device being moved to a different port. Knowing the device location is less important
than knowing whether the device is online. The network bandwidth necessary to retrieve the forwarding database from the
switches can be large in large systems, so separate parameters allows for tradeoffs to be made between bandwidth and the
speed of detection of abnormal conditions.
The system network drawing displays all physical networks, as well as network switches and devices, their physical locations,
and their interconnection. The host name and IP address of each device network connection on a per network basis, as well as
the switch and port where the physical connection is made is also provided. This information is entered for the network
switches and devices as they are added to a system.
When a new system is created, it automatically includes a UDH network. This is the default controller-level network to which
all controllers are connected. The Network Monitor only attempts to monitor devices configured as Ethernet, IP networks.
Additional networks are added as needed.
Network Status
Viewer displays
a hierarchy of
network, switch,
and devices
The Device View As Configured tab displays the devices in their configured locations, as well as deviations of the device
connections from their configured locations. This is used to find occurrences of a device connected to the wrong port that is
masking the location of an offline device, but configured to be connected to that port.
The Device View By Connection tab displays the actual location of each device’s switch and port.
Note Refer to the WorkstationST Alarm Server Instruction Guide (GEI-100626) for additional information on the
WorkstationST Alarm Server.
3. From the Alarm tab Tree View, select the Alarm Server item to display the Alarm Server configuration properties.
Note Each OPC AE server must be installed and configured before you add the server to the list and get the published
categories and condition names.
Refer to the WorkstationST OPC AE Server Instruction Guide (GEI-100624) for additional information.
➢ To add an external OPC AE Server: from the Tree View, right-click the External OPC AE Server item, then
click Add. A selection dialog box displays installed and operational servers.
WS1
WS1.Softing.OPCToolboxDemo_ServerAE
When an OPC AE server is added and selected in the Tree View from the Alarm tab, the data grid displays the translation of
each event category and condition name published by the OPC AE Server.
To translate incoming alarms and events, condition states must be mapped for the selected OPC AE Server. Once the
WorkstationST configuration has been downloaded, all Alarm Server clients can display alarms and events from all
configured OPC AE Servers.
➢ To display alarm and event types: click the OPC AE Server tab. The alarm and event types display in the
Summary View.
Note The GeCssOpcAeServer is a WorkstationST runtime feature, and must be installed and running for this configuration
to work.
From the Tree View , select WorkstationST Variables to display the variables.
Note Only variables from WorkstationST and External Device components that have been configured as an alarm or event
will be available for selection. Mark VI, EX2100 and LS2100 variables are not available to be scanned as they are already
part of the alarm system. Do not scan the controller component variables, since this causes redundant alarms to be generated.
Note The variable attributes cannot be modified from the Alarm Scanner variable list. The variable’s configuration displays,
but settings can only be changed from the component or feature where the variable is defined (typically the OPC DA Server
tab).
Click OK .
4. From the Tree View, right-click Fault Code Scanner and select Add Variable.
5. From the Select a Variable dialog box, locate and select the WorkstationST variables to be scanned.
6. From the WorkstationST Component Editor toolbar, click Build, then click Download.
7. Click Go Online and force the variable to test the generation of the alarms as displayed in the following figures.
Fault Condition 1
Fault Condition 2
Fault Condition 3
Note If the variable value falls outside the range of the enumerated values, the alarm is still generated and the alarm
description indicates the reason that the alarm text lookup failed as displayed in the following figure.
Note Each OPC UA server must be installed and configured before being added to the list to receive a list of alarms.
The server
displays in the
Tree View
Server Properties
Property Description
If set to True, creates a connection to the OPC UA server and consumes configured Alarms
Enable Connection To Server and Events.
If set to False, the configuration is preserved but ignored by the Alarm Server.
Host Name Host name of the computer where the OPC UA server is running
Server URL URL of the OPC UA server running on the specified host
Endpoint Configuration - Security Mode used for a secure connection. If Use Best Available Security is set to True, this
Security Mode setting will be ignored.
Endpoint Configuration - Security Policy used for a secure connection. If Use Best Available Security is True, this setting
Security Policy will be ignored.
Endpoint Configuration - Use If set to True, the client will attempt to connect to the server’s most secure endpoint, otherwise
Best Available Security the security settings defined in the Endpoint Configuration will be used.
User Token Information – User Name when a server implements a user name and password authentication. If blank, the
User Name user will be anonymous.
User Token Information –
Password when a server implements a user name and password authentication policy.
User Password
When the server connection is selected in the Tree View, two tabs display in the data grid: Variable and Active Severity
Mapping. Additional property values can be added to the alarms from the Variables tab.
Note If Printing Enabled is set to False (default setting), the Filters tab does not display.
When an alarm type is enabled for printing, the filtering configuration options
display in the Summary View .
Note Additionally, if the WorkstationST General tab setting Use Second Language is set to True, certain alarm fields (such
as Alarm State and Description) will be printed with the second language text.
Note Refer to the WorkstationST Alarm Viewer Instruction Guide (GEI-100620) for further details.
Note Global Project Parameters displays as a Tree View item only if the HMI Graphics without a Project property is set to
False.
Global parameters can be either system-level or project-level. Both types are user-defined. When the HMI Config tab is
selected, Global System Parameters displays as an item in the Tree View.
➢ To add a global system or project parameter: from the Tree View, right-click either Global System or Project
Parameters and select Add.
➢ To download HMI screen files from the master location to an HMI WorkstationST component
1. From the WorkstationST Component Editor HMI Config tab, select HMI Screens.
2. From the Summary View, select one or more HMI screen files and right-click to select Download selected HMI
Screens.
Note The most important status property is whether the HMI WorkstationST screen file is current with the master file.
The System Information Editor can display the status of HMI screen files, including the date and size of the master HMI
screen file and the WorkstationST component’s screen file.
The OPC DA Server receives Ethernet Global Data (EGD) from all EGD-referenced devices consumed by the WorkstationST
application. The OPC DA Server provides live, time-stamped 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 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 component that speaks SDI protocol, such as a Mark VIe controller, a Mark VI controller, or
a UC2000 Innovation Series controller. The OPC DA client data plug-in allows the server to obtain variables from an external
OPC DA Server.
Note Refer to the WorkstationST OPC DA Server Installation Guide (GEI-100621) for further details.
Note DCOM security issues may be encountered when OPC DA client-to-server communications are configured. Refer to
the WorkstationST OPC DA Server Installation Guide (GEI-100621).
The OPC DA client allows you to receive data from other OPC DA Servers. An OPC DA client connection contains one or
more groups that are collections of variables to be updated.
➢ To add an OPC DA group to the connection: from the Tree View, right-click the connection and select Add
Group.
Enter a group
name and
click OK.
➢ To connect all items in the Tree View: select the top level item and click GoOn/Offline or right-click and select
Connect.
If a connection is successful, live values display in the Data Grid.
A connection between the client and the OPC DA Server requires access and launch permissions by the client on the server
computer. Since OPC DA Servers often run as system users (not administrators), the server must be able to access the client
computer to return data values. The client computer must allow access by the system account to the client. Refer to the
WorkstationST OPC DA Server Installation Guide (GEI-100621) for information on DCOM settings.
When the OPC DA server is started, and whenever the specified .csv file is changed, the live values are read and set to the
variables specified in the .csv file. The variables can be any writable variables to which the WorkstationST has access. For
example, a client-driven variable can be defined and put onto an EGD Produced Page. This variable’s value is then updated
from the .csv file values. Any errors display in the Component InfoView Status tab.
If CSV Uses New Format is True, the .csv file format is a variable name with a value on each line, for example:
Var1, 3.7
Var2, true
Var3, 4.5
If CSV Uses New Format is False, the .csv file format is one line of variable names and a second line of data values, for
example:
Var1,Var2,Var3
3.7,true,4.5
The utility LiveVarsToCsv.exe, which is in the GeCssOpcServer installation folder, is used to read a snapshot of live values
and write them to an output .csv file. The command line utility’s syntax is as follows:
LiveVarsToCsv [options] <varCfgFileName |
var1,var2,var3...> <outputFileName>
If the alias is part of a bit-packed word, the GroupShortName and Offset columns must be populated. WorkstationST
variables cannot be used as part of a bit-packed word. Additional fields are ignored. The column order does not matter.
Note To use the import WindSCADA feature, the OPC DA Server tab must be enabled. Refer to the section Features.
Once the OPC dataset has been imported, perform the Save, Build, and Download commands. This updates the OPC DA
Server without requiring a restart. New OPC tags with the specified alias names are added to the namespace for access by
OPC clients.
Bit-packed Words Properties
Property Description
Name Full name with the device prefix
Description Existing Boolean variable in the OPC DA Server namespace
Type Offset for the Boolean variable in the packed word
The data is only configurable from the .csv file. If It becomes necessary to modify or add to the data, the file can be exported
back to the original .csv file from the WorkstationST configuration.
The WorkstationST Alarm server feature will consume alarms for all Mark VIe, Mark VI, and Mark V product line of
controllers that are configured to be referenced as Yes on the General Tab, Consumed Devices configuration. For example, the
following figure displays a configuration where alarms from the BOP controller will be consumed by the alarm server.
Alarm consumption can be configured to consume additional alarms from other remote alarm servers on the Alarm tab. The
primary and secondary alarm servers in the system are intended to be used to consume or aggregate alarms from other remote
alarm servers. Continuing with the example, the following figures illustrate the primary alarm server being additionally
configured to consume alarms from the controllers in Block1 and Block2. Both a primary and a secondary alarm server are
configured.
Note The period, which is user-configured as an exchange on a page, is the rate at which the exchange is sent.
WorkstationST EGD Produced Pages can be configured with primary or secondary redundancy. A primary redundancy sends
the Produced Page if the page’s data source is healthy. A secondary Produced Page is sent by another WorkstationST
component if the primary Produced Page is not heard for three periods. Typically a consumer of an EGD Produced Page
declares the page unhealthy if the page is not received after five periods. If the secondary redundancy again detects the
production of the primary page, data production is stopped. Like the primary, the secondary producer sends the page if the
data source is healthy.
➢ To show redundancy
1. From the EGD tab, select a Produced Page.
2. From the Property Editor, modify the Redundancy by selecting from the drop-down list.
Note DCOM security issues may be encountered when OPC DA client-to-server communications are configured. Refer to
the WorkstationST OPC DA Server Installation Guide (GEI-100621).
The WorkstationST application provides an OPC DA Server that can be configured with an OPC DA client, which consumes
data from other OPC DA Servers. The OPC DA test client allows browsing and live data callback connections (OPC DA 2.0)
to any OPC DA Server. Detailed information displays in the Log window.
➢ To use the Test OPC DA Client feature: from the View menu, select Test OPC DA Client from the drop-down
list. Refer to the section OPC DA Client.
An OPC connection contains one or more groups that are collections of variables to be updated.
➢ To add an OPC group to the connection: from the Tree View, right-click the created connection and select Add
Group.
Note For information on DCOM settings, Refer to the WorkstationST OPC DA Server Installation Guide (GEI-100621).
A connection between the client and the OPC DA Server requires access and launch permissions by the client on the server
computer. Since OPC DA Servers often run as System users (not Administrators), the server must be able to access the client
computer to return data values. The client computer must allow access by the System account to the client.
Properties
Property Description
Default source for Historical data if a source is not specified by the client.
Default Historian Type
Choices are Historian or Recorder, based on the features being enabled.
Enable High Performance EGD If set to True, enables multiple EGD receive threads to handle EGD activity.
Consumption More CPU is required by the OPC UA Server process, when this is enabled.
Note Refer to the ControlST Software Suite How-to Guides (GEH-6808), the section, How to Define Roles and Users in the
ToolboxST Application.
The Security Certificate/User Association item displays in the OPC UA Server tab Tree View and allows you to associate a
security certificate to a user account. Security certificates are obtained from the Windows store. Users and roles are assigned
in the ToolboxST configuration.
The user associates the certificate by name, distinguished name or thumbprint of the certificate. Using either name could
associate any certificate with that name or distinguished name to the SecurityST user. Selecting the thumbprint results in only
one certificate being associated with that SecurityST user. The association grants the privileges of the SecurityST user to the
applications using this certificate. Certificates can only be associated with one SecurityST user.
Failing to make a secure connection to the server results in data being exchanged over
non-secure or encrypted channels. Some OPC UA servers will not accept non-secure
connections.
Attention
Server Properties
Property Description
Host Name Host name of the computer where the OPC UA server is running
Server URL URL of the OPC UA server running on the specified host
Endpoint Configuration - Security Mode used for a secure connection. If Use Best Available Security is set to True, this
Security Mode setting will be ignored.
Endpoint Configuration - Security Policy used for a secure connection. If Use Best Available Security is set to True, this
Security Policy setting will be ignored.
Endpoint Configuration - If set to True, the client will attempt to connect to the server’s most secure endpoint, otherwise
Use Best Available Security the security settings defined in the Endpoint Configuration will be used.
User Token Information – User Name when a server implements a user name and password authentication. If blank, the
User Name user will be anonymous.
User Token Information –
Password when a server implements a user name and password authentication policy.
User Password
➢ To connect all items in the Tree View: select the top level item and click Go On/Offline or right-click and select
Connect.
If a connection is successful, live values display in the Data Grid.
Properties
Property Description
Name of this external Historian. This name displays in the OPC UA server's namespace, with all
Historian Name
variables from this Historian prefixed by this name.
Host Name Host name or IP address of the Historian WorkstationST running the OPC HDA server
OPC HDA Server Name of this external Historian's OPC HDA server
Enter a valid
Windows domain
name, username,
and password. The
domain is left blank
for computers using
Windows workgroups
➢ To use the Test OPC UA Client feature: from the View menu, select Test OPC UA Client.
Note These variables, previously named Client-driven Variables, are defined on the OPC DA Server tab.
WorkstationST-owned variables are written to by WorkstationST clients, such as Modbus and OPC DA and OPC UA clients.
➢ To add variables: from the Variables tab Tree View, select WorkstationST Variables.
Enter a variable
Variables can be edited both in the Data Grid and the Property Editors. The Data Grid is used to view or edit variable
definitions, and can be configured to display a subset of the variable properties. When a variable is selected in the Data Grid,
the Property Editor displays all variable properties.
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 heartbeat to maintain the client connection.
OPC AE Server, configured in a WorkstationST component, requires ToolboxST V 02.02 or later. The server is implemented
as a service with the name GeCssOpcAeServer.
16.21.1 Routing
The OPC AE Server can be connected locally or remotely from another computer.
Note Variable is used to describe an entity within the ToolboxST application. Source is the comparable OPC AE term; the
comparable OPC DA term is Item.
When an alarm or 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.
Example 2
In the following table, the component name is G1, the Boolean variable name is TooHot, and the variable properties are Alarm
= True, Event = False, and Hold = False.
The three alarm and 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.
➢ To display the alarm class definition: from the System Editor Edit menu, select System Information.
Alarm definitions display in the System Information Editor Data Grid.
OPC Properties
Note The Alarm Server must be enabled for the OPC AE server to be used.
4. Select 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.
5. Click the OPC AE Server tab, then from the Tree View, select Publish Settings. All alarm and event types are
published by default. These settings are for each consumed device.
The WorkstationST component can be built and downloaded. Use the WorkstationST 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 can connect.
The Tree View contains an entry for each component selected from the General tab. A system item is created for collecting
data from multiple components.
Properties
Property Description
Recorder Path Location of the recorder files being create
Provides validation of the trip logs by connecting to the controller and uploading the configuration of
Validate Trip Logs
the capture buffers
➢ To add a collection
1. From the Tree View, right-click a component and select Add Collection.
2. From the drop-down list, select the collection type, to display the Collection Name dialog box.
Enter a name
and click OK.
Note When the Alarms and Events or the diagnostic alarms are enabled for a collection, they are saved to the file when the
file is closed. This typically occurs at the end of the hour.
Properties
Property Description
Source from which data values are received
Network indicates data values obtained over Ethernet through the OPC DA server (example: EGD
data).
Source Direct indicates data values obtained through direct connection to the device with the device sending
the Data to the Recorder (example: data through SDI).
ByProxy allows the Recorder to collect data from devices referenced by proxy in this WorkstationST
(configured as consumed devices).
Configuration Method, either Automatic or Manual, used to configure this collection
Type Type of collection (Live Data)
Disk Usage Amount of disk space, in MB, that this collection is allowed
Storage Time Time, in days, that the files are maintained on disk
If set to True, records the alarms and events that occurred in the collection time frame. The Alarm
Alarms/Events
feature must be enabled in this WorkstationST component.
Description Provides a description of the collection
If set to True, records diagnostic alarms that occurred in the collection time frame. The Alarm feature
Diagnostic Alarms
must be enabled in this WorkstationST component.
Enable If set to True, enables the data collection
If set to True (default), controls whether the Recorder feature uses or ignores all predefined Recorder
Use Component
variables from the controller. If set to False, variables required for collection must be added manually
Configuration
(only when the Configuration property is set to Automatic).
Method Method, either Continuous, Triggered Level, or Triggered Edge, used for data collection
Name Collection name, is used as part of the file name
Scan Rate Rate, in ms, that the data is scanned for changes
Variable Count Number of variables in the collection
Properties
Property Description
Configuration Method, either Automatic or Manual, used to configure this collection
Type Type of collection (Trip Log)
Description Provides the description of the collection
Enable If set to True, enables the data collection
Name Name of the collection that is used as part of the filename
Upload Diagnostics If set to True, uploads the controller and I/O pack diagnostics and writes them to a .txt file.
Variable Count Number of variables in the collection (the last 30 trips are maintained on disk)
Properties
Property Description
Characters Per Line 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
Print CSV file If set to True, allows you to print the .csv file.
Printer Provides a drop-down list of printers
Configuration Method, either Automatic or Manual, used to configure this collection
Type Type of collection (Capture Buffer)
Disk Usage Maximum amount of disk space, in MB, that this collection is allowed
Storage Time Maximum length of time in days that the collection files are maintained on disk
If set to True, records the alarms and events that occurred in the collection time frame. The Alarm
Alarms/Events
feature must be enabled in this WorkstationST component.
Description Description of the collection
If set to True, records diagnostic alarms that occurred in the collection time frame. The Alarm feature
Diagnostic Alarms
must be enabled in this WorkstationST component.
Enable If set to True, enables the data collection
Name Name of the collection that is used as part of the filename
Scan Rate Rate, in ms, at which the data is scanned for changes
Variable Count Number of variables in the collection
Properties
Property Description
Characters Per Line Number of characters that can be printed on one line
Create CSV file If set to True, creates a .csv file as well as the .dca file.
Print CSV file If set to True, allows you to print the .csv file.
Printer Provides a drop-down list of printers
Configuration Method, either Automatic or Manual, used to configure this collection
Type Type of collection (EPA log)
Disk Usage Maximum amount of disk space, in MB, that this collection is allowed
Storage Time Maximum length of time in days that the collection files are maintained on disk
Description Description of the collection
Enable If set to True, enables the data collection
Name Name of the collection that is used as part of the filename
Scan Rate Rate, in ms, at which the data is scanned for changes
Variable Count Number of variables in the collection
Note Removing a component from the Tree View causes that component and all of its collections to be deleted. An
automatic collection can only be deleted by removal from the component’s configuration.
➢ To delete a collection: from the Tree View, right-click the collection to be deleted and select Delete.
➢ To add a variable
1. From the Tree View, right-click the desired collection and select Add Variable.
2. From the Select a Variable dialog box, select desired variables and click OK.
➢ To delete a variable: from the Data Grid, right-click the variable to be deleted and select Delete Selected Row(s).
Modbus is an application layer messaging protocol for client/server communications between components connected on
different types of busses or networks. The WorkstationST application supports both serial and Ethernet communication, and
can operate as both a Master and a Slave.
The WorkstationST Historian is the configuration interface between the ToolboxST application and WorkstationST
components and third-party Historian systems used for collecting long-term data from the system components.
GE Standard Messaging (GSM) provides a consistent external interface regardless of internal protocols and data
representations. Used by a Distributed Control System (DCS) to communicate with the turbine control system, the DCS can
receive alarms, events, and periodic data from turbine controllers as well as support writing periodic data or commands to the
turbine controllers.
Note Refer to the WorkstationST Application Mark V Feature System Guide (GEH-6759).
Each Mark V controller that communicates with an HMI has a unit-specific directory and subdirectory on the HMI hard drive.
Note Refer to the WorkstationST Device Manager Gateway Instruction Guide (GEI-100757).
The Device Manager Gateway enables communication between the Asset Management System (AMS) and fieldbus devices
in the Mark VIe controller. It provides access to FOUNDATION Fieldbus™, PROFIBUS ®, and HART® devices connected to
Mark VIe controllers over UDH.
Note Refer to the WorkstationST Control System Health Instruction Guide (GEI-100834) for information on parameters and
alarms.
The Control System Health feature allows you to display the health of various components on the UDH, the PDH, and IONet.
This includes the following:
Note When the first Produced Page is created, it automatically becomes the default page.
Tip � Any variable defined with $Default as the EGD page name is automatically placed on the currently selected default
page.
➢ To delete a page: from the Tree View, right-click the page to delete and select Delete.
➢ To compress a single page: from the Tree View, right-click the page to compress and select Compress.
➢ To compress all Produced Pages in a component: from the Tree View, right-click Produced Pages and
select Compress All.
Tip � If the variable to be added to the EGD page is already in use on the Software tab, you can add the variable without
using the EGD tab. To add a variable from the Software tab, select the desired variable(s) in the Summary View and set the
EGD Page property using either the Summary View or the Property Editor.
➢ To add a variable to a produced page: from the Tree View, right click a Produced Page and select Add
Variable to display the Select a Variable dialog box.
➢ To delete a variable from an EGD Page: from the Summary View, right-click the variable to delete and select
Delete Selected Row(s).
➢ To copy variable information from an EGD Page to the clipboard: from the Summary View, right-click a
variable and select Copy Selection. The data is copied in .csv format.
Note To edit exchange signatures and configuration time, set the Layout Mode property to Manual. The Layout Mode
property displays when a Produced Page is selected in the Tree View.
3. Review the warning about manual Exchange Signature editing and click OK.
4. Make any desired changes to the signatures and configuration time and click OK.
Note When EGD configurations are edited in remote devices, you must refresh the configuration to ensure that the latest
variable information is used. The configuration is automatically refreshed occurs when a WorkstationST component is
opened, and when a Build command is performed.
➢ To refresh the configuration of a referenced device: from the Tree View right-click the device to be refreshed,
and select Refresh.
The EGD protocol includes a Command Message Protocol (CMP) to obtain the status of a Class 2 or higher EGD device. The
WorkstationST component is a Class 3 EGD device. When any EGD item in the Tree View other than a referenced device is
selected, the EGD Statistics from [Device] tab displays the statistics from the open component. When a Referenced Devices
item is selected, the statistics are obtained from that device, and the name of the tab page changes accordingly.
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.
When the collection is started, the runtime begins 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.
The collection status displays in the status bar.
The Global Variables window is particularly useful when you want to modify a property for multiple variables. For example,
to move multiple variables onto an EGD page, select the rows for the desired variables and then change the EGD Page
property in the Property Editor. Refer to the section Data Grids.
Because only existing global variables can be changed, new variables cannot be added from the Global Variables window.
You cannot make any change that affects the name of the global variable (such as Name or Global Name Prefix).
• Alarm
• Event
• Workstation Consumed Device Information
• GE Rationalization
Note The Hold report is not supported for WorkstationST at this time.
Note The Alarms report will only display alarms that are configured in the Alarm Scanner or Fault Code Scanner.
The Event report lists digital signals defined as an Event, and provides an alarm History record when a signal transitions from
a 1 to 0. Event notifications provide the date and time stamp for when the Event occurred. This report can be used for
troubleshooting and informational reference.
➢ To create a Workstation Consumed Device Information report: from the View menu, select Reports, then
select Workstation Consumed Device Information.
There are several tabs available for the user to view consumption. These report views are detailed in the following sections:
➢ To create a System IP Address Information report: from the View menu, select Reports, then select System IP
Address Information to display the report.
Alarm Help files are generated when a build is performed for the device or when the
device is saved. However, Alarm help files are only generated when the Publish Alarm
Help property is set to True in the system Property Editor.
Attention
Note When a GE Rationalization report is generated from a WorkstationST component, it includes the following:
• WorkstationST owned variables with the Alarm property set to True. For Analog alarms, it will also include a line for each
unique combination of Variable Name and Alarm Condition Name.
• A line for each unique combination of Variable Name and Alarm Type if any External OPC AE Servers on the Alarm tab
are configured.
• A line for each Variable Name if any External OPC UA Servers on the Alarm tab are configured.
• Save report
• Retrieve (generate) report
• Export report
• Import report
• Print report
• Sort (modify) columns
• Filter
• Refresh
• Zoom
• Find text
• Help
Toolbar Icons
Icon Description
Zoom in
Zoom out
Get help
➢ To save, retrieve, or print a report: from the report File menu, select the desired command.
Column
names that
display in
blue cannot
be moved.
Or
2. Select a column header and use the drag-and-drop feature.
➢ To apply a report filter: from the Report menu, click Apply Filter to open the Edit Report Filter dialog box.
Available Available
columns comparison
(double-click and Boolean
to add to an operators
equation) (double-click
to add to an
equation)
Click to add
parentheses
Click OK to
accept the
filter equation
Enter filter that displays.
equation to
be used. Click Clear
to delete the
equation.
Click Cancel
to cancel the
equation but
keep the
current
settings.
<= Left expression must be less than or equal to the right expression
>= Left expression must be greater than or equal to the right expression
Expression to the left of the operator must match the wildcard expression
to the right of the operator
When using the LIKE operator, you can prefix or suffix a wildcard
LIKE character, either * or %, to the right-hand value. The wildcard character
can stand for any number of alphanumeric characters, including zero. The
wildcard character can only be present at the beginning or the end of the
right-hand value (for example, *value or value* or *value*).
AND Expressions to the left and right of the AND operator must both be True
OR Either the expression to the left or to the right of the operator must be True
Expression Description
NOT Expression to the right of the operator must be False
➢ To remove a report filter: from the Report menu, click Remove Filter. The filter is removed and all available rows
display.
➢ To save a filtered report: from the File menu, click Save Report.
➢ To search for text within a report: from the Report menu, click Find to display the Find dialog box.
If selected,
capitalization
in the test
string must
match the
text in the
report exactly
➢ To export a GE Rationalization report: from the GE Rationalization report File menu, select Save. Save it as a .csv
file to your computer, and modify as needed.
Tip: Change the Save as type to All Files (*.*) so you will
still be able to save the file as a .csv file.
Click Save .
5. Import the file into ToolboxST and verify that all the special characters display correctly.
If you use Microsoft Excel to modify the .csv file, make sure you save the file back to a
.csv file from a .xls file.
If the .csv file contains UTF-8 special characters, to avoid issues with displaying
special characters after import back into ToolboxST open the file with Notepad and
Attention save the file with Encoding set to UTF-8. Refer to the procedure To avoid issues with
second language special characters during import.
Select from the Available Attributes table using the arrows to add them to or remove them from the
Selected Attribute table. Click Export to export alarms for Rationalization.
GE Rationalization is an available selection for export (as displayed in this figure). However, it is only available for
backwards compatibility.
Note The GE Rationalization report contains a column for Parent Alarms and for Child Alarms. A large number of
parent/child relationships can cause these two columns in the .csv file to be incompatible with the Excel application. The
application allows a maximum limit of 32,767 characters in a cell.
When a GE Rationalization report is generated, it can be saved as a .csv file, modified, and then imported back into the
ToolboxST application. For the procedures to export and import GE Rationalization reports, refer to the section Export and
Import Reports.
➢ To open a stand-alone Watch Window: from the Start menu, select All Programs, GE ControlST, ToolboxST,
and Watch Window.
➢ To create a Watch Window: from the System Editor Tree View, right-click the system and select Insert New,
Tool and Watch Window.
Enter a Name,
and a Description
(optional), and
click OK.
Note If this Watch Window is being opened for the first time, the list is empty. Add or import a new Watch Window.
➢ To open an existing Watch Window: from the System Editor Tree View, right-click the system and select Insert
Existing and Watch Window.
➢ To open a Watch Window: from a Component Editor View menu, select Watch Windows.
If you selected
System
Component in the
previous page,
select the desired
component from
the drop-down list
and click Next.
The variables
will display here.
Click Finish .
Once a variable is added to a Watch Window, right-click the variable row header to perform the following actions:
Note When a system component providing signals to a Watch Window is replicated, the Watch Window is replicated as
well.
Forcing of protective functions is never permissible for an operating unit. All safety
Warning measures should be strictly enforced in conjunction with this procedure.
Note The Watch Window tool only exports grid columns necessary to retrieve variable information. For example,
DatasourceName from the exported file is used to retrieve the variable’s remaining properties from the system. User-defined
columns such as User Comment are also included.
➢ To save a Watch Window: from the <Watch Window name> File menu, select Save As to save the Watch Window
as a .watch file in a user-selected location,
or select Save to save the Watch Window as a .watch file in the Tools folder in the system.
16.33 CommandLineST
CommandLineST allows you to perform the following:
• Add and delete variables and their supporting structures to/from a WorkstationST component
• Build and download a WorkstationST component
• Get a .csv file of all variables a WorkstationST component can access
• Get a .csv file of all aliases defined in a WorkstationST component
Note The ToolboxST application must be installed. In addition, a system and a WorkstationST component must already
exist, the OPC DA Server feature must be enabled, and any network adapters must be added to the WorkstationST
configuration.
CommandLineST.exe[options]<CommandFileName|command,arg1key,arg1value,arg2key,arg2value...>
Example:
CommandLineST.exe /SuppressInfos c:\temp\AddTestWk1.csv
16.33.2 Options
The following options are supported:
/ErrorLog=filename Where filename is the name of the error log. If this option isn’t included, the default name is
CommandLineST.log. The error log is written to the directory from which the executable is
run unless a path was included in the filename.
/SuppressWarnings Keeps both warnings and infos from being printed in the error log.
• Select
• Add
• Delete
• Enable
• Report
• Compress
• Save
• Build
• Download
• Download WorkstationST Feature
• Reports
Select opens the .tcw file and selects a WorkstationST component. The appropriate parent item must be selected before an
Add or Delete command can be performed. For example, before adding a new group to an OPC DA client, the client needs to
be selected. The selection for any item type remains until another item of that type is selected. For example, an OPC DA
client is selected and several groups are added. Then several commands perform operations on the Modbus configuration. If
the following command tries to select a group, it searches for it under the OPC DA client that was selected many commands
prior because it had not been superseded by any another OPC DA client. Performing commands in this manner works, but the
command file is more difficult to read unless comments are included.
Add selects an item automatically. If an identical item already exists underneath the current parent, the existing item is
removed before adding the new item (the log file displays a warning). This implies two things. First, any children items are
removed. (For example, any groups under a client are removed, as well.) Second, all desired non-default attributes of the
signal must be included. A separate Modify command does not currently exist that would leave all current definitions in
place, and only replace specified attributes.
Delete searches for the identified item under the currently selected parent and deletes it. If it is not found, the log file
displays a warning.
Enable enables the identified WorkstationST feature. Component features must be enabled before they can be configured. It
is assumed that the OPC DA Server feature is already enabled in the identified WorkstationST component. However, Modbus
can be enabled through the command line interface.
Compress compresses the identified EGD page. If you delete a variable from an EGD Page, a Compress command of all
EGD Pages in that WorkstationST component must be performed before you can build it. Otherwise, a validation error
displays. The Compress command compresses all EGD Pages in the currently selected WorkstationST component. Performing
a Compress command corresponds to a major signature change for that exchange on EGD, and has system implications.
Performing an Add command of an existing variable, which removes the old variable definition and adds the new variable
definition, does not require you to perform a Compress command if you have not removed a variable from an EGD Page. For
example, if a variable was on page1, the new variable definition must be complete enough to include the key/value pair,
egdpage, page1.
Save saves changes made to the currently selected WorkstationST component. No changes are saved unless an explicit Save
or Build command is performed.
Build builds the currently selected WorkstationST component. A validation is run. If the validation does not have any errors
(warnings are permitted), it runs the build. (A successful build automatically saves the configuration.) If any validate errors or
warnings occur during the validation, they are written to the error log. Any errors that occur during the Build command are
also written to the log (other Build messages are not included). Informational messages are also not included.
Download downloads the currently selected WorkstationST component. If this WorkstationST component was successfully
built since its selection, this download occurs. Otherwise, the log file displays an error.
Download WorkstationST Feature adds WorkstationST variables with only the specified feature receiving the download.
“WorkstationName”_VariableReport.csv or “WorkstationName”_AliasReport.csv
Report Fields
DataType x —
Description x —
Units x —
FormatSpec x —
Computer and
Command Item Name Parent AddressType Alias
OPCServerName
System,
System,
WorkstationST,
Workstation,
Group, Client requires both
Select Client, Group1, N/A N/A Select
HWInterface, these arguments
HWInterface,
and Slave
Slave1
require a Name
Client, Group1, Group, Variable, For a Variable, it
Variable, Alias must be either For a
Add
HWInterface, HWInterface, OpcServer or SlavePoint:
Client requires both (Alias
Add2 Slave1, Slave, Group3. HoldingReg;
these arguments requires
SlavePoint1, SlavePoint, and For a HWInterface Input; InputReg;
this)
MasterMes- MasterMessage must be either Coil
sage1 require a Name Masters or Slaves
Client, Group1, Group,
Variable, Alias Variable4, For a
For a Variable, it Delete
HWInterface, HWInterface, SlavePoint:
Client requires both must be either (Alias
Delete Slave1, Slave, HoldingReg;
these arguments OpcServer or requires
SlavePoint1, SlavePoint and Input; InputReg;
Group3. this)
MasterMes- MasterMessage Coil
sage1 require a Name
Enable Modbus N/A N/A N/A Enable
Report4 5 Variable, Alias Name4 optional N/A N/A N/A Report
Com-
Compress6 N/A N/A N/A N/A N/A
press
Save6 N/A N/A N/A N/A N/A Save
Build6 N/A N/A N/A N/A N/A Build
Down-
Download6 N/A N/A N/A N/A N/A
load
Download
WorkstationST OPC DA Server N/A N/A N/A N/A N/A
Feature
2When an item is added, it is automatically selected. For example, if you add a Client, then add a Group, the
Group becomes a child under the Client that was just added.
3 If the Parent argument value is OpcServer, the variable is added or deleted from the WorkstationST Variables
list. If the Parent argument value is Group, the variable is added or deleted from the last selected or added
Group.
4 When Delete a Variable or make a report, you can use a * wildcard in the Name.
5 The report includes all variables and aliases that the currently selected WorkstationST component has access
to, or a subset of them if a search string is entered in the Name field (using Name, *, or leaving off the optional
name key/value pair reports all variables or aliases that the currently selected WorkstationST component has
access to).
# Add a Modbus Master and its signals; test signal definition in OPCserver space
add, item, hwinterface, parent, masters, name, 3.25.180.202
add, item, slave, name, 18
add, item, Variable, name, ClientSig18, parent, opcserver, description, Client Sig 18 description, externalaccess, readwrite
add, item, slavepoint, name, ClientSig18, addresstype, InputReg, datatype, lreal, address, 2, rawmin, 0, rawmax, 1000, eng
min, 0, engmax, 100
add, item, mastermessage, name, modbusmastermessage0, functioncode, funccode4, periodmultiplier, 6, numberofregisters, 4,
startaddress, 2
# Add a Modbus Slave and its signals; test signal definition in OPCClient group
add, item, hwinterface, parent, slaves, name, 3.25.180.201
add, item, slave, name, 28
add, item, client, computer, npiCAR, opcservername, GeCssOpcServer
add, item, group, name, grp1, deadband, 5, egdpagehealth, Page1, updaterate, 2000, uselocaltime, true
add, item, Variable, name, ClientSig28, parent, group, remotename, RemoteClientSig28, datatype, int, externalaccess,
readwrite
add, item, slavepoint, name, ClientSig28, addresstype, holdingreg, datatype, dint, address, 3
# Run a report
report, item, workstation, name, wk1, search, ClientSig*
# Open the system and add WorkstationST variables to the OPC DA Server
Note Connecting a variable to a Modbus register automatically defines the variable. The variable must have already been
added either to the OPC DA Server or to an OPC Client group as a separate action.
If the key/value pair for a given attribute is not included when adding a variable, the variable is assigned the default value.
If the key/value pair for a given attribute is not included when adding a group, the group is assigned the default value.
If the key/value pair for a given attribute is not included when adding a hardware interface, the HW Interface is assigned the
default value.
HW Interface Key/Value Pairs
Attribute Default Value
Required. The name is either the Com port if it is serial (COM1) or the IP Address if it is
Name
Ethernet.
Parent Required when adding. Value is either Masters or Slaves.
Ethernet. Possible Values:
InterfaceType
Ethernet, serial
IPAddress 0.0.0.0
BR19K2. Possible Values:
Port COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, COM10,
COM11, COM12, COM13, COM14, COM15, COM16.
ResponseDelay 0
StopBits 1
If the key/value pair for a given attribute is not included when adding a MasterMessage, the MasterMessage is assigned the
default value.
MasterMessage Key/Value Pairs
Attribute Default Value
Required. Format should be:
Possible Values:
FunctionCode
FuncCode1, FuncCode2, FuncCode3, FuncCode4, FuncCode5, FuncCode6,
FuncCode8, FuncCode15, FuncCode16
NumberOfRegisters 1
PeriodMultiplier 5
StartAddress 1
Status Colors
Color Condition
Green All features functioning normally — normal state
One or more of the following:
The following attributes are the maximum number that can display for a configured WorkstationST application (with all
features enabled).
• Compressing variables
• Changing frame rate
• Changing the background blockware period
• Adding the first I/O pack to a controller
• Changing redundancy type
• Changing the platform type, which changes the number of Ethernets
• Changing any NTP configuration on a controller
Note Certain conditions do not allow a download, for example, an incorrect platform type. Check the Component InfoView
for errors that would prohibit a download.
➢ To create a component: from the System Editor Tree View, right-click the system name and select Insert New,
Controller, and Power Conversion Control.
Note For more configuration information, refer to ControlST Software Suite How-to Guides (GEH-6808), the sections How
to Configure a Solar Power Converter and How to Configure a Wind Turbine ESS Doubly Fed Induction Generator Control.
Property Editor
allows you to edit
the item currently
selected in the
Tree View.
Component
InfoView displays
information about
the currently
selected item.
➢ To edit the component: select an item in the Tree View. The configuration information for that item displays in the
Summary View and Property Editor.
➢ To import an existing component: from the Tree View, right-click either a system or a group and select Insert
Existing and select Device. Select the Device .xml file for the component to be imported and click Open.
➢ To edit a property in the Property Editor: select an item by clicking its value 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.
Log tab displays messages related to user commands or system events issued in the ToolboxST configuration.
Tip � If there is a build problem, the error is listed on the Log tab. Double-click the error. The input focus goes to the
location in the component configuration where the error occurred.
Status tab displays operating state and equality information about the 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 at the beginning of some lines indicates that the variable is being written at that location.
Find Results tab displays the results of the Finder.
Info tab displays context-sensitive descriptions for the selected Tree View or Summary View item.
Each time a Build command is performed, the Log tab is updated with current errors, warnings, and general information.
Concurrently, with each Build command, a file is generated in the component folder that reflects the contents of the Log tab.
This file, called build.log, remains until the next Build command then is updated.
When the Build command is performed or the Build icon is clicked, dialog box displays with a message to view the change
log.
Note Right-click either an Error or a Warning and select Go To to find its location in the ToolboxST application.
Note Some Data Grids, especially those without an Append Row, may not support all features described in this chapter.
Data Grids are used to view or edit many of the configuration properties available in ToolboxST component editors. While
each Data Grid contains different columns and properties, several features are common to all Data Grids, including column
resizing, clipboard operations, and multi-row editing.
Quickly set a property to Left-click the row header for the first row to be edited. Then, while pressing the CTRL key,
the same value for multiple left-click added row headers. After selecting all desired rows, use the Property Editor to change
rows properties for all selected rows. (Some properties are omitted when a group of rows is selected,
and properties with conflicting values display no value in the Property Editor.)
To... Do this:
Resize a column Drag the vertical bar on the right of the column header to a new location.
Quickly remove a single column Right-click the column header and select Hide Column.
Move a column to a different location Drag the column header to a new location.
Sort by a column Click a column header. The column will sort in ascending order. To sort in
descending order, click the column header again.
Reset columns to the original configuration Right-click any column header and select Default Column Organization.
Add or remove columns Right-click any column header and select Organize Columns to display the
Organize Columns dialog box.
Select a
column name
and use the up
arrow to move
it to the left-
most side of
the Data Grid
in the destination grid and select Paste Row(s) to insert the row into its new
location.
Copy and paste multiple rows Left-click the row header for the first source row. Then, while pressing the CTRL key,
left-click added row headers. After selecting all desired rows, continue to hold down the
CTRL key and right-click any selected header. From the shortcut menu, select Copy
Selected/Current Rows to place the rows on the clipboard. Then, right-click the header
for the append row in the destination grid and select Paste Row(s) to insert the
rows into their new location.
Copy and paste a range of two or Click the top left cell of the desired range and drag to the bottom right cell. Right-click the
more cells selected region and select Copy Selected/Current Rows to place the cells on the
clipboard. Then, click the top left cell of the destination range and drag to select the
same number of columns and rows that were copied to the clipboard. Right-click inside
the destination region and select Paste Row(s).
Move rows between data grids Arrange windows on screen so both the source and destination grid are visible. (An
entry in a Tree View is acceptable as a destination). Left click the row header for the first
row. Then, while pressing CTRL, click any added row headers to be moved. Release the
CTRL key and drag a row header to the new data grid.
Add a variable to a block diagram, Arrange windows on screen so both the source grid and a destination block diagram,
Trender window or Watch Window Trender window or watch window are visible. Then, drag the row header for the variable
from a data grid 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.
➢ To open the Settings dialog box: from the Component Editor, select the Options menu, then select Settings to
display the Settings dialog box.
Properties
Property Description
Full Access (reserved for GE When set to True, displays additional settings to GE personnel (when True is selected, an
personnel) Enter Password dialog box displays)
Serial communication port Allows you to select the port to be used for serial communications
Show Short Names When set to True, displays the abbreviated names for DSP parameters and variables
Access Rights
Access Rights Description
Allows you to set Modify Data and Modify Design access rights to pre-defined user roles. Once roles
Access Roles
have been assigned to a protected object, only users with those roles can access the object.
Allows you to make changes to data values associated with an object without changing how it works.
Modify Data 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.
Allows you to change the way a protected object works. For example, this protects block creation and
Modify Design 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.
Note Passwords are case-sensitive – secret and Secret are not considered to be the same password.
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.
➢ To clear all passwords and protect the component: from the Device menu, select Restore Password
Protection.
Protection Properties
Property Description
Access Roles Allows you to set modifying data and design rights to previously defined user roles
Allows you to modify data values and forcing of variables
The GE ControlST DVD supports a variety of control equipment. These products include updated firmware for the equipment
and configuration tools that are available as component editors inside the ToolboxST application. When you install a new
version of the DVD, newer versions of some components may be installed as well. To use the new versions, you must
upgrade each component separately.
➢ To upgrade a component
1. Install the latest version of the ToolboxST application.
2. Start the ToolboxST application and open the system file. Double-click a component.
3. From the File menu, select Upgrade.
➢ To generate a Compare Devices report: from the System Editor Tree View, double-click the Power Conversion
component to display the Component Editor. A Compare Results: window displays differences between the two
selected components.
➢ To configure Power Conversion control: from the System Editor, open the Power Conversion component
and select the General tab.
General Tab Properties
Property Description
Communication
Determines the type of communications to use to connect to the device
Type
Control Interface
Determines the type of control interface to use for this device
Type
Diagnostic EGD Used to enable or disable the diagnostic EGD network for this device
Description Stores comments about the current controller
Name of the current controller; It is read-only in the Power Conversion Component Editor, and must be
Name
changed from the System Editor.
Product Subtype Specific type of selected Power Conversion component (Read-only)
Version of the selected Power Conversion component; The version number, which is set during
Product Version
configuration, changes with each upgrade. (Read-only)
Includes:
Modify Data allows you to modify data values and force variables.
Variables, which are similar to parameters, have a 20–character name and a five-character unit field. They are changed by the
controller as a result of the run pattern. For example, the variable Speed feedback (RPM), which represents the actual speed of
the device, gets updated on a continuous basis. Pre-defined trends are used to automatically populate the Trender with a list of
variables. The parameters, variables, and pre-defined trends are grouped under menus by function. The ToolboxST Finder can
be used to locate specific items by name.
Right-click a row in the data grid to display the menu for the selected parameter.
Note Since some parameters do not display on diagrams, Diagram is not always a menu option.
➢ To open the Select Variable dialog box: from the Tree View, select a pointer parameter and click the ellipsis
button.
Note A pointer parameter points to a variable. All pointer parameters display Var Address in the Units column of the
Summary View.
Preset enumerations defined for specific parameters display in the drop-down list.
As you enter the variable name in the Find Text field, the Variable List highlights that variable in an alphabetical list
containing all variables. Select the Anywhere in check box to display only the variables containing the letters as they are
entered.
Read-only variables display in the data grid. If the ToolboxST application is connected, the parameter values display in green
to indicate that they are being continuously updated.
➢ To use a pre-defined trend: from the Settings tab, double-click on a pre-defined trend to select variables.
For a multi-controller device, the variable browser displays a variable for each controller. The Trender is automatically started
with the variables you select from the Select a Variable dialog box.
The Diagrams tab graphically displays the parameters, sequencing, and variables of a Power Conversion component. Each
diagram contains drawings and text that represents a particular aspect of the Power Conversion component’s configuration or
state. Diagrams also allow you to edit parameters and display variable values, when the ToolboxST application is online with
a device.
➢ To view diagrams: from the Component Editor, click the Diagrams tab.
Zoom In and Zoom Out make the diagram larger and smaller, respectively.
Item Help opens an item-specific help window, if available.
Top Left, Top Right, Lower Left, and Lower Right scroll the diagram to those positions.
Save to File creates an Enhanced Windows Metafile (emf) of the drawing that includes live values.
Print sends the diagram that includes live values to a printer.
Right-click a hyperlink to open a shortcut menu.
Zoom In and Zoom Out make the diagram larger and smaller, respectively.
Zoom To scales the diagram to the scale selected from the drop-down list. Determines the type of control
interface to use for this device.
Actual Size resets the zoom to the normal scale factor (100%).
Fit Page causes the diagram to fill the entire Summary View.
Fit Width causes the entire width of the diagram to fit in the Summary View.
Note Use the drag-and-drop operation to move variables in the diagram into Trender or a Watch Window.
Or
Or
Tip � Any variable defined with $Default as the EGD page name is automatically placed on the currently selected Default
page.
Note The EMT provides a more detailed view of the configuration server contents.
Filter Toggle defaults to a filtered state showing only nodes that have the same name but a different producer ID as
the open component.
Delete deletes the selected node or nodes from the EGD configuration server. When documents are saved, they are
added to the configuration in the configuration server.
➢ To create a report
1. Open a Power Conversion Component Editor.
2. From the View menu, select Reports, and the desired report type.
• Open report
• Save report
• Retrieve (generate) report
• Export
• Import
• Print report
• Sort (modify) columns
• Filter
• Refresh
• Zoom
• Find text
• Help
Toolbar Icons
Icon Description
Zoom in
Zoom out
Get help
Some reports can be saved, modified, and imported back into the ToolboxST system.
➢ To save a report
➢ To sort a report column: click any column heading to apply a sort to that column. The first click sorts the column in
ascending order; a second click sorts the column in descending order.
Column
names that
display in
blue cannot
be moved.
Or
2. Select a column header and use the drag-and-drop feature.
If selected,
capitalization
in the test
string must
match the
text in the
report exactly
➢ To apply a report filter: from the Report menu, click Apply Filter to open the Edit Report Filter dialog box.
Available Available
columns comparison
(double-click and Boolean
to add to an operators
equation) (double-click
to add to an
equation)
Click to add
parentheses
Click OK to
accept the
filter equation
Enter filter that displays.
equation to
be used. Click Clear
to delete the
equation.
Click Cancel
to cancel the
equation but
keep the
current
settings.
When using the LIKE operator, you can prefix or suffix a wildcard character, either * or %, to the
LIKE right-hand value. The wildcard character can stand for any number of alphanumeric characters,
including zero. The wildcard character can only be present at the beginning or the end of the right-hand
value (for example, *value or value* or *value*)
AND Expressions to the left and right of the AND operator must both be True
OR Either the expression to the left or to the right of the operator must be True
NOT Expression to the right of the operator must be False
You can use as many groups of parentheses as necessary to define an expression.
String values must be enclosed in single quotes , for example 'string'
➢ To remove a report filter: from the Report menu, click Remove Filter. The filter is removed and all available rows
display.
➢ To save a filtered report: from the File menu, click Save Report.
➢ To open a stand-alone Watch Window: from the Start menu, select All Programs, GE ControlST, ToolboxST,
and Watch Window.
➢ To create a Watch Window: from the System Editor Tree View, right-click the system and select Insert New,
Tool and Watch Window.
Enter a Name,
and a Description
(optional), and
click OK.
Note If this Watch Window is being opened for the first time, the list is empty. Add or import a new Watch Window.
➢ To open an existing Watch Window: from the System Editor Tree View, right-click the system and select Insert
Existing and Watch Window.
➢ To open a Watch Window: from a Component Editor View menu, select Watch Windows.
If you selected
System
Component in the
previous page,
select the desired
component from
the drop-down list
and click Next.
The variables
will display here.
Click Finish .
Once a variable is added to a Watch Window, right-click the variable row header to perform the following actions:
Note When a system component providing signals to a Watch Window is replicated, the Watch Window is replicated as
well.
Forcing of protective functions is never permissible for an operating unit. All safety
Warning measures should be strictly enforced in conjunction with this procedure.
Note The Watch Window tool only exports grid columns necessary to retrieve variable information. For example,
DatasourceName from the exported file is used to retrieve the variable’s remaining properties from the system. User-defined
columns such as User Comment are also included.
➢ To save a Watch Window: from the <Watch Window name> File menu, select Save As to save the Watch Window
as a .watch file in a user-selected location,
or select Save to save the Watch Window as a .watch file in the Tools folder in the system.
18.20 LiveView
The LiveView feature allows you to display a graphical representation of live data from various sources in the system.
LiveViews can be added to a ToolboxST system, to a component, or opened as a standalone editor.
➢ To add an existing LiveView: from the System Editor, right-click the system and select Insert Existing and
LiveView.
➢ To edit a LiveView: from the System Editor, right-click a LiveView and select Edit System Component.
➢ To add a LiveView from a Component Editor: from the View menu, select LiveViews.
Reference point
Select a Bar
Color for the
High Alarm and
High Warning
range above the
reference point
Select a Bar
Color for the
Normal range
above the
reference point
Select a Bar
Color for the
Low Alarm and
Low Warning
range above the
reference point
If the Behavior
property is set to
Momentary and
the On Push
property is set to
False, the state of
the attached
variable is set to
True when the left-
mouse button is
clicked
Locked enables
or disables the
ability to move
and resize objects
Locked Property
Or
Variables display
here. Click
Finish
Note You can also attach a variable by entering the variable name in the Property View.
➢ To connect to a controller: from the System Editor, open a Power Conversion Component Editor. From the
Device menu, select Online.
If you are using Ethernet, a connection is automatically established. If you are using a serial connection to a multi-controller
Power Conversion component, a dialog box displays to allow you to select the desired controller.
Color Conditions
Green All controllers functioning normally.
- No faults or alarms
- Parameters are equal
- No overrides in the control
- Router configuration is equal (if applicable)
• Multiple Application Converter Control (MACC) controller runs the Power Conversion algorithms
• Router controller provides the Ethernet routing for multi-controller device
• Boot Loader starts the operating system for the controller and modules, much like the BIOS on a desktop computer.
Changes to the boot loader are very infrequent.
• Firmware provides the functionality of the controller and I/O modules. It can be updated over the lifetime of the
controller to incorporate new features and bug fixes.
• Parameters contain the configuration values of the controller as created in the ToolboxST application. Whenever a
change is made to the configuration, the parameters must be downloaded. At the end of the parameter download, the
device is reset.
Boot loader, firmware, and parameter downloads all require the target device to be
restarted. Before downloading new code to a controller, take necessary steps to secure
the controlled equipment to prevent equipment damage and/or personal injury.
Warning
• Boot Loader starts the operating system for the controller and modules, much like the BIOS on a desktop computer.
Changes to the boot loader are very infrequent.
• Base Load contains the operating system for the router controller. While changes to the base load are more likely than
changes to the boot loader, they still occur infrequently.
• Firmware provides the functionality of the router controller. It can be updated over the lifetime of the controller to
incorporate new features and bug fixes.
• Parameters contain the configuration values of the controller as created in ToolboxST. Whenever a change is made to
the configuration, the parameters must be downloaded. At the end of the parameter download, the device is reset.
Boot loader, firmware, and parameter downloads all require the target device to be
restarted. Before downloading new code to a controller, take necessary steps to secure
the controlled equipment to prevent equipment damage and/or personal injury.
Warning
• Boot Loader starts the operating system for the controller, much like the BIOS on a desktop computer. Changes to the
boot loader are very infrequent.
Note Not all devices have the boot loader. In this case, the boot loader is contained within the base load.
Base Load contains the operating system for the controller. While changes to the base load are more likely than changes
to the boot loader, they still occur infrequently.
• Firmware provides the functionality of the controller. It can be updated over the lifetime of the controller to incorporate
new features and bug fixes.
• Application Code contains the configuration of the controller as created in the ToolboxST application. Whenever a
change is made to the configuration, the application code must be downloaded. There are two types of application code
download: online and offline. An online download (very commonly performed) changes the configuration without
interrupting control and the new configuration takes effect between control frames. An offline download requires a
controller restart (performed less frequently).
• Parameters contain specific configuration for the power conversion portion of the controller.
Boot loader, base load, firmware, offline application code downloads, and parameter
downloads all require the target device to be restarted. Before downloading new
software to a controller, take the necessary steps to secure the control equipment to
prevent equipment damage and personal injury.
Warning
Note The type of software download needed is determined by which changes have been made to the controller
configuration.
Note Certain conditions do not allow a download, for example, an incorrect platform type. Check the Component InfoView
for errors that would prohibit a download.
1. From the Power Conversion Component Editor Device menu select Download and Download Wizard.
4. Select the values you wish to upload by selecting the check boxes next to the desired values or by clicking the Check All
button.
5. Click Upload to upload the selected values.
Click Reset
Faults to request
the fault list again.
Note A warning may display if the parameter values in the toolbox do not match the parameter values in the device.
The Tool Value can be changed and sent to the device. Right-click an override to display a menu that allows you to clear the
override or get help on the parameter.
➢ To create a component: from the System Editor Tree View, right-click the system and select Insert New,
Controller, and MarkStat Controller.
Property Editor
allows you to edit
the item currently
selected in the
Tree View
Component
InfoView displays
information about
the currently
selected item
➢ To edit the controller: select an item in the Tree View. The configuration information displays in the Summary
View and Property Editor.
➢ To edit a property in the Property Editor: select an item by clicking its value 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.
Log Tip � If there is a build problem, the error is listed on the Log tab. Double-click the error. The input focus goes
to the location in the component configuration where the error occurred.
Status Displays operating state and equality information about the component
Keeps a navigation history for each user session and allows you to return to different places in the
History 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.
Finds all uses of a variable within a Library Container
The write icon at the beginning of some lines indicates that the variable is being written at that location.
Where 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.
Each time a Build is performed, a message displays that allows you to view the Change log.
When Errors or Warnings are present, the Log tab notifies the user by displaying the current count, as well as a description.
Click each button to hide the corresponding item. For example, click Warning to hide the warnings listed in the Log tab;
Click Warnings again to display the warnings in the Log tab.
Note Some Data Grids, especially those without an Append Row, may not support all available features.
Quickly set a property to the Left-click the row header for the first row to be edited. Then, while pressing the CTRL key,
same value for multiple rows left-click added row headers. After selecting all desired rows, use the Property Editor to
change properties for all selected rows. (Some properties are omitted when a group of rows is
selected, and properties with conflicting values will display no value in the property editor.)
To... Do this:
Resize a column Drag the vertical bar on the right of the column header to a new location.
Quickly remove a single column Right-click the column header and select Hide Column.
Move a column to a different location Drag the column header to a new location.
Sort by a column Click a column header. The column sorts in ascending order. To sort in descending
order, click the column header again.
Reset columns to the original Right-click any column header and select Default Column Organization.
configuration
Add or remove columns Right-click any column header and select Organize Columns to display the
Organize Columns dialog box.
Select a
column name
and use the up
arrow to move
it to the left-
most side of
the Data Grid.
in the destination grid and select Paste Row(s) to insert the row into its new
location.
Copy and paste multiple rows Left-click the row header for the first source row. Then, while pressing the CTRL key,
left-click added row headers. After selecting all desired rows, continue to hold down the
CTRL key and right-click any selected header. From the shortcut menu, select Copy
Selected/Current Rows to place the rows on the clipboard. Then, right-click the header
for the append row in the destination grid and select Paste Row(s) to insert the rows into
their new location.
Copy and paste a range of two or Click the top left cell of the desired range and drag to the bottom right cell. Right-click the
more cells selected region and select Copy Selected/Current Rows to place the cells on the
clipboard. Then, click the top left cell of the destination range and drag to select the
same number of columns and rows that were copied to the clipboard. Right-click inside
the destination region and select Paste Row(s).
Move rows between data grids Arrange windows on screen so both the source and destination grid are visible. (An
entry in a Tree View is acceptable as a destination). Left click the row header for the first
row. Then, while pressing CTRL, click any added row headers to be moved. Release the
CTRL key and drag a row header to the new data grid.
Add a variable to a block diagram, Arrange windows on screen so both the source grid and a destination block diagram,
Trender window or Watch Window Trender window or Watch Window are visible. Then, drag the row header for the variable
from a data grid 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.
Show Boot Loader displays the boot loader in the Download Wizard when it does not have to be downloaded.
Access Rights
Access Rights Description
Allows you to set Modify Data and Modify Design access rights to pre-defined user roles. Once roles
Access Roles
have been assigned to a protected object, only users with those roles can access the object.
Allows you to make changes to data values associated with an object without changing how it works.
Modify Data 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.
Allows you to change the way a protected object works. For example, this protects block creation and
Modify Design 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.
Note Passwords are case-sensitive – secret and Secret are not considered to be the same password.
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.
➢ To clear all passwords and protect the component: from the Device menu, select Restore Password
Protection.
Protection Properties
Property Description
Access Roles Allows you to set modifying data and design rights to previously defined user roles
Allows you to modify data values and forcing of variables
➢ To upgrade a component
After a component has been upgraded, you cannot undo the upgrade. You also cannot
upgrade a component to its current or a previous version.
Attention
1. Install the latest version of the ToolboxST application.
2. Open the ToolboxST application, open the system .tcw file, and double-click a component.
3. From the File menu, select Upgrade, then select the component and appropriate I/O module(s) to upgrade.
To select all I/O modules for upgrade, click the top box in Item column box. From the New column drop -down list,
select the new firmware version .
To select one I/O module, select the box next to the I/ O module name.
Click the document icon next to the
To select multiple I/O modules, press and hold the Ctrl or Shift Key and version to display release notes for the
select each I/O module. selected version .
➢ To generate a Compare to Controller report: From the MarkStat Component Editor File menu, select
Compare To Controller.
Property Description
Stores information concerning alarm and event transitions and variable set commands on the
Command Event Log controller file system.
This data can be viewed by an external client through a web interface.
Specifies the maximum size (as a percentage) of both the command and event portions of the
% Command Size
Command and Event log.
Specifies the maximum size (as a percentage) of the event portions of the Command and Event
% Event Size
log.
Log to Disk Specifies whether Command events should be logged to the flash on the controller.
Specifies the number of days that the Command and Event log is kept if the allocated space is
Time
not exceeded.
Enable Controller Web When set to True, activates the Web server on the controller and displays the Web Page tab.
Pages When set to False, a major configuration difference occurs that forces an offline load.
Password Allows you to create or change a password used to access a web page from a browser.
Web File Path Directory used as the web page source when downloading product web pages to the controller.
Description Functional description of the current power conversion controller
Enable Alias Prefix If set to False, the device prefix name is not displayed in CIMPLICITY screens (default is False)
Time of the Build command performed after the most recent major change (read-only). (Major
Major Revision
changes require the controller to be restarted after download.)
Time of the Build command performed after the most recent minor change (read-only). Minor
Minor Revision
changes do not require a controller restart.
Name of the current controller. It is read-only in the Component Editor, and can only be changed
Name
from the System Editor.
NTP Configuration Determines how the Network Time Protocol client synchronizes the controller time.
Platform Type of hardware on which the MarkStat control code is started.
Product Sub Type Read-only property that reflects the type of selected MarkStat power conversion control
Read-only property that reflects the version of the MarkStat product associated with the selected
Product Version component. The version number is set when the configuration is first created, and is updated with
each product upgrade.
Profiler Enabled Determines if the controller load profiler is enabled.
Includes:
Access Roles: assigned to protect each access right for this controller
Modify Data: allows you to modify data values and force variables
Note The first time you attempt a password-protected function, the Enter Password dialog box displays. All protected
functions performed during the remainder of the ToolboxST session do not require re-entering the password.
➢ To open the Attribute Value Editor: from an attribute Data Grid, select a Value Cell and click the ellipsis button.
Name of the
attribute being
modified
If checked, the
attribute values are
restricted to an
enumeration (a
pre-defined set of
allowable values).
Variables, which are similar to parameters, have a 20–character name and a five-character unit field. They are changed by the
controller as a result of the run pattern. For example, the variable Speed feedback (RPM), which represents the actual speed of
the device, gets updated on a continuous basis. Pre-defined trends are used to automatically populate the Trender with a list of
variables. The parameters, variables, and pre-defined trends are grouped under menus by function. The ToolboxST Finder can
be used to locate specific items by name.
Right-click a row in the data grid to display the menu for the selected parameter.
Note Since some parameters do not display on diagrams, Diagram is not always a menu option.
➢ To open the Select Variable dialog box: from the Tree View, select a pointer parameter and click the ellipsis
button.
Note A pointer parameter points to a variable. All pointer parameters display Var Address in the Units column of the
Summary View.
Preset enumerations defined for specific parameters display in the drop-down list.
As you enter the variable name in the Find Text field, the Variable List highlights that variable in an alphabetical list
containing all variables. Select the Anywhere in check box to display only the variables containing the letters as they are
entered.
Read-only variables display in the data grid. If the ToolboxST application is connected, the parameter values display in green
to indicate that they are being continuously updated.
➢ To use a pre-defined trend: from the Settings tab, double-click on a pre-defined trend to select variables.
The Diagrams tab graphically displays the parameters, sequencing, and variables of a controller. Each diagram contains
drawings and text that represents a particular aspect of the controller’s configuration or state. Diagrams also allow you to edit
parameters and display variable values, when the ToolboxST application is online with a device.
➢ To view diagrams: from the Component Editor, click the Diagrams tab.
Zoom In and Zoom Out make the diagram larger and smaller, respectively.
Item Help opens an item-specific help window, if available.
Top Left, Top Right, Lower Left, and Lower Right scroll the diagram to those positions.
Save to File creates an Enhanced Windows Metafile (emf) of the drawing that includes live values.
Print sends the diagram that includes live values to a printer.
Right-click a hyperlink to open a shortcut menu.
Zoom In and Zoom Out make the diagram larger and smaller, respectively.
Zoom To scales the diagram to the scale selected from the drop-down list. Determines the type of control
interface to use for this device.
Actual Size resets the zoom to the normal scale factor (100%).
Fit Page causes the diagram to fill the entire Summary View.
Fit Width causes the entire width of the diagram to fit in the Summary View.
Note Use the drag-and-drop operation to move variables in the diagram into Trender or a Watch Window.
When you double-click a pointer parameter, an ellipsis button displays. Click it to open the Select Variable window.
If the ToolboxST application is online with the Power Conversion component, it optionally sends the new parameter value to
the component. You may also be prompted to enter initials or reset the component.
Note The first time you attempt a password-protected function, the Enter Password dialog box displays. All protected
functions performed during the remainder of the ToolboxST session do not require re-entering the password.
Enter the
Terminal Board
Position.
Select I/O
modules and
click OK.
➢ To create a group: from the Hardware tab Tree View, right-click the Distributed I/O item and select Add Group.
♦ From the Hardware tab Tree View, drag an I/O module to the desired group. When the cursor changes to a symbol,
release the mouse button to move the module.
Modifiable properties
include:
Note For information about the settings configured by I/O pack-specific tabs, refer to the I/O pack documentation.
When you select an I/O module from the Tree View, the Summary View provides tabs. The tabs that display vary according to
the I/O module. Tabs that display for all modules include:
• Summary
• Variables
• Diagnostics
• Status
The Summary View toolbar is as follows:
The I/O module in this example is a PAIC. The Summary tab displays a graphical overview of the selected I/O module.
Parameters tab allows you to configure all I/O module-specific parameters. After a parameter is changed, updated
pseudocode files must be downloaded to the I/O packs. This download operation does not require a restart of either the
controller or the I/O packs.
Variables tab displays available variables from the I/O module that have no physical endpoint. These variables exist only
internally in the I/O module, and can be connected to another variable for use in code.
Extra Circuits tab contains input/output variables found on the I/O module terminal boards, which can be associated with
the application software. For some I/O modules, these tabs are split into more I/O module-specific input/output tabs that
better define their function.
Note For some I/O modules, these tabs are split into more module-specific input/output tabs that better define their function.
Input and Output tabs contain input/output variables found on the I/O module terminal boards, which can be associated
with the application software.
The Status tab allows you to check the I/O pack version and network communication status.
Note A software item (programs, tasks, and such) must be defined in the Software tab before this feature can be performed.
➢ To attach a software variable to an I/O variable: from the Data Grid, select the Variables tab.
You can also attach a variable by entering the variable name in the Connected Variable column and pressing Enter. If the
variable name entered is a defined variable, it continues to display and the cursor moves to the next field. If the variable name
entered is undefined, click Yes when the Undefined Variable dialog box displays.
The Diagnostics tab allows you to check alarms and errors on I/O packs. Each I/O pack has a unique set of diagnostic
signals that can be monitored.
Inactive Alarm(s)
Active Alarm(s)
The Status tab allows you to check the I/O pack version and network communication status.
Late Cnt Number of times the exchange was later than expected
➢ To upgrade an I/O module: from the Tree View, right-click the I/O module and select Upgrade.
Note You must be online to view all diagnostics, with the exception of reports.
Normal
Inactive Alarm(s)
Active Alarm(s)
Link broken
Link error
Link warning
Link information
Note Place the mouse over the icon to display Tool Tips.
➢ To create an I/O diagnostic report: right-click an I/O pack or terminal board in the Summary tab and select
Create module Report.
I/O-related reports include:
• Alarm
• Revision
• Communication
• Hardware
Each report contains configuration or diagnostic details about the I/O hardware.
➢ To download parameters to a module: from the Hardware tab Tree View, right-click the module to be
downloaded and select Download Parameters.
As module parameters directly affect the operation of the controller and associated
I/O modules, always check the Compare Parameters dialog box before downloading
new parameter values to a component to reduce the risk of improper operation or
damage to the unit.
Caution
➢ To open the Compare Parameters dialog box: from the Hardware tab Tree View, right-click a module to
compare and select Compare Parameters.
Note The first time you attempt a password-protected function, the Enter Password dialog box displays. All protected
functions performed during the remainder of the ToolboxST session do not require re-entering the password.
If adding a
program group,
enter a name
and click OK
Note The Add Existing Program command reads an .xml file from another system or controller into the current controller.
When the controller is online, double-click the live value of the variable _Enable for the task, select True to enable the task
or False to disable the task, then click Send & Close.
Disabled
Task Disabled
• Function block libraries describe software that is part of the controller firmware
• User block libraries combine these function blocks into user blocks
The Instance All command creates a new copy of all linked user blocks from the referenced user block libraries. In addition to
updating the user blocks, this command causes the instance scripts and text substitutions to run.
➢ To instance a user block: from the Tree View, right-click a user block and select Instance.
Note Variables can also be added in the Summary View by directly editing the append row of the variable grid.
User block attributes only display on linked or unlinked user blocks whose user block definition contained attributes in the
library. They can be modified so that when their parent user block is instanced, the modified attributes are used in the scripts
and text substitutions that access them.
Note Linked tasks and user blocks can also be unlinked permanently.
➢ To unlink a program: from the Tree View, right-click a program item and select Unlink Permanently.
The linked icon next to the item in the Tree View changes and the program is unlinked from the library.
Property Editors
Programs
Remove Unused Variables Removes the unused variables for all linked user blocks in this device when the user block is
instanced
Program
Description Allows you to describe the program
Library Type Is the name of the library definition that this program came from.
Name Allows you to name the program
Protection Properties control the Access Roles, Modify Data, Modify Design, and View Design
permissions for this program.
Execution Order Sets the order of program execution
Task
Block Type Is the name of the user block definition in the library from which this task started
Description Is the description of this task
Name Is the name of this task
Instance Script Runs when the task is instanced.
Detached Summary File Is the path to the summary diagram for the user block definition.
Help File Allows you to locate the Help file by clicking the ellipsis button.
Help Text Is locally defined Help that supersedes the global Help.
Protection Properties control the Access Roles, Modify Data, Modify Design, and View Design
permissions for this task.
Revision History Allows you to edit the revision history by opening the Edit Text dialog box.
Version Is the user-defined version of a task
Execution Order Sets the order of program execution
Frame Multiplier Is the number of frames at which the task runs
Schedule Offset Is the offset from beginning of frame at which the task runs
User Block
Block Type Is the name of the library block that the selected block is an instance of
Description Is text describing the instance of the block.
Instance Name Is a unique identifier that allows the block to be referenced from other locations in the
ToolboxST application
Instance Script Causes the script to run when the block is instanced
Height Is the height of the selected block in the diagram.
Left Is the location of the left of the selected block
Selected Pin Is the pin currently highlighted in the diagram
Show Description When set to True, displays the description of the selected block
Top Is the location of the top of the selected block
Width Is the width of the selected block
Block Data Type Is the data type for variant pins in the selected block instance
Detached Summary File Is the backsheet for the selected block
Enable When set to True, enables variables for the selected block
Version Is the version number for the source of the selected block instance
Execution Order Determines when this block is started
➢ To add a variable to a program: from the Software tab, expand the Programs item.
Right-click the
Variables item and
select Add Variable
or Add Undefined
Variables
User block and task variables are local by default, and display under the associated user block item in the Tree View.
Variables can be edited both in the Data Grid and the Property Editors. The Data Grid is used to view or edit variable
definitions, and can be configured to display a subset of the variable properties.
Right-click to select
Organize Columns .
➢ To change the frame multiplier or the schedule offset: from the Summary View, click the Frame Multiplier
or Schedule Offset cell and select from the drop-down list.
Note Since the schedule offset depends on the frame multiplier, it is possible to select a frame multiplier for which the
current schedule offset is invalid. This causes a validation error when you build the application.
Note There is a 12 MB size limit on the memory that can be allocated to the DDRs. If this memory allocation is exceeded,
an error is reported during validation.
➢ To add a variable
1. From the DDR tab Tree View, right-click the DDR and select Add Variable.
2. Select the desired variables and click OK.
DDRs can be updated separately from the application code download.
➢ To update a DDR: from the Device menu, select Download and Update Dynamic Data Recorder.
Note DDRs cannot be downloaded if there is a major difference in the device. In this case, the application code must be
downloaded.
➢ To import or export a DDR: from the DDR tab Tree View, right-click the desired DDR and select Import
Configuration or Export Configuration.
Note If the .xml file being imported contains the formatting flags %n, it is replaced by the component Design Memo (DM)
number. This is a GE Power Systems project number and can be edited by selecting the General tab and Requisition Info.
4. Create a User Block in the program, and add two FuncGen blocks from the Data Collection section. Set up the pins
on the two blocks as follows. FuncGen1 is set up as a Sine wave generator and FuncGen2 is set up as a Triangle wave
generator.
5. Add the two variables SineOut and TriangleOut to the DDR. Set the Frame Period Multiplier to 3, which means a
sample is collected every 120 ms. The base frame period is typically 40 ms. Set the PreTrigger samples to 20 and the
PostTrigger samples to 100, so that the entire capture takes 14.4 seconds.
9. From the View menu, select Trenders to add a new trend and upload the capture buffer.
10. From the Trender window, select Edit and Add Traces to display the Trender - Add Trace Wizard.
11. From the wizard, select Capture Buffer/Dynamic Data Recorder to select the DDR to upload.
Note When the first Produced Page is created, it automatically becomes the default page.
Tip � Any variable defined with $Default as the EGD page name is automatically placed on the currently selected default
page.
➢ To delete a page: from the Tree View, right-click the page to delete and select Delete.
➢ To compress a single page: from the Tree View, right-click the page to compress and select Compress.
➢ To compress all Produced Pages in a component: from the Tree View, right-click Produced Pages and
select Compress All.
Tip � If the variable to be added to the EGD page is already in use on the Software tab, you can add the variable without
using the EGD tab. To add a variable from the Software tab, select the desired variable(s) in the Summary View and set the
EGD Page property using either the Summary View or the Property Editor.
➢ To add a variable to a produced page: from the Tree View, right click a Produced Page and select Add
Variable to display the Select a Variable dialog box.
➢ To delete a variable from an EGD Page: from the Summary View, right-click the variable to delete and select
Delete Selected Row(s).
➢ To copy variable information from an EGD Page to the clipboard: from the Summary View, right-click a
variable and select Copy Selection. The data is copied in .csv format.
Note To edit exchange signatures and configuration time, set the Layout Mode property to Manual. The Layout Mode
property displays when a Produced Page is selected in the Tree View.
3. Review the warning about manual Exchange Signature editing and click OK.
4. Make any desired changes to the signatures and configuration time and click OK.
Filter Toggle defaults to a filtered state. It displays items that have the same name but have a different Producer ID as
the open component.
Delete deletes the selected item(s). If the item(s) were saved as part of the configuration, they can be added again.
The EGD configuration server uses the producer ID to store all the documents for an EGD node.
When a component is saved, the EGD configuration is automatically published to the EGD configuration server. To avoid
unintentional overwriting of data, do not configure more than one .tcw file for a server.
• Compare command compares the component's EGD-produced data configuration with the EGD configuration server’s
content.
• UnConsumed Data command generates a report showing variables produced by this component that are not listed in
any other device’s consumed data file.
Note You can select devices to search against. The individual pages, with just variables, perform the same Compare.
The Referenced Devices item on the EGD tab also has a Compare command that compares the consumed variable
information for the open component against the EGD configuration server’s content.
Note When EGD configurations are edited in remote devices, you must refresh the configuration to ensure that the latest
variable information is used. The configuration is automatically refreshed when a component is opened, and when a Build is
performed in the component.
➢ To refresh the configuration of a referenced device: from the Tree View, right-click the device to be refreshed
and select Refresh.
➢ To create undefined variables for a single or multiple referenced device(s): from the Tree View, right-click
either the device or Referenced Devices and select Create Undefined Variables.
Report Description
Device Version and Hardware
Displays all device firmware versions and hardware information
Information
Provides four reports:
Change History
Parameter Compare to Device
Value
Override List
Reports include:
Global lists all global variables in the controller, including name, description, data type,
Alarm/Hold/Event status, initial value, and units.
Configuration lists all signals and their configuration.
Attributes lists all of the attributes defined for the device and their current settings.
Block Pin lists all block pins in the controller software. For every variable, the report lists
name, description, execution number, connected variable name, data type, the program
where the block pin resides, pin description, user (macro) block name, block name, program
running number, and pin usage description.
Alarm displays all variables marked as Alarms. For every variable, the report lists name,
Variable
description, alarm class, display screen, and status if it alarms on a zero condition. Variables
are marked as Alarms in the Property Editor.
Hold displays all variables marked as Holds. For each variable, it lists variable name,
description, and Hold ID. Variables are marked as Holds in the Property Editor.
Event displays all variables marked as Events. For each variable, it lists the variable name,
description, and Event ID. Variables are marked as Events in the Property Editor.
NovRAM displays all variables marked as non-volatile. It lists each variable name and
description. Variables are marked as Nonvolatile in the Property Editor.
Alias lists global variables with name, alias, and description.
Second Language lists global variables with name, and primary and secondary languages.
Reports include:
I/O Variable provides a list of all I/O variables.
Configuration provides a list of all variables in the current configuration.
Reports include:
Alarm provides a list of all alarms in the current configuration.
Revision provides a list of modules, I/O packs, revision types, I/O pack revisions, and
ToolboxST revisions.
I/O Diagnostics
Communication provides communication information, including module, I/O pack, product
ID, frame rate, and connection.
Hardware provides a list of hardware information for an I/O pack, including firmware ID,
serial number, and bar code.
Coding Practices Generates a list of unwritten variables, multiple writes, and unused I/O variables
GE Rationalization Lists GE Rationalization parameters and the current alarms generated for the variables
Unwritten Variables are used in blockware logic, but have no assigned values.
Multiple Writes are variables used in multiple locations, such as blockware logic, EGD, or I/O point configuration.
Multiple Output Assigned Variables displays all variables attached to more than one output.
Unused I/O are connected I/O values that are not used anywhere.
Spares are unconnected and unused I/O values.
Example of a
coding practices
report
➢ To create a report: from the View menu, select Reports and the desired report.
Toolbar Icons
Icon Description
Zoom in
Zoom out
Get help
➢ To save a report: from the report File menu, select the desired command.
➢ To sort a report column: click any column heading to apply a sort to that column. The first click sorts the column in
ascending order; a second click sorts the column in descending order.
Note Column
names that
display in
blue cannot
be moved.
Or
2. Select a column header and use the drag-and-drop feature.
If selected,
capitalization
in the test
string must
match the
text in the
report exactly
➢ To apply a report filter: from the Report menu, click Apply Filter to open the Edit Report Filter dialog box.
When using the LIKE operator, you can prefix or suffix a wildcard character, either * or %, to the
LIKE right-hand value. The wildcard character can stand for any number of alphanumeric characters,
including zero. The wildcard character can only be present at the beginning or the end of the right-hand
value (for example, *value or value* or *value*)
AND Expressions to the left and right of the AND operator must both be True
OR Either the expression to the left or to the right of the operator must be True
NOT Expression to the right of the operator must be False
You can use as many groups of parentheses as necessary to define an expression.
String values must be enclosed in single quotes , for example 'string'
➢ To remove a report filter: from the Report menu, click Remove Filter. The filter is removed and all available rows
display.
➢ To save a filtered report: from the File menu, click Save Report.
• Variable Alias
• Second Language
• GE Rationalization
The Variable Alias report and the Second Language report can be imported from either a .cvs or an .xml file. Generator data
can also be imported.
Note A large number of parent/child relationships can cause the number of characters in an Excel .csv file cell to exceed the
maximum allowed (32,767). If your data exceeds this number of characters, do not attempt to use the Excel application.
Alarm Help files are generated when a build is performed for the device or when the
device is saved. However, Alarm help files are only generated when the Publish Alarm
Help property is set to True in the system Property Editor.
Attention
Tip: Change the Save as type to All Files (*.*) so you will
still be able to save the file as a .csv file.
Click Save .
5. Import the file into ToolboxST and verify that all the special characters display correctly.
If you use Microsoft Excel to modify the .csv file, make sure you save the file back to a
.csv file from a .xls file.
If the .csv file contains UTF-8 special characters, to avoid issues with displaying
special characters after import back into ToolboxST open the file with Notepad and
Attention save the file with Encoding set to UTF-8. Refer to the procedure To avoid issues with
second language special characters during import
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
Warning measures should be strictly enforced in conjunction with this procedure.
➢ To display Forced Variables: from the Component Editor View menu, select Forced Variables.
➢ To force a value or change a previously forced value: from the Forced Variables dialog box, double-click a
value to display the Send Value dialog box.
➢ To remove a single forced value: right-click a forced variable and select Remove Selected Forces.
➢ To remove all forced values: right-click anywhere inside the Forced Variables dialog box and select Remove All
Forces.
➢ To print a report
1. From the File menu, select Print.
2. In the Print dialog box, verify that the settings are correct and click OK.
➢ To display the Global Variables window: from the Component Editor View menu, select Global Variables.
The Global Variables window allows you to modify a property for multiple variables. For example, to move multiple
variables onto an EGD page, select the rows for the desired variables and change the EGD Page property in the Property
Editor.
Because only existing global variables can be changed, new variables cannot be added from the Global Variables window.
You cannot make any change that affects the name of the global variable (like Name or Global Name Prefix). Most properties
of variables that are instanced from a library can only be modified by using the Overridable Properties feature.
Select from the Available Attributes table using the arrows to add them to or remove them from the
Selected Attribute table. Click Export to export alarms for Rationalization.
GE Rationalization is an available selection for export (as displayed in this figure). However, it is only available for
backwards compatibility.
Note The GE Rationalization report contains a column for Parent Alarms and for Child Alarms. A large number of
parent/child relationships can cause these two columns in the .csv file to be incompatible with the Excel application. The
application allows a maximum limit of 32,767 characters in a cell.
When a GE Rationalization report is generated, it can be saved as a .csv file, modified, and then imported back into the
ToolboxST application. For the procedures to export and import GE Rationalization reports, refer to the section Import
Reports.
➢ To import alarms to the library: from the System Editor Tree View, open the Library Container Editor.
The report displays all variables found in the library; variables missing from the library display in red. It is possible to
re-export the report to include all rows not found during the original import.
➢ To import the report back into the controller: from the controller File menu, select Import and GE
Rationalization Report.
The report automatically overrides properties in the controller configuration to change the linked library code.
➢ To open a stand-alone Watch Window: from the Start menu, select All Programs, GE ControlST, ToolboxST,
and Watch Window.
➢ To create a Watch Window: from the System Editor Tree View, right-click the system and select Insert New,
Tool and Watch Window.
Enter a Name,
and a Description
(optional), and
click OK.
Note If this Watch Window is being opened for the first time, the list is empty. Add or import a new Watch Window.
➢ To open an existing Watch Window: from the System Editor Tree View, right-click the system and select Insert
Existing and Watch Window.
➢ To open a Watch Window: from a Component Editor View menu, select Watch Windows.
If you selected
System
Component in the
previous page,
select the desired
component from
the drop-down list
and click Next.
The variables
will display here.
Click Finish .
Once a variable is added to a Watch Window, right-click the variable row header to perform the following actions:
Note When a system component providing signals to a Watch Window is replicated, the Watch Window is replicated as
well.
Forcing of protective functions is never permissible for an operating unit. All safety
Warning measures should be strictly enforced in conjunction with this procedure.
Note The Watch Window tool only exports grid columns necessary to retrieve variable information. For example,
DatasourceName from the exported file is used to retrieve the variable’s remaining properties from the system. User-defined
columns such as User Comment are also included.
➢ To save a Watch Window: from the <Watch Window name> File menu, select Save As to save the Watch Window
as a .watch file in a user-selected location,
or select Save to save the Watch Window as a .watch file in the Tools folder in the system.
20.27 LiveView
The LiveView feature allows you to display a graphical representation of live data from various sources in the system.
LiveViews can be added to a ToolboxST system, to a component, or opened as a standalone editor.
➢ To add an existing LiveView: from the System Editor, right-click the system and select Insert Existing and
LiveView.
➢ To edit a LiveView: from the System Editor, right-click a LiveView and select Edit System Component.
➢ To add a LiveView from a Component Editor: from the View menu, select LiveViews.
Reference point
Select a Bar
Color for the
High Alarm and
High Warning
range above the
reference point
Select a Bar
Color for the
Normal range
above the
reference point
Select a Bar
Color for the
Low Alarm and
Low Warning
range above the
reference point
If the Behavior
property is set to
Momentary and
the On Push
property is set to
False, the state of
the attached
variable is set to
True when the left-
mouse button is
clicked
Locked enables
or disables the
ability to move
and resize objects
Locked Property
Or
Variables display
here. Click
Finish
Note You can also attach a variable by entering the variable name in the Property View.
➢ To display constants
Note During an Import, the Override Entry Limit property is set to True for all control constants linked to a library where
either the Entry High Limits or Entry Low Limits properties have different values from the values in the .csv file.
The Controller Value is the value in Select the check box next
the running controller. to the correct value to
The ToolboxST Initial Value is the synchronize the constant,
value in the ToolboxST configuration. then click OK
1. From the Control Constants File menu, select Reconcile Differences. The Constants Reconciliation dialog
box displays all constants with different live and initial values.
2. Select the check box next to the correct value to synchronize the constant and click OK.
The constants are synchronized as follows.
• For constants when the ToolboxST initial value was checked, that value is either sent to the controller (where the OK
button is clicked), or a pcode record is created, causing the next online download to change both the initial and live
values.
• For constants when the live value was checked, the ToolboxST initial value is set equal to the controller live value. This
causes a minor revision configuration change to Not Equal. A Build and Download to the controller is required to
complete the reconcile function.
➢ To display I/O values: from the Hardware tab, select an I/O module.
Icons Conditions
All controllers functioning normally
Controller trip
• Compressing variables
• Changing frame rate
• Changing the background blockware period
• Adding the first I/O pack to a controller
• Changing redundancy type
• Changing the platform type, which changes the number of Ethernets
• Changing any NTP configuration on a controller
State Description
Powerup Power up controller
Master initialization Controller is loading its own configuration
Designated controller
Determine which controller is designated in a redundant controller configuration
determination
Perform initialization of non-designated controllers with NVRAM, command variables, and
Data initialization
constants
Inputs enabled Wait in this state for all required I/O packs to start transmitting inputs
Input voting Check voting inputs prior to execution of application code
Exchange initialization Populate redundant controllers with dc state variables prior to voting
Exchange state variables so that a controller joining a running system will not have a step in its
Exchanging
initial calculations
Sequencing Turn on the application code and execute each task at least once before driving outputs
Controlling Turn on outputs
Loading Online load is in progress
Load complete Online load has finished. Wait for re-synchronization of redundant controllers
Fail Failure has occurred.
Click Go to Secure.
Note When the process is in the Authenticated state, the controller is retrieving a certificate revocation list from the CA
Server to verify that the requestor has a valid certificate.
A controller cannot communicate on a network until these setup tasks are complete.
Attention
Prerequisites
• The control system hardware and network cabling have been connected properly
• All system equipment has been successfully powered on.
• The controller has been added to the system with the correct redundancy
i. Enter the device password, then select a COM port and the appropriate controller Channel.
i. Insert a non-encrypted removable USB 2.0 (only) flash device with a 4 GB minimum capacity into the HMI
computer USB port.
ii. Initialize the controller.
iii. Remove the flash device from the USB port of the HMI computer, then click Finish.
iv. Remove power from the controller.
v. Insert the flash device into the controller. For a UCSB, press and hold in the Backup/Restore button. For a
UCSC, press and hold the PHY PRES button.
Note Refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose Applications System
Manual (GEH-6721_Vol_II), the sections UCSC Restore and UCSB Backup and Restore for these procedures.
vi. Apply power to the controller while continuing to press the button until the On LED on the front of the
controller becomes solid green, then release the button. The On LED turns off when the process is complete.
vii. Remove power from the controller, remove the USB flash device, then re-apply power to the controller.
viii. If using redundant controllers, repeat this procedure for the S and T controllers (if TMR) or S (if dual). Be sure
to select the correct Channel.
The user must change the factory default controller password for a device. The
maximum number of characters for the new password is limited to characters. The
new password cannot be the factory default password. If you do not know the factory
default password, contact the nearest GE Sales or Service Office, or an authorized GE
Sales Representative.
Attention For additional details, refer to Mark VIe and Mark VIeS Control Systems Volume II:
General-purpose Applications, GEH-6721_Vol_II, the chapter Controller Diagnostic
Alarms, alarm 547.
Note For a device configured with redundant controllers, the password applies to all controllers in that device.
Note This password is required for configuring the network address during controller setup.
When the password for the replacement controller is successfully synchronized to the other controller passwords in the set, a
message displays in the Log window.
• Boot Loader starts the operating system for the controller and I/O modules, much like the BIOS on a desktop computer.
Changes to the boot loader are very infrequent.
Note Not all devices have the boot loader. In this case, the boot loader is contained within the base load.
Base Load contains the operating system for the controller I/O modules. While changes to the base load are more likely
than changes to the boot loader, they still occur infrequently.
• Firmware provides the functionality of the controller I/O modules. It can be updated over the lifetime of the controller
to incorporate new features and bug fixes.
• Application Code contains the configuration of the controller as created in the ToolboxST application. Whenever a
change is made to the configuration, the application code must be downloaded. There are two types of application code
download: online and offline. An online download (very commonly performed) changes the configuration without
interrupting control and the new configuration takes effect between control frames. An offline download requires a
controller restart (performed less frequently).
• Parameters contain configuration settings necessary for the power converter portion of the controller and I/O modules.
Boot loader, base load, firmware, offline application code downloads, and parameter
downloads all require the target device to be restarted. Before downloading new
software to a controller, take the necessary steps to secure the control equipment to
prevent equipment damage and personal injury.
Warning
Note The type of software download needed is determined by which changes have been made to the controller
configuration.
The Download Wizard is used to download software to a MarkStat component over an Ethernet connection. The Download
Wizard can automatically examine the system configuration to locate out-of-date software, or you can manually select
individual items to download.
Note Certain conditions do not allow a download, such as an incorrect platform type. Check the Component InfoView for
errors that may prohibit a download.
1. From the Component Editor Device menu, select Download and Download Wizard.
2. If you have changed configuration settings since the last Build operation, a message box indicates that the software is out
of date. Click Yes to build the current configuration.
3. When the welcome wizard displays, click Next .
If a change occurred that requires a restart of the controller, a wizard page displays with a Restart Controller after
Download check box selected.
4. When the download has completed, click Finish.
The APP_STATE block can prohibit a download and restart of the controller.
Attention
If the DOWNLOAD_OK input of the APP_STATE block is set to True, all downloads are allowed. If this value is set to
False, all downloads (except Update DDR and Device Backup) are prohibited. This condition also applies to an attempted
download of an I/O pack from the Hardware tab of the Component Editor. If the download is prohibited, a warning displays in
the Component InfoView, and the Download Mark VIe Controller wizard displays the prohibited download. For additional
information on the APP_State block, refer to the Mark VIe Controller Standard Block Library Instruction Guide
(GEI-100682).
➢ To update the DDR: from the Device menu, select Update Dynamic Data Recorder and follow the instructions
on the ToolboxST windows.
➢ To view and set the controller time: from the Device menu, select View/Set Time... and follow the instructions
on the ToolboxST windows.
Note The UCSC, as shipped from the factory, does not include the software on the controller to support communication
from the PHY PRES button to the EFA. The user needs to download to the controller at least once (using ToolboxST) to
enable this.
From the
View menu,
select
Reconcile
Parameter
Differences
Note From the Component InfoView, you can also double-click the Status tab to display the Reconcile Parameter
Differences dialog box.
➢ To open Controller Diagnostics view: from the View menu, select Diagnostics and Controller Diagnostics.
The I/O diagnostics view displays diagnostic messages for a component hardware I/O module. Retrieve these messages to
diagnose problems with hardware I/O.
➢ To open I/O Diagnostics view: from the View menu, select Diagnostics and I/O Diagnostics.
Note Before modifying Totalizer values in a redundant controller, connect to the R controller and make sure all other
redundant controllers are healthy and communicating. (Refer to the section Connect to a Controller.)
Note Totalizer passwords are specific to the connected redundant controller (R, S, or T) and cannot be used on other
controllers.
Note Totalizer passwords are usually valid for 24 hours from time of creation.
2. From the Modify Totalizer Value dialog box, enter the new value and click OK.
➢ To create a component: from the System Editor Tree View, right-click the system and select Insert New,
Controller, Excitation Control, and EX2100e.
Property Editor
allows you to edit
the item currently
selected in the
Tree View.
Component
InfoView displays
information about
the currently
selected item.
➢ To edit the component: select an item in the Tree View. The configuration information for that item displays in the
Summary View and Property Editor.
1. From the Tree View, right-click either a system or a group and select Insert Existing and select Device.
2. Select the Device.xml file for the component to be imported and click Open.
Note If no button displays, edit the value directly in the corresponding text box on the right side of the Property Editor.
➢ To edit a property in the Property Editor: select an item by clicking its value 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.
Tip � If there is a build problem, the error is listed on the Log tab. Double-click the error. The input focus goes to the
location in the component configuration where the error occurred.
Status tab displays operating state and equality information about the 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 at the beginning of some lines indicates that the variable is being written at that location.
Find Results tab displays the results of the Finder.
Info tab displays context-sensitive descriptions for the selected Tree View or Summary View item.
When the Build command is performed or the Build icon is clicked, a dialog box displays a message to view the change log.
Note Right-click either an Error or a Warning and select Go To to find its location in the ToolboxST application.
Note Some Data Grids, especially those without an Append Row, may not support all available features.
Quickly set a property to the Left-click the row header for the first row to be edited. Then, while pressing the CTRL key,
same value for multiple rows left-click added row headers. After selecting all desired rows, use the Property Editor to
change properties for all selected rows. (Some properties are omitted when a group of rows is
selected, and properties with conflicting values will display no value in the property editor.)
To... Do this:
Resize a column Drag the vertical bar on the right of the column header to a new location.
Quickly remove a single column Right-click the column header and select Hide Column.
Move a column to a different location Drag the column header to a new location.
Sort by a column Click a column header. The column sorts in ascending order. To sort in descending
order, click the column header again.
Reset columns to the original Right-click any column header and select Default Column Organization.
configuration
Add or remove columns Right-click any column header and select Organize Columns to display the
Organize Columns dialog box.
Select a
column name
and use the up
arrow to move
it to the left-
most side of
the Data Grid.
in the destination grid and select Paste Row(s) to insert the row into its new
location.
Copy and paste multiple rows Left-click the row header for the first source row. Then, while pressing the CTRL key,
left-click added row headers. After selecting all desired rows, continue to hold down the
CTRL key and right-click any selected header. From the shortcut menu, select Copy
Selected/Current Rows to place the rows on the clipboard. Then, right-click the header
for the append row in the destination grid and select Paste Row(s) to insert the rows into
their new location.
Copy and paste a range of two or Click the top left cell of the desired range and drag to the bottom right cell. Right-click the
more cells selected region and select Copy Selected/Current Rows to place the cells on the
clipboard. Then, click the top left cell of the destination range and drag to select the
same number of columns and rows that were copied to the clipboard. Right-click inside
the destination region and select Paste Row(s).
Move rows between data grids Arrange windows on screen so both the source and destination grid are visible. (An
entry in a Tree View is acceptable as a destination). Left click the row header for the first
row. Then, while pressing CTRL, click any added row headers to be moved. Release the
CTRL key and drag a row header to the new data grid.
Add a variable to a block diagram, Arrange windows on screen so both the source grid and a destination block diagram,
Trender window or Watch Window Trender window or Watch Window are visible. Then, drag the row header for the variable
from a data grid 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.
➢ To open the Settings dialog box: from the Component Editor, select Options and Settings.
Access Rights
Access Rights Description
Allows you to set Modify Data and Modify Design access rights to pre-defined user roles. Once roles
Access Roles
have been assigned to a protected object, only users with those roles can access the object.
Allows you to make changes to data values associated with an object without changing how it works.
Modify Data 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.
Allows you to change the way a protected object works. For example, this protects block creation and
Modify Design 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.
Note Passwords are case-sensitive – secret and Secret are not considered to be the same password.
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.
➢ To clear all passwords and protect the component: from the Device menu, select Restore Password
Protection.
Protection Properties
Property Description
Access Roles Allows you to set modifying data and design rights to previously defined user roles
Allows you to modify data values and forcing of variables
2. Select the .csv file to import. Make sure the .csv file has the following format:
Name,Value
ExciterType,Brushless
ControlType,Simplex
BridgeType,77mm
2. Select the .xml file to import. Make sure the .xml file has the following format:
2. Select the .csv file to import. Make sure the .csv file has the following format:
Name, Value,Source
AFFL, 1599, EXSetting
EstFireComp, .6766, EXSetting
➢ To upgrade a component
1. Install the latest version of the ToolboxST application.
2. Start the ToolboxST application, open the system .tcw file, and double-click the component to display the Component
Editor.
3. From the File menu, select Upgrade.
4. When the Welcome wizard displays, click Next.
5. Select the version to upgrade to and click Finish.
A Compare Results: window displays differences between the two selected devices.
➢ To configure EX2100e excitation control: open the Component Editor and select the General tab.
Property Description
Stores information concerning alarm and event transitions and variable set commands on the
Command Event Log controller file system.
This data can be viewed for analysis by an external client through a web interface.
Specifies the maximum size (as a percentage) of both the command and event portions of the
% Command Size
Command and Event log
% Event Size Specifies the maximum size (as a percentage) of the event portions of the Command and Event log
Log to Disk Specifies whether Command events should be logged to the CompactFlash® on the controller
Specifies the number of days that the Command and Event log is kept if the allocated space is not
Time
exceeded
When set to True, enables access to controller web pages if they are provided by the controller or
another product. The controller can provide a set of default pages as part of the firmware download.
Controller Web Pages
Product web pages can also be downloaded to the controller. For example, the 1.5 MW Wind
Turbine uses product-specific web pages that are downloaded separately.
Enable Controller Web
When set to True, activates the Web server on the controller. It also displays the Web Page Tab.
Pages
Password Allows you to create or change a password
Description Free-form field to store comments about the current controller
Enable Alias Prefix If set to False, the device prefix name is not displayed in CIMPLICITY screens (default is False)
Time of the Build command performed after the most recent major change. (Major changes require
Major Revision
the controller to be restarted after download.)
Time of the Build command performed after the most recent minor change (minor changes do not
Minor Revision
require a controller restart)
Name of the current controller. It is read-only in the EX2100e Component Editor, and can only be
Name
changed from the System Editor.
NTP Configuration Determines how the Network Time Protocol (NTP) client synchronizes the controller time
Configuration Manual If set to True, displays the Mode property that allows you to override the system NTP settings and
Override use the local device settings only
Includes:
• Disabled: controller does not perform any time synchronization
Mode
• Broadcast: client listens for NTP broadcasts on the network
• Unicast: client uses the specified servers to obtain the time
NTP Configuration
Optional IP address of a secondary (backup) server used when unicast mode is selected
Secondary Server
Platform Type of hardware on which the EX2100e control code is started
Product SubType Specific type of selected EX2100e (either Regulator or Static Start).
Read-only version number of the EX2100e product associated with the selected component. The
Product Version version number is set when the configuration is first created and is updated with each product
upgrade.
22.15.1 Attributes
Attributes are device-level values that affect how the configuration is generated. When the Attributes item is selected in the
Tree View, those controller attributes can be edited in the Summary View data grid.
Attribute Columns
Column Description
Name Unique identifier for the attribute
Description Stores added comments about the attribute
Value Displays and modifies the current attribute value
Pre-defined trends are used to automatically populate the Trender with a list of variables. The parameters, variables and
pre-defined trends are grouped under menus by function.
Use the Finder to locate specific items by name.
The Data Grid contains columns that list the properties of the selected parameter. If the ToolboxST application is connected,
the component values display in blue to indicate that the live values are read from the component one time. The columns and
column layout on the data grid can be customized.
When the Tool Value is changed, you are asked if the value should be sent to the device configuration.
Right-click a row in the data grid to display the menu for the selected parameter.
Note Since some parameters do not display on diagrams, Diagram is not always a menu option.
Note A pointer parameter points to a variable. All pointer parameters display Var Address in the Units column of the
Summary View.
➢ To open the Select Variable dialog box: from the Tree View, select a pointer parameter and click the ellipsis
button.
Preset enumerations defined for specific parameters display in the drop-down list.
As you enter the variable name in the Find Text text box, the Variable List highlights that variable in an alphabetical list
containing all variables. Selecting the Anywhere in check box displays only the variables containing the letters as they are
entered.
The Diagrams tab graphically displays the parameters, sequencing, and variables of an EX2100e component. Each diagram
contains drawings and text that represents a particular aspect of the component’s configuration or state. Diagrams also allow
you to edit parameters and display variable values, when the ToolboxST application is online with a device.
➢ To view diagrams: from the Component Editor, click the Diagrams tab.
Zoom In and Zoom Out make the diagram larger and smaller, respectively.
Item Help opens an item-specific help window, if available.
Top Left, Top Right, Lower Left, and Lower Right scroll the diagram to those positions.
Save to File creates an Enhanced Windows Metafile (.emf) of the drawing that includes live values.
Print sends the diagram that includes live values to a printer.
Right-click a hyperlink to open a shortcut menu.
Zoom In and Zoom Out make the diagram larger and smaller, respectively
Zoom To scales the diagram to the scale selected from the drop-down list. Determines the type of control
interface to use for this device.
Actual Size resets the zoom to the normal scale factor (100%).
Fit Page causes the diagram to fill the entire Summary View.
Fit Width causes the entire width of the diagram to fit in the Summary View.
Modify displays the attributes of variables and parameters. Variable attributes cannot be modified. When a parameter is
right-clicked, a text box displays to modify the value.
Item Help opens the help file for the selected variable.
Diagram allows you to navigate to other diagrams that contain the variable.
Goto Settings switches to the Settings tab and navigates to the selected variable.
Send to Device sends the parameter value to the device, if the ToolboxST application is online.
Note Use the drag-and-drop operation to move variables in the diagram into Trender and Watch Windows.
When you double-click a pointer parameter, an ellipsis button displays. Click it to open the Select Variable dialog box.
If the ToolboxST application is online with the Power Conversion component, it optionally sends the new parameter value to
the component. You may also be prompted to enter initials or reset the component.
Note The first time you attempt a password-protected function, the Enter Password dialog box displays. All protected
functions performed during the remainder of the ToolboxST session do not require re-entering the password.
If adding a
program group,
enter a name
and click OK
Note The Add Existing Program command reads an .xml file from another system or controller into the current controller.
When the controller is online, double-click the live value of the variable _Enable for the task, select True to enable the task
or False to disable the task, then click Send & Close.
Disabled
Task Disabled
• Function block libraries describe software that is part of the controller firmware
• User block libraries combine these function blocks into user blocks
Attention
➢ To instance a user block: from the Tree View, right-click a user block and select Instance.
Note Variables can also be added in the Summary View by directly editing the append row of the variable grid.
➢ To unlink a program: from the Tree View, right-click a program item and select Unlink Permanently.
The linked icon next to the item in the Tree View changes and the program is unlinked from the library.
Property Editors
Programs
Removes the unused variables for all linked user blocks in this device when the user block is
Remove Unused Variables
instanced
Program
Library Type Name of the library definition that this program came from
Properties control the Access Roles, Modify Data, Modify Design, and View Design
Protection
permissions for this program
Task
Block Type Name of the user block definition in the library from which this task started
Help File Allows you to locate the Help file by clicking the ellipsis button
Help Text Locally defined Help that supersedes the global Help
Properties control the Access Roles, Modify Data, Modify Design, and View Design
Protection
permissions for this task
Revision History Allows you to edit the revision history by opening the Edit Text dialog box
Schedule Offset Offset from beginning of frame at which the task runs
User Block
Block Type Name of the library block of which the selected block is an instance
Unique identifier that allows the block to be referenced from other locations in the ToolboxST
Instance Name
application
Instance Script Causes the script to run when the block is instanced
Programs
Left Location of the left of the selected block
Selected Pin Pin currently highlighted in the diagram
Show Description When set to True, displays the description of the selected block
Enable When set to True, enables variables for the selected block
Version Version number for the source of the selected block instance
Execution Order Determines when this block is started
➢ To add a variable to a program: from the Software tab, expand the Programs item.
Includes:
• Not Logged
Controller
• Average Linear: this is a linear average {1/N * sum(values)}
Connected
• Average Linear Angle: This is an average for angle based variables; it takes into account 0 degrees
equals/360 degrees wrap-around for angles.
• Average Cosine Phi: This average calculation is for power factor (cos phi). It effectively calculates the
average of the arccosine of each of the data values during the interval. The value returned is the
cosine of this average.
• Data Snapshot: This selection is for end-of-interval values. The last value captured during the
specified interval is returned.
Enables the automatic collection by the Historian when:
Historian
Boolean and set to Logged on Change
Deadband
Analog and set to 0 or higher
Historian
Deadband Defines the deadband value as either engineering units or percent of range.
Definition
Enables the automatic collection by the Recorder when:
Recorder
Boolean and set to Logged Continuous or Logged on Change
Deadband
Analog and set to 0 or higher
Recorder
Deadband Defines the deadband value as either engineering units or percent of range
Definition
Usage
Allows a variable to be designated as a configuration setting. The default value is False, which prohibits
Control Constant
changing live values. Setting the property to True allows you to change live values.
If set to True, downloads extended information to the controller that is used by the web server, as well as
Download Info other processes. For example, to view alarms on the touchscreen, the Download Info parameter must be
set to True for each alarmed variable.
EGD Page Used to assign the variable to an Ethernet Global Data Page
Used primarily for EGD:
ReadOnly variable can be read on EGD
External Access
ReadWrite variable can be written to through EGD
NoAccess variable cannot be changed with the ToolboxST application
The variable's global name prefix type (None, Full, Block, Program, Task).
This controls the form of the global name that displays on the EGD page. For example, the name for
variable IGVA in user block VG_Health in task Task1 in program CORE would display (depending on the
Global Name Prefix) as:
Global Name
None: IGVA
Prefix
Full: CORE.VG_Health.IGVA
Block: VG_Health.IGVA
Program: Task1.IGVAv
Task: Task1.IGVAv
From the
Summary View,
select a variable.
From the Type
drop-down list,
select the
variable type.
Or:
from the
Property
Editor,
select Type
and the
variable type
• Replace the blockware detail view for the task or userblock with a graphic
• Add the graphic as a Sheet tab in the block’s detail view
• Display the graphic in a separate window using the eyeglasses button on the toolbar
• Diagnostic Alarms
• Process Alarms
• Hold List Alarms
• Events
• Sequence of Events (SOE)
Beginning with ControlST V04.04, controller configurations must not exceed the
following limits. If these limits are exceeded, reduce the number of configured Process
Alarms, Events, and Holds.
Note For further details, refer to the Mark VIe and Mark VIeS Controls Systems Guide (GEH-6721_Vol_I), the chapter
Alarm Overview, and the Workstation Alarm Server Instruction Guide (GEI-100626).
Parent and child Alarms can be exported using Alarm Rationalization. Parent alarms only can be imported from a .csv file.
Corresponding child Alarms are automatically placed in the configuration.
➢ To change the frame multiplier or the schedule offset: from the Summary View, click the Frame Multiplier
or Schedule Offset cell and select from the drop-down list.
Note Since the schedule offset depends on the frame multiplier, it is possible to select a frame multiplier for which the
current schedule offset is invalid. This causes a validation error when you build the application.
Note There is a 12 MB size limit on the memory that can be allocated to the DDRs. If this memory allocation is exceeded,
an error is reported during validation.
➢ To add a variable
1. From the DDR tab Tree View, right-click the DDR and select Add Variable.
2. Select the desired variables and click OK.
DDRs can be updated separately from the application code download.
➢ To update a DDR: from the Device menu, select Download and Update Dynamic Data Recorder.
Note DDRs cannot be downloaded if there is a major difference in the device. In this case, the application code must be
downloaded.
➢ To import or export a DDR: from the DDR tab Tree View, right-click the desired DDR and select Import
Configuration or Export Configuration.
Note If the .xml file being imported contains the formatting flags %n, it is replaced by the component Design Memo (DM)
number. This is a GE Power Systems project number and can be edited by selecting the General tab and Requisition Info.
4. Create a User Block in the program, and add two FuncGen blocks from the Data Collection section. Set up the pins
on the two blocks as follows. FuncGen1 is set up as a Sine wave generator and FuncGen2 is set up as a Triangle wave
generator.
5. Add the two variables SineOut and TriangleOut to the DDR. Set the Frame Period Multiplier to 3, which means a
sample is collected every 120 ms. The base frame period is typically 40 ms. Set the PreTrigger samples to 20 and the
PostTrigger samples to 100, so that the entire capture takes 14.4 seconds.
9. From the View menu, select Trenders to add a new trend and upload the capture buffer.
10. From the Trender window, select Edit and Add Traces to display the Trender - Add Trace Wizard.
11. From the wizard, select Capture Buffer/Dynamic Data Recorder to select the DDR to upload.
Note When the first Produced Page is created, it automatically becomes the default page.
Tip � Any variable defined with $Default as the EGD page name is automatically placed on the currently selected default
page.
➢ To delete a page: from the Tree View, right-click the page to delete and select Delete.
➢ To compress a single page: from the Tree View, right-click the page to compress and select Compress.
➢ To compress all Produced Pages in a component: from the Tree View, right-click Produced Pages and
select Compress All.
Tip � If the variable to be added to the EGD page is already in use on the Software tab, you can add the variable without
using the EGD tab. To add a variable from the Software tab, select the desired variable(s) in the Summary View and set the
EGD Page property using either the Summary View or the Property Editor.
➢ To add a variable to a produced page: from the Tree View, right click a Produced Page and select Add
Variable to display the Select a Variable dialog box.
➢ To delete a variable from an EGD Page: from the Summary View, right-click the variable to delete and select
Delete Selected Row(s).
➢ To copy variable information from an EGD Page to the clipboard: from the Summary View, right-click a
variable and select Copy Selection. The data is copied in .csv format.
Note To edit exchange signatures and configuration time, set the Layout Mode property to Manual. The Layout Mode
property displays when a Produced Page is selected in the Tree View.
3. Review the warning about manual Exchange Signature editing and click OK.
4. Make any desired changes to the signatures and configuration time and click OK.
Filter Toggle defaults to a filtered state. It displays items that have the same name but have a different Producer ID as
the open component.
Delete deletes the selected item(s). If the item(s) were saved as part of the configuration, they can be added again.
The EGD configuration server uses the producer ID to store all the documents for an EGD node.
When a component is saved, the EGD configuration is automatically published to the EGD configuration server. To avoid
unintentional overwriting of data, do not configure more than one .tcw file for a server.
• Compare command compares the component's EGD-produced data configuration with the EGD configuration server’s
content.
• UnConsumed Data command generates a report showing variables produced by this component that are not listed in
any other device’s consumed data file.
Note You can select devices to search against. The individual pages, with just variables, perform the same Compare.
The Referenced Devices item on the EGD tab also has a Compare command that compares the consumed variable
information for the open component against the EGD configuration server’s content.
Note When EGD configurations are edited in remote devices, you must refresh the configuration to ensure that the latest
variable information is used. The configuration is automatically refreshed when a component is opened, and when a Build is
performed in the component.
➢ To refresh the configuration of a referenced device: from the Tree View, right-click the device to be refreshed
and select Refresh.
➢ To create undefined variables for a single or multiple referenced device(s): from the Tree View, right-click
either the device or Referenced Devices and select Create Undefined Variables.
Modbus Properties
Property Description
Specifies the time in minutes that the Slave remains connected to the master over Ethernet when no
Connection Timeout
requests are being received. The valid range is one to 10.
specifies the Ethernet port to be used for slave-Ethernet communication. The valid port choices are
Ethernet Port
502 and 503.
Sets the interface type:
Ethernet is supported on both.
Shared (both Ethernet and serial) is only supported on Mark VIe gateway Modbus.
Interface
Settings Example
If set to True 32-bit example: 0x01234567 would be transmitted as 0x45 0x67 0x01 0x23
64-bit example: 0x0123456789ABCDEF would be transmitted as 0xCD 0xEF 0x89 0xAB 0x45
0x67 0x01 0x23
If set to False 32-bit example: 0x01234567 would be transmitted as 0x01 0x23 0x45 0x67
64-bit example: 0x0123456789ABCDEF would be transmitted as 0x01 0x23 0x45 0x67 0x89 0xAB
0xCD 0xEF
The ToolboxST application allows you to specify the variables on each page using a Data Grid. When you add a variable to a
page, both the Modbus Slave and the selected page are enabled on the controller. As you add and remove variables, the
controller is updated so that only pages containing variables are enabled. To completely disable the Modbus Slave, remove all
variables on all pages or select None as the Interface in the Property Editor.
When a variable is added, columns that display include:
Connected Variable is the variable that is read or written from the device or the referenced device. A connected variable
must be added before the other columns become active.
• BOOL is one bit of a 16-bit word (this is the only option if the connected variable is a BOOL.)
• INT is a signed 16-bit word that takes one register
• UINT is an unsigned 16-bit word that takes one register
• DINT is a signed 32-bit word that takes two registers
• UDINT is an unsigned 32-bit word that takes two registers
• REAL is a signed 32-bit float that takes two registers
• LREAL is a signed 64-bit float that takes four registers
Address specifies the register address. When a variable is created, the address is automatically set to a value adjacent to the
highest address previously on the page, but the automatic value can be modified. Any data types that are 32 bits or more
(DINT, UDINT, REAL, and LREAL) should be placed on odd addresses. The valid range for addresses is 1 to 65534. When
specifying an address for a BOOL variable, the bit 0-15 within the 16-bit word is represented by a decimal. For example, 1.00
selects register address 1 and bit 0, and 10423.7 selects register address 10423 and bit 7.
Raw Min, Raw Max, Eng Min, and Eng Max are columns that convert Modbus Slave variable data into engineering units.
The Raw Min and Raw Max columns control the minimum and maximum for the raw data. The Eng Min 0 and Eng Max
columns control the minimum and maximum engineering units to which the raw data will be scaled. (The BOOL data type
cannot be scaled.)
Name is a read-only identifier automatically generated from the register page name, the address, and, if necessary, an added
unique number.
For more information, refer to the following links:
For Modbus resources, go to: http://www.modbus.org
For Modbus protocol, go to: http://www.modicon.com/techpubs/toc7.html
• Device Version and Hardware Information displays all device firmware and hardware.
• Parameter provides four types of parameter reports: Change History, Compare to Device, Value, and Override List.
• Variable provides reports, such as global and configuration.
• Coding Practices provides reports for unwritten variables, multiple writes, multiple output assigned variables, and
unused I/O.
Unwritten Variables are used in blockware logic, but have no assigned values.
Multiple Writes are variables used in multiple locations, such as blockware logic, EGD, or I/O point configuration.
Multiple Output Assigned Variables displays all variables attached to more than one output.
Unused I/O are connected I/O values that are not used anywhere.
Spares are unconnected and unused I/O values.
➢ To create a report: from the View menu, select Reports and the desired report type.
Toolbar Icons
Icon Description
Zoom in
Zoom out
Get help
➢ To save a report: from the report File menu, select the desired command.
➢ To change the zoom level of a report: from the report View menu, select Zoom and select the desired zoom value
from the drop-down list.
➢ To sort a report column: click any column heading to apply a sort to that column. The first click sorts the column in
ascending order; a second click sorts the column in descending order.
Note Column
names that
display in
blue cannot
be moved.
Or
2. Select a column header and use the drag-and-drop feature.
➢ To search for text within a report: from the Report menu, click Find to display the Find dialog box.
If selected,
capitalization
in the test
string must
match the
text in the
report exactly
➢ To apply a report filter: from the Report menu, click Apply Filter to open the Edit Report Filter dialog box.
Available Available
columns comparison
(double-click and Boolean
to add to an operators
equation) (double-click
to add to an
equation)
Click to add
parentheses
Click OK to
accept the
filter equation
Enter filter that displays.
equation to
be used. Click Clear
to delete the
equation.
Click Cancel
to cancel the
equation but
keep the
current
settings.
When using the LIKE operator, you can prefix or suffix a wildcard character, either * or %, to the
LIKE right-hand value. The wildcard character can stand for any number of alphanumeric characters,
including zero. The wildcard character can only be present at the beginning or the end of the right-hand
value (for example, *value or value* or *value*)
AND Expressions to the left and right of the AND operator must both be True
OR Either the expression to the left or to the right of the operator must be True
NOT Expression to the right of the operator must be False
You can use as many groups of parentheses as necessary to define an expression.
String values must be enclosed in single quotes , for example 'string'
➢ To remove a report filter: from the Report menu, click Remove Filter. The filter is removed and all available rows
display.
➢ To save a filtered report: from the File menu, click Save Report.
• Variable Alias
• Second Language
• GE Rationalization
The Variable Alias and Second Language reports can be imported from either a .csv or an .xml file. Generator data can also be
imported.
Note A large number of parent/child relationships can cause the number of characters in an Excel .csv file cell to exceed the
maximum allowed (32,767). If your data exceeds this number of characters, do not attempt to use the Excel application.
Note Alarm Help templates for primary and secondary languages must be located within the system working folder.
Alarm Help files are generated when a build is performed for the device or when the
device is saved. However, Alarm help files are only generated when the Publish Alarm
Help property is set to True in the system Property Editor.
Attention
Tip: Change the Save as type to All Files (*.*) so you will
still be able to save the file as a .csv file.
Click Save .
5. Import the file into ToolboxST and verify that all the special characters display correctly.
If you use Microsoft Excel to modify the .csv file, make sure you save the file back to a
.csv file from a .xls file.
If the .csv file contains UTF–8 special characters, to avoid issues with displaying
special characters after import back into ToolboxST open the file with Notepad and
Attention save the file with Encoding set to UTF-8. Refer to the procedure To avoid issues with
second language special characters during import
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
Warning measures should be strictly enforced in conjunction with this procedure.
➢ To force a value or change a previously forced value: from the Forced Variables dialog box, double-click a
value to display the Send Value dialog box.
➢ To remove a single forced value: right-click a forced variable and select Remove Selected Forces.
➢ To remove all forced values: right-click anywhere inside the Forced Variables dialog box and select Remove All
Forces.
➢ To print a report
1. From the File menu, select Print.
2. In the Print dialog box, verify that the settings are correct and click OK.
➢ To display the Global Variables window: from the EX2100e Component Editor View menu, select Global
Variables.
The Global Variables window is particularly useful when you want to modify a property for multiple variables. For example,
to move multiple variables onto an EGD page, select the rows for the desired variables and then change the EGD Page
property in the Property Editor.
Because only existing global variables can be changed, new variables cannot be added from the Global Variables window.
You cannot make any change that affects the name of the global variable (like Name or Global Name Prefix). Variables from
an instanced library user block can only be modified if the Merge Variables at Instance property of the Programs item on the
Software tab is set to True.
Select from the Available Attributes table using the arrows to add them to or remove them from the
Selected Attribute table. Click Export to export alarms for Rationalization.
GE Rationalization is an available selection for export (as displayed in this figure). However, it is only available for
backwards compatibility.
Note The GE Rationalization report contains a column for Parent Alarms and for Child Alarms. A large number of
parent/child relationships can cause these two columns in the .csv file to be incompatible with the Excel application. The
application allows a maximum limit of 32,767 characters in a cell.
When a GE Rationalization report is generated, it can be saved as a .csv file, modified, and then imported back into the
ToolboxST application. For the procedures to export and import GE Rationalization reports, refer to the section Import
Reports.
➢ To import alarms to the library: from the System Editor Tree View, open the Library Container Editor.
The report displays all variables found in the library; variables missing from the library display in red. It is possible to
re-export the report to include all rows not found during the original import.
➢ To import the report back into the controller: from the controller File menu, select Import and GE
Rationalization Report.
The report automatically overrides properties in the controller configuration to change the linked library code.
➢ To open a stand-alone Watch Window: from the Start menu, select All Programs, GE ControlST, ToolboxST,
and Watch Window.
Enter a Name,
and a Description
(optional), and
click OK.
Note If this Watch Window is being opened for the first time, the list is empty. Add or import a new Watch Window.
➢ To open an existing Watch Window: from the System Editor Tree View, right-click the system and select Insert
Existing and Watch Window.
➢ To open a Watch Window: from a Component Editor View menu, select Watch Windows.
If you selected
System
Component in the
previous page,
select the desired
component from
the drop-down list
and click Next.
The variables
will display here.
Click Finish .
Once a variable is added to a Watch Window, right-click the variable row header to perform the following actions:
Note When a system component providing signals to a Watch Window is replicated, the Watch Window is replicated as
well.
Forcing of protective functions is never permissible for an operating unit. All safety
Warning measures should be strictly enforced in conjunction with this procedure.
Note The Watch Window tool only exports grid columns necessary to retrieve variable information. For example,
DatasourceName from the exported file is used to retrieve the variable’s remaining properties from the system. User-defined
columns such as User Comment are also included.
➢ To save a Watch Window: from the <Watch Window name> File menu, select Save As to save the Watch Window
as a .watch file in a user-selected location,
or select Save to save the Watch Window as a .watch file in the Tools folder in the system.
22.27 LiveView
The LiveView feature allows you to display a graphical representation of live data from various sources in the system.
LiveViews can be added to a ToolboxST system, to a component, or opened as a standalone editor.
➢ To add an existing LiveView: from the System Editor, right-click the system and select Insert Existing and
LiveView.
➢ To edit a LiveView: from the System Editor, right-click a LiveView and select Edit System Component.
➢ To add a LiveView from a Component Editor: from the View menu, select LiveViews.
Reference point
Select a Bar
Color for the
High Alarm and
High Warning
range above the
reference point
Select a Bar
Color for the
Normal range
above the
reference point
Select a Bar
Color for the
Low Alarm and
Low Warning
range above the
reference point
If the Behavior
property is set to
Momentary and
the On Push
property is set to
False, the state of
the attached
variable is set to
True when the left-
mouse button is
clicked
Locked enables
or disables the
ability to move
and resize objects
Locked Property
Or
Variables display
here. Click
Finish
Note You can also attach a variable by entering the variable name in the Property View.
➢ To display constants
The Reconcile Differences dialog box displays constants with both initial and live values.
• For constants when the ToolboxST initial value was checked, that value is either sent to the controller (where the OK
button is clicked), or a pcode record is created, causing the next online download to change both the initial and live
values.
• For constants when the live value was checked, the ToolboxST initial value is set equal to the controller live value. This
causes a minor revision configuration change to Not Equal. A Build and Download to the controller is required to
complete the reconcile function.
➢ To connect to a controller
1. From the System Editor, open an EX2100e Component Editor.
2. From the Device menu, select Online or click Go On/Offline.
If you are connecting to a simplex controller, a connection is automatically established with the M1 controller. In a Warm
backup or Dual configuration, a dialog box displays to select either a redundant controller (either M1 or M2) or the controller
currently designated as the supplier of initialization data.
Icons Conditions
All controllers functioning normally.
Controller trip
• Compressing variables
• Changing frame rate
• Changing the background blockware period
• Adding the first I/O pack to a controller
• Changing redundancy type
• Changing the platform type, which changes the number of Ethernets
• Changing any NTP configuration on a controller
State Description
Powerup Power up controller
Master initialization Controller is loading its own configuration
Designated controller
Determine which controller is designated in a redundant controller configuration
determination
Perform initialization of non-designated controllers with NVRAM, command variables, and
Data initialization
constants
Inputs enabled Wait in this state for all required I/O packs to start transmitting inputs
Input voting Check voting inputs prior to execution of application code
Exchange initialization Populate redundant controllers with dc state variables prior to voting
Exchange state variables so that a controller joining a running system will not have a step in
Exchanging
its initial calculations
Sequencing Turn on the application code and execute each task at least once before driving outputs
Controlling Turn on outputs
Loading Online load is in progress
Load complete Online load has finished. Wait for re-synchronization of redundant controllers
Fail Failure has occurred.
Click Go to Secure.
Note When the process is in the Authenticated state, the controller is retrieving a certificate revocation list from the CA
Server to verify that the requestor has a valid certificate.
A controller cannot communicate on a network until these controller setup tasks are
completed.
Attention
Prerequisites
If this is a new UCSB controller received directly from the factory, or a UCSB that has
not been previously configured, the IP address must be set using a USB flash device.
Skip to step b in this procedure.
Attention
i. Enter the device password and select a COM port and the appropriate Channel.
i. Insert a non-encrypted removable USB 2.0–compliant flash device with a 4 GB minimum capacity into the HMI
computer USB port.
ii. Initialize the controller.
iii. Remove the flash device from the USB port of the HMI computer, then click Finish.
iv. Remove power from the controller.
v. Insert the flash device into the controller. For a UCSB, press and hold in the Backup/Restore button.
Note Refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose Applications System
Manual (GEH-6721_Vol_II), the section UCSB Backup and Restore for this procedure.
vi. Apply power to the controller while continuing to press the button until the On LED on the front of the
controller becomes solid green, then release the button. The On LED turns off when the process is complete.
vii. Remove power from the controller, remove the USB flash device, then re-apply power to the controller.
viii. If using redundant controllers, repeat this procedure for the S and T controllers (if TMR) or S (if dual). Be sure
to select the correct Channel.
The user must change the factory default controller password for a device. The
maximum number of characters for the new password is limited to characters. The
new password cannot be the factory default password. If you do not know the factory
default password, contact the nearest GE Sales or Service Office, or an authorized GE
Sales Representative.
Attention For additional details, refer to Mark VIe and Mark VIeS Control Systems Volume II:
General-purpose Applications, GEH-6721_Vol_II, the chapter Controller Diagnostic
Alarms, alarm 547.
Note For a device configured with redundant controllers, the password applies to all controllers in that device.
Note This password is required for configuring the network address during controller setup.
When the password for the replacement controller is successfully synchronized to the other controller passwords in the set, a
message displays in the Log window.
• Boot Loader starts the operating system for the controller much like the BIOS on a desktop computer. Changes to the
boot loader are very infrequent.
Note Not all devices have the boot loader. In this case, the boot loader is contained within the base load.
• Base Load is the operating system for the controller. While changes to the base load are more likely than changes to the
boot loader, they still occur infrequently.
• Firmware provides the controller functionality. It can be updated over the lifetime of the controller to incorporate new
features and bug fixes.
• Application Code contains the configuration of the controller as created in the ToolboxST application. Whenever a
change is made to the configuration, the application code must be downloaded. There are two types of application code
download, online and offline. An online download (very commonly performed) changes the configuration without
interrupting control and the new configuration takes effect between control frames. An offline download requires a
controller restart (performed less frequently).
• Parameters contain specific configuration for the excitation portion of the controller.
Boot loader, base load, firmware, offline application code downloads, and parameter
downloads all require the target device to be restarted. Before downloading new
software to a controller, take the necessary steps to secure the control equipment to
prevent equipment damage and personal injury.
Warning
Note The type of software download needed is determined by which changes have been made to the controller
configuration.
The Download Wizard is used to download software to an EX2100e component and its associated modules over an Ethernet
connection. The Download Wizard can automatically examine the system configuration to locate out-of-date software, or you
can manually select individual items to download.
Note Certain conditions do not allow a download, such as an incorrect platform type. Check the Component InfoView for
errors that may prohibit a download.
1. From the EX2100e Component Editor Device menu, select Download and Download Wizard.
2. If you have changed configuration settings since the last Build operation, a message box displays indicating that the
software is out of date. Click Yes to build the current configuration.
3. When the welcome wizard displays, click Next.
The APP_STATE block can prohibit a download and restart of the controller.
Attention
If the DOWNLOAD_OK input of the APP_STATE block is set to True, all downloads are allowed. If this value is set to
False, all downloads (except Update DDR and Device Backup) are prohibited. This condition also applies to an attempted
download of an I/O pack from the Hardware tab of the Component Editor. If the download is prohibited, a warning displays in
the Component InfoView, and the Download EX2100e Controller wizard displays the prohibited download. For additional
information on the APP_STATE block, refer to the Mark VIe Controller Standard Block Library Instruction Guide
(GEI-100682).
➢ To update the DDR: from the Device menu, select Update Dynamic Data Recorder and follow the instructions
on the ToolboxST windows.
➢ To view and set the controller time: from the Device menu, select View/Set Time... and follow the instructions
on the ToolboxST windows.
From the
View menu,
select
Reconcile
Parameter
Differences
Note From the Component Infoview, you can also double-click the Status tab to display the Reconcile Parameter
Differences dialog box.
➢ To open Controller Diagnostic View for Controller: from the View menu, select Controller Diagnostics.
The Controller Advanced Diagnostic view displays additional information from the controller.
➢ To open Advanced Diagnostic view: from the View menu, select Diagnostics and Controller Advanced
Diagnostics.
Note Before modifying Totalizer values in a redundant controller, connect to the R controller and make sure all other
redundant controllers are healthy and communicating. (Refer to the section Connect to a Controller.)
Note Totalizer passwords are specific to the connected redundant controller (R, S, or T) and cannot be used on other
controllers.
Note Totalizer passwords are usually valid for 24 hours from time of creation.
2. From the Modify Totalizer Value dialog box, enter the new value and click OK.
➢ To create a component: from the System Editor Tree View, right-click the system and select Insert New,
Controller, Static Starter Control, and LS2100e.
Property Editor
allows you to edit
the item currently
selected in the
Tree View
Component
InfoView displays
information about
the currently
selected item
➢ To edit the controller: select an item in the Tree View. The configuration information for that item displays in the
Summary View and Property Editor.
➢ To edit a property in the Property Editor: select an item by clicking its value 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.
Tip � If there is a build problem, the error is listed on the Log tab. Double-click the error. The input focus goes to the
location in the component configuration where the error occurred.
Status tab displays operating state and equality information about the 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 at the beginning of some lines indicates that the variable is being written at that location.
Find Results tab displays the results of the Finder.
Info tab displays context-sensitive descriptions for the selected Tree View or Summary View item.
When the Build command is performed or the Build icon is clicked, a dialog box displays a message to view the change log.
Note Right-click either an Error or a Warning and select Go To to find its location in the ToolboxST application.
Note Some Data Grids, especially those without an Append Row, may not support all available features.
Quickly set a property to the Left-click the row header for the first row to be edited. Then, while pressing the CTRL key,
same value for multiple rows left-click added row headers. After selecting all desired rows, use the Property Editor to
change properties for all selected rows. (Some properties are omitted when a group of rows is
selected, and properties with conflicting values will display no value in the property editor.)
To... Do this:
Resize a column Drag the vertical bar on the right of the column header to a new location.
Quickly remove a single column Right-click the column header and select Hide Column.
Move a column to a different location Drag the column header to a new location.
Sort by a column Click a column header. The column sorts in ascending order. To sort in descending
order, click the column header again.
Reset columns to the original Right-click any column header and select Default Column Organization.
configuration
Add or remove columns Right-click any column header and select Organize Columns to display the
Organize Columns dialog box.
Select a
column name
and use the up
arrow to move
it to the left-
most side of
the Data Grid.
in the destination grid and select Paste Row(s) to insert the row into its new
location.
Copy and paste multiple rows Left-click the row header for the first source row. Then, while pressing the CTRL key,
left-click added row headers. After selecting all desired rows, continue to hold down the
CTRL key and right-click any selected header. From the shortcut menu, select Copy
Selected/Current Rows to place the rows on the clipboard. Then, right-click the header
for the append row in the destination grid and select Paste Row(s) to insert the rows into
their new location.
Copy and paste a range of two or Click the top left cell of the desired range and drag to the bottom right cell. Right-click the
more cells selected region and select Copy Selected/Current Rows to place the cells on the
clipboard. Then, click the top left cell of the destination range and drag to select the
same number of columns and rows that were copied to the clipboard. Right-click inside
the destination region and select Paste Row(s).
Move rows between data grids Arrange windows on screen so both the source and destination grid are visible. (An
entry in a Tree View is acceptable as a destination). Left click the row header for the first
row. Then, while pressing CTRL, click any added row headers to be moved. Release the
CTRL key and drag a row header to the new data grid.
Add a variable to a block diagram, Arrange windows on screen so both the source grid and a destination block diagram,
Trender window or Watch Window Trender window or Watch Window are visible. Then, drag the row header for the variable
from a data grid 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.
➢ To open the Settings dialog box: from the Component Editor, select Options and Settings.
Show Boot Loader displays the boot loader in the Download Wizard when it does not have to be downloaded.
Show Short Names, when set to True, displays the abbreviated names for DSP parameters and variables.
Access Rights
Access Rights Description
Allows you to set Modify Data and Modify Design access rights to pre-defined user roles. Once roles
Access Roles
have been assigned to a protected object, only users with those roles can access the object.
Allows you to make changes to data values associated with an object without changing how it works.
Modify Data 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.
Allows you to change the way a protected object works. For example, this protects block creation and
Modify Design 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.
Note Passwords are case-sensitive – secret and Secret are not considered to be the same password.
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.
➢ To clear all passwords and protect the component: from the Device menu, select Restore Password
Protection.
Protection Properties
Property Description
Access Roles Allows you to set modifying data and design rights to previously defined user roles
Allows you to modify data values and forcing of variables
2. Select the .csv file to import. Make sure the .csv file has the following format:
Name,Value
ExciterType,Brushless
ControlType,Simplex
BridgeType,77mm
2. Select the .xml file to import. Make sure the .xml file has the following format:
2. Select the .csv file to import. Make sure the .csv file has the following format:
Name, Value,Source
AFFL, 1599, EXSetting
EstFireComp, .6766, EXSetting
➢ To upgrade a component
1. Install the latest version of the ToolboxST application.
2. Start the ToolboxST application, open the system .tcw file, and double-click a static starter control to display the
Component Editor.
3. From the File menu, select Upgrade.
4. When the Welcome wizard displays, click Next.
5. Select the version to upgrade to and click Finish.
A Compare Results window displays differences between the two selected devices.
➢ To configure LS2100e Static Starter control: open the Component Editor and select the General tab.
Properties
Property Description
Stores information concerning alarm and event transitions and variable set commands on the
Command Event Log
controller file system. This data can be viewed by an external client through a web interface.
Specifies the maximum size (as a percentage) of both the command and event portions of the
% Command Size
Command and Event log
Specifies the maximum size (as a percentage) of the event portions of the Command and Event
% Event Size
log
Log to Disk Specifies whether Command events should be logged to the CompactFlash® on the controller
Specifies the number of days that the Command and Event log is kept if the allocated space is not
Time
exceeded
When set to True, enables access to controller web pages if they are provided by the controller or
another product. The controller can provide a set of default pages as part of the firmware
Controller Web Pages
download. Product web pages can also be downloaded to the controller. For example, the 1.5 MW
Wind Turbine uses product-specific web pages that are downloaded separately.
Enable Controller Web When set to True, activates the Web server on the controller and displays the Web Page tab
Pages When set to False, a major configuration difference occurs that forces an offline load.
Password Allows you to create or change a password
Description Functional description of the current controller
Enable Alias Prefix If set to False, the device prefix name is not displayed in CIMPLICITY screens (default is False)
If set to False, the device prefix name is not displayed in CIMPLICITY screens (default is False).
Major Revision Time of the Build command performed after the most recent major change (Major changes require
the controller to be restarted after download).
Time of the Build command performed after the most recent minor change (Minor changes do not
Minor Revision
require a controller restart)
Name of the current controller. It is read-only in the Component Editor, and can only be changed
Name
from the System Editor.
NTP Configuration Determines how the Network Time Protocol client synchronizes the controller time
Configuration Manual When set to True, displays the Mode property that allows you to override the system NTP settings
Override and use the local device settings only
Includes:
• Disabled – controller does not perform any time synchronization
Mode
• Broadcast – client listens for NTP broadcasts on the network
• Unicast – client uses the specified servers to obtain the time
NTP Configuration
Optional IP address of a secondary (backup) server used when unicast mode is selected
Secondary Server
Platform Type of hardware on which the control code is started
Read-only property that reflects the version of the product associated with the selected
Product Version component. The version number is set when the configuration is first created, and is updated with
each product upgrade.
Product SubType Specific type of selected LS2100e control system (Regulator or Static Start)
Columns
Column Description
Name Unique identifier for the attribute
Description Stores added comments about the attribute
Value Displays and modifies the current attribute value
Pre-defined trends are used to automatically populate the Trender with a list of variables. The parameters, variables and
pre-defined trends are grouped under menus by function.
When the Tool Value is changed, you are asked if the value should be sent to the device configuration.
Right-click a row to display the menu for the selected parameter.
Note Since some parameters do not display on diagrams, Diagram is not always a menu option.
Note A pointer parameter points to a variable. All pointer parameters display Var Address in the Units column of the
Summary View.
Preset enumerations defined for specific parameters display in the drop-down list.
As you enter the variable name in the Find Text field, the Variable List highlights that variable in an alphabetical list
containing all variables. Selecting the Anywhere in check box displays only the variables containing the letters as they are
entered.
The Diagrams tab graphically displays the parameters, sequencing, and variables of a static starter control. Each diagram
contains drawings and text that represents a particular aspect of the controller’s configuration or state. Diagrams also allow
you to edit parameters and display variable values, when the ToolboxST application is online with a device.
➢ To view diagrams: from the Component Editor, click the Diagrams tab.
Zoom In and Zoom Out make the diagram larger and smaller, respectively.
Item Help opens an item-specific help window, if available.
Top Left, Top Right, Lower Left, and Lower Right scroll the diagram to those positions.
Save to File creates an Enhanced Windows Metafile (.emf) of the drawing that includes live values.
Print sends the diagram that includes live values to a printer.
Right-click a hyperlink to open a shortcut menu.
Zoom In and Zoom Out make the diagram larger and smaller, respectively
Zoom To scales the diagram to the scale selected from the drop-down list. Determines the type of control
interface to use for this device.
Actual Size resets the zoom to the normal scale factor (100%).
Fit Page causes the diagram to fill the entire Summary View.
Fit Width causes the entire width of the diagram to fit in the Summary View.
Modify displays the attributes of variables and parameters. Variable attributes cannot be modified. When a parameter is
right-clicked, a text box displays to modify the value.
Item Help opens the help file for the selected variable.
Diagram allows you to navigate to other diagrams that contain the variable.
Goto Settings switches to the Settings tab and navigates to the selected variable.
Send to Device sends the parameter value to the device, if the ToolboxST application is online.
When you double-click a pointer parameter, an ellipsis button displays. Click it to open the Select Variable dialog box.
If the ToolboxST application is online with the static starter control, it optionally sends the new parameter value to the
controller. You may also be prompted to enter initials or reset the controller.
Note The Add Existing Program command reads an .xml file from another system or controller into the current controller.
OR
When the controller is online, double-click the live value of the variable _Enable for the task, select True to enable the task
or False to disable the task, then click Send & Close.
Disabled
Task Disabled
• Function block libraries describe software that is part of the controller firmware
• User block libraries combine these function blocks into user blocks
Attention
The Protection
property defines
access rights to
the properties list.
➢ To instance a user block: from the Tree View, right-click a user block and select Instance.
Note Variables can also be added in the Summary View by directly editing the append row of the variable grid.
➢ To unlink a program: from the Tree View, right-click a program item and select Unlink Permanently.
The linked icon next to the item in the Tree View changes and the program is unlinked from the library.
Property Editors
Programs
Removes the unused variables for all linked user blocks in this device when the user block is
Remove Unused Variables
instanced
Program
Library Type Name of the library definition that this program came from
Properties control the Access Roles, Modify Data, Modify Design, and View Design
Protection
permissions for this program
Task
Block Type Name of the user block definition in the library from which this task started
Help File Allows you to locate the Help file by clicking the ellipsis button
Help Text Locally defined Help that supersedes the global Help
Properties control the Access Roles, Modify Data, Modify Design, and View Design
Protection
permissions for this task
Revision History Allows you to edit the revision history by opening the Edit Text dialog box
Schedule Offset Offset from beginning of frame at which the task runs
User Block
Block Type Name of the library block of which the selected block is an instance
Unique identifier that allows the block to be referenced from other locations in the ToolboxST
Instance Name
application
Instance Script Causes the script to run when the block is instanced
Programs
Left Location of the left of the selected block
Selected Pin Pin currently highlighted in the diagram
Show Description When set to True, displays the description of the selected block
Enable When set to True, enables variables for the selected block
Version Version number for the source of the selected block instance
Execution Order Determines when this block is started
➢ To add a variable to a program: from the Software tab, expand the Programs item.
Includes:
• Not Logged
Controller
• Average Linear: this is a linear average {1/N * sum(values)}
Connected
• Average Linear Angle: This is an average for angle based variables; it takes into account 0 degrees
equals/360 degrees wrap-around for angles.
• Average Cosine Phi: This average calculation is for power factor (cos phi). It effectively calculates the
average of the arccosine of each of the data values during the interval. The value returned is the
cosine of this average.
• Data Snapshot: This selection is for end-of-interval values. The last value captured during the
specified interval is returned.
Enables the automatic collection by the Historian when:
Historian
Boolean and set to Logged on Change
Deadband
Analog and set to 0 or higher
Historian
Deadband Defines the deadband value as either engineering units or percent of range.
Definition
Enables the automatic collection by the Recorder when:
Recorder
Boolean and set to Logged Continuous or Logged on Change
Deadband
Analog and set to 0 or higher
Recorder
Deadband Defines the deadband value as either engineering units or percent of range
Definition
Usage
Allows a variable to be designated as a configuration setting. The default value is False, which prohibits
Control Constant
changing live values. Setting the property to True allows you to change live values.
If set to True, downloads extended information to the controller that is used by the web server, as well as
Download Info other processes. For example, to view alarms on the touchscreen, the Download Info parameter must be
set to True for each alarmed variable.
EGD Page Used to assign the variable to an Ethernet Global Data Page
Used primarily for EGD:
ReadOnly variable can be read on EGD
External Access
ReadWrite variable can be written to through EGD
NoAccess variable cannot be changed with the ToolboxST application
The variable's global name prefix type (None, Full, Block, Program, Task).
This controls the form of the global name that displays on the EGD page. For example, the name for
variable IGVA in user block VG_Health in task Task1 in program CORE would display (depending on the
Global Name Prefix) as:
Global Name
None: IGVA
Prefix
Full: CORE.VG_Health.IGVA
Block: VG_Health.IGVA
Program: Task1.IGVAv
Task: Task1.IGVAv
From the
Summary View,
select a variable.
From the Type
drop-down list,
select the
variable type.
Or:
from the
Property
Editor,
select Type
and the
variable type
• Replace the blockware detail view for the task or userblock with a graphic
• Add the graphic as a Sheet tab in the block’s detail view
• Display the graphic in a separate window using the eyeglasses button on the toolbar
• Diagnostic Alarms
• Process Alarms
• Hold List Alarms
• Events
• Sequence of Events (SOE)
Beginning with ControlST V04.04, controller configurations must not exceed the
following limits. If these limits are exceeded, reduce the number of configured Process
Alarms, Events, and Holds.
Note For further details, refer to the Mark VIe and Mark VIeS Controls Systems Guide (GEH-6721_Vol_I), the chapter
Alarm Overview, and the Workstation Alarm Server Instruction Guide (GEI-100626).
Parent and child Alarms can be exported using Alarm Rationalization. Parent alarms only can be imported from a .csv file.
Corresponding child Alarms are automatically placed in the configuration.
➢ To change the frame multiplier or the schedule offset: from the Summary View, click the Frame Multiplier
or Schedule Offset cell and select from the drop-down list.
Note Since the schedule offset depends on the frame multiplier, it is possible to select a frame multiplier for which the
current schedule offset is invalid. This causes a validation error when you build the application.
Note There is a 12 MB size limit on the memory that can be allocated to the DDRs. If this memory allocation is exceeded,
an error is reported during validation.
➢ To add a variable
1. From the DDR tab Tree View, right-click the DDR and select Add Variable.
2. Select the desired variables and click OK.
DDRs can be updated separately from the application code download.
➢ To update a DDR: from the Device menu, select Download and Update Dynamic Data Recorder.
Note DDRs cannot be downloaded if there is a major difference in the device. In this case, the application code must be
downloaded.
➢ To import or export a DDR: from the DDR tab Tree View, right-click the desired DDR and select Import
Configuration or Export Configuration.
Note If the .xml file being imported contains the formatting flags %n, it is replaced by the component Design Memo (DM)
number. This is a GE Power Systems project number and can be edited by selecting the General tab and Requisition Info.
4. Create a User Block in the program, and add two FuncGen blocks from the Data Collection section. Set up the pins
on the two blocks as follows. FuncGen1 is set up as a Sine wave generator and FuncGen2 is set up as a Triangle wave
generator.
5. Add the two variables SineOut and TriangleOut to the DDR. Set the Frame Period Multiplier to 3, which means a
sample is collected every 120 ms. The base frame period is typically 40 ms. Set the PreTrigger samples to 20 and the
PostTrigger samples to 100, so that the entire capture takes 14.4 seconds.
9. From the View menu, select Trenders to add a new trend and upload the capture buffer.
10. From the Trender window, select Edit and Add Traces to display the Trender - Add Trace Wizard.
11. From the wizard, select Capture Buffer/Dynamic Data Recorder to select the DDR to upload.
Note When the first Produced Page is created, it automatically becomes the default page.
Tip � Any variable defined with $Default as the EGD page name is automatically placed on the currently selected default
page.
➢ To delete a page: from the Tree View, right-click the page to delete and select Delete.
➢ To compress a single page: from the Tree View, right-click the page to compress and select Compress.
➢ To compress all Produced Pages in a component: from the Tree View, right-click Produced Pages and
select Compress All.
Tip � If the variable to be added to the EGD page is already in use on the Software tab, you can add the variable without
using the EGD tab. To add a variable from the Software tab, select the desired variable(s) in the Summary View and set the
EGD Page property using either the Summary View or the Property Editor.
➢ To add a variable to a produced page: from the Tree View, right click a Produced Page and select Add
Variable to display the Select a Variable dialog box.
➢ To delete a variable from an EGD Page: from the Summary View, right-click the variable to delete and select
Delete Selected Row(s).
➢ To copy variable information from an EGD Page to the clipboard: from the Summary View, right-click a
variable and select Copy Selection. The data is copied in .csv format.
Note To edit exchange signatures and configuration time, set the Layout Mode property to Manual. The Layout Mode
property displays when a Produced Page is selected in the Tree View.
3. Review the warning about manual Exchange Signature editing and click OK.
4. Make any desired changes to the signatures and configuration time and click OK.
The EGD protocol includes a command mechanism that obtains the status of a Class 2 or higher EGD device. LS2100e is a
Class 3 EGD device. When any EGD item in the Tree View other than a referenced device is selected, the EGD Statistics
from [Device] tab displays the statistics from the open component. When a Referenced Devices item is selected, the statistics
are obtained from that referenced device, and the name of the tab page changes accordingly.
Status columns in the Summary View include the following:
Exchange is the Exchange identifier <device name>.<exchange number>.
Configuration Time is the time that the exchange was configured.
Due Time is the time that a consumer data packet must be received for an exchange to remain valid.
Status is the health of the exchange.
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.
Message Count is the number of data production packets produced or consumed since initialization.
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.
Filter Toggle defaults to a filtered state. It displays items that have the same name but have a different Producer ID as
the open component.
Delete deletes the selected item(s). If the item(s) were saved as part of the configuration, they can be added again.
The EGD configuration server uses the producer ID to store all the documents for an EGD node.
When a component is saved, the EGD configuration is automatically published to the EGD configuration server. To avoid
unintentional overwriting of data, do not configure more than one .tcw file for a server.
• Compare command compares the component's EGD-produced data configuration with the EGD configuration server’s
content.
• UnConsumed Data command generates a report showing variables produced by this component that are not listed in
any other device’s consumed data file.
Note You can select devices to search against. The individual pages, with just variables, perform the same Compare.
The Referenced Devices item on the EGD tab also has a Compare command that compares the consumed variable
information for the open component against the EGD configuration server’s content.
Note When EGD configurations are edited in remote devices, you must refresh the configuration to ensure that the latest
variable information is used. The configuration is automatically refreshed when a component is opened, and when a Build is
performed in the component.
➢ To refresh the configuration of a referenced device: from the Tree View, right-click the device to be refreshed
and select Refresh.
➢ To create undefined variables for a single or multiple referenced device(s): from the Tree View, right-click
either the device or Referenced Devices and select Create Undefined Variables.
• Device Version and Hardware Information displays all device firmware and hardware.
• Parameter provides four types of reports: Change History, Compare to Device, Value, and Override List.
• Variable provides reports, such as global and configuration.
• Coding Practices provides reports for unwritten variables, multiple writes, multiple output assigned variables, and
unused I/O.
Toolbar Icons
Icon Description
Zoom in
Zoom out
Get help
➢ To sort a report column: click any column heading to apply a sort to that column. The first click sorts the column in
ascending order; a second click sorts the column in descending order.
Column
names that
display in
blue cannot
be moved.
Or
2. Select a column header and use the drag-and-drop feature.
If selected,
capitalization
in the test
string must
match the
text in the
report exactly
➢ To apply a report filter: from the Report menu, click Apply Filter to open the Edit Report Filter dialog box.
Available Available
columns comparison
(double-click and Boolean
to add to an operators
equation) (double-click
to add to an
equation)
Click to add
parentheses
Click OK to
accept the
filter equation
Enter filter that displays.
equation to
be used. Click Clear
to delete the
equation.
Click Cancel
to cancel the
equation but
keep the
current
settings.
When using the LIKE operator, you can prefix or suffix a wildcard character, either * or %, to the
LIKE right-hand value. The wildcard character can stand for any number of alphanumeric characters,
including zero. The wildcard character can only be present at the beginning or the end of the right-hand
value (for example, *value or value* or *value*)
AND Expressions to the left and right of the AND operator must both be True
OR Either the expression to the left or to the right of the operator must be True
➢ To remove a report filter: from the Report menu, click Remove Filter. The filter is removed and all available rows
display.
➢ To save a filtered report: from the File menu, click Save Report.
• Variable Alias
• Second Language
• GE Rationalization
Only the Alias and Second Language properties can be modified. The Variable Alias and Second Language reports can be
imported from either a .csv or an .xml file. Generator data can also be imported.
Note A large number of parent/child relationships can cause the number of characters in an Excel .csv file cell to exceed the
maximum allowed (32,767). If your data exceeds this number of characters, do not attempt to use the Excel application.
Note Alarm Help templates for primary and secondary languages must be located within the system working folder.
Alarm Help files are generated when a build is performed for the device or when the
device is saved. However, Alarm help files are only generated when the Publish Alarm
Help property is set to True in the system Property Editor.
Attention
Tip: Change the Save as type to All Files (*.*) so you will
still be able to save the file as a .csv file.
Click Save .
5. Import the file into ToolboxST and verify that all the special characters display correctly.
If you use Microsoft Excel to modify the .csv file, make sure you save the file back to a
.csv file from a .xls file.
If the .csv file contains UTF-8 special characters, to avoid issues with displaying
special characters after import back into ToolboxST open the file with Notepad and
Attention save the file with Encoding set to UTF-8. Refer to the procedure To avoid issues with
second language special characters during import
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
Warning measures should be strictly enforced in conjunction with this procedure.
➢ To force a value or change a previously forced value: from the Forced Variables dialog box, double-click a
value to display the Send Value dialog box.
➢ To remove a single forced value: right-click a forced variable and select Remove Selected Forces.
➢ To remove all forced values: right-click anywhere inside the Forced Variables dialog box and select Remove All
Forces.
➢ To print a report
1. From the File menu, select Print.
2. In the Print dialog box, verify that the settings are correct and click OK.
➢ To display the Global Variables window: from the Component Editor View menu, select Global Variables.
The Global Variables window is particularly useful when you want to modify a property for multiple variables. For example,
to move multiple variables onto an EGD page, select the rows for the desired variables and then change the EGD Page
property in the Property Editor.
Because only existing global variables can be changed, new variables cannot be added from the Global Variables window.
You cannot make any change that affects the name of the global variable (like Name or Global Name Prefix). Variables from
an instanced library user block can only be modified if the Merge Variables at Instance property of the Programs item on the
Software tab is set to True.
Select from the Available Attributes table using the arrows to add them to or remove them from the
Selected Attribute table. Click Export to export alarms for Rationalization.
GE Rationalization is an available selection for export (as displayed in this figure). However, it is only available for
backwards compatibility.
Note The GE Rationalization report contains a column for Parent Alarms and for Child Alarms. A large number of
parent/child relationships can cause these two columns in the .csv file to be incompatible with the Excel application. The
application allows a maximum limit of 32,767 characters in a cell.
When a GE Rationalization report is generated, it can be saved as a .csv file, modified, and then imported back into the
ToolboxST application. For the procedures to export and import GE Rationalization reports, refer to the section Import
Reports.
➢ To import alarms to the library: from the System Editor Tree View, open the Library Container Editor.
The report displays all variables found in the library; variables missing from the library display in red. It is possible to
re-export the report to include all rows not found during the original import.
➢ To import the report back into the controller: from the controller File menu, select Import and GE
Rationalization Report.
The report automatically overrides properties in the controller configuration to change the linked library code.
➢ To open a stand-alone Watch Window: from the Start menu, select All Programs, GE ControlST, ToolboxST,
and Watch Window.
➢ To create a Watch Window: from the System Editor Tree View, right-click the system and select Insert New,
Tool and Watch Window.
Enter a Name,
and a Description
(optional), and
click OK.
Note If this Watch Window is being opened for the first time, the list is empty. Add or import a new Watch Window.
➢ To open an existing Watch Window: from the System Editor Tree View, right-click the system and select Insert
Existing and Watch Window.
➢ To open a Watch Window: from a Component Editor View menu, select Watch Windows.
If you selected
System
Component in the
previous page,
select the desired
component from
the drop-down list
and click Next.
The variables
will display here.
Click Finish .
Once a variable is added to a Watch Window, right-click the variable row header to perform the following actions:
Note When a system component providing signals to a Watch Window is replicated, the Watch Window is replicated as
well.
Forcing of protective functions is never permissible for an operating unit. All safety
Warning measures should be strictly enforced in conjunction with this procedure.
Note The Watch Window tool only exports grid columns necessary to retrieve variable information. For example,
DatasourceName from the exported file is used to retrieve the variable’s remaining properties from the system. User-defined
columns such as User Comment are also included.
➢ To save a Watch Window: from the <Watch Window name> File menu, select Save As to save the Watch Window
as a .watch file in a user-selected location,
or select Save to save the Watch Window as a .watch file in the Tools folder in the system.
24.25 LiveView
The LiveView feature allows you to display a graphical representation of live data from various sources in the system.
LiveViews can be added to a ToolboxST system, to a component, or opened as a standalone editor.
➢ To add an existing LiveView: from the System Editor, right-click the system and select Insert Existing and
LiveView.
➢ To edit a LiveView: from the System Editor, right-click a LiveView and select Edit System Component.
➢ To add a LiveView from a Component Editor: from the View menu, select LiveViews.
Reference point
Select a Bar
Color for the
High Alarm and
High Warning
range above the
reference point
Select a Bar
Color for the
Normal range
above the
reference point
Select a Bar
Color for the
Low Alarm and
Low Warning
range above the
reference point
If the Behavior
property is set to
Momentary and
the On Push
property is set to
False, the state of
the attached
variable is set to
True when the left-
mouse button is
clicked
Locked enables
or disables the
ability to move
and resize objects
Locked Property
Or
Variables display
here. Click
Finish
Note You can also attach a variable by entering the variable name in the Property View.
➢ To display constants
The Reconcile Differences dialog box displays constants with both initial and live values.
• For constants when the ToolboxST initial value was checked, that value is either sent to the controller (where the OK
button is clicked), or a pcode record is created, causing the next online download to change both the initial and live
values.
• For constants when the live value was checked, the ToolboxST initial value is set equal to the controller live value. This
causes a minor revision configuration change to Not Equal. A Build and Download to the controller is required to
complete the reconcile function.
➢ To connect to a controller: from the Component Editor Device menu, select Online or click Go On/Offline.
Icons Conditions
All controllers functioning normally:
Controller trip
• Compressing variables
• Changing frame rate
• Changing the background blockware period
• Adding the first I/O pack to a controller
• Changing redundancy type
• Changing the platform type, which changes the number of Ethernets
• Changing any NTP configuration on a controller
Click Go to Secure.
Note When the process is in the Authenticated state, the controller is retrieving a certificate revocation list from the CA
Server to verify that the requestor has a valid certificate.
A controller cannot communicate on a network until these controller setup tasks are
completed.
Attention
Prerequisites
If this is a new UCSB controller received directly from the factory, or a UCSB that has
not been previously configured, the IP address must be set using a USB flash device.
Skip to step b in this procedure.
Attention
i. Enter the device password, then select a COM port and the appropriate controller Channel.
i. Insert a non-encrypted removable USB 2.0–compliant flash device with a 4 GB minimum capacity into the HMI
computer USB port.
ii. Initialize the controller.
iii. Remove the USB flash device from the USB port of the HMI computer, then click Finish.
iv. Remove power from the controller.
v. Insert the USB flash device into the controller. For a UCSB, press and hold in the Backup/Restore button.
Note Refer to the Mark VIe and Mark VIes Control Systems Volume II: General-purpose Applications System
Manual (GEH-6721_Vol_II), the section UCSB Backup and Restore for this procedure.
vi. Apply power to the controller while continuing to press the button until the On LED on the front of the
controller becomes solid green, then release the button. The On LED turns off when the process is complete.
vii. Remove power from the controller, remove the USB flash device, then re-apply power to the controller.
viii. If using redundant controllers, repeat this procedure for the S and T controllers (if TMR) or S (if dual). Be sure
to select the correct Channel.
The user must change the factory default controller password for a device. The
maximum number of characters for the new password is limited to characters. The
new password cannot be the factory default password. If you do not know the factory
default password, contact the nearest GE Sales or Service Office, or an authorized GE
Sales Representative.
Attention For additional details, refer to Mark VIe and Mark VIeS Control Systems Volume II:
General-purpose Applications, GEH-6721_Vol_II, the chapter Controller Diagnostic
Alarms, alarm 547.
Note For a device configured with redundant controllers, the password applies to all controllers in that device.
Note This password is required for configuring the network address during controller setup.
When the password for the replacement controller is successfully synchronized to the other controller passwords in the set, a
message displays in the Log window.
• Boot Loader starts the operating system for the controller much like the BIOS on a desktop computer. Changes to the
boot loader are very infrequent.
Note Not all devices have the boot loader. In this case, the boot loader is contained within the base load.
• Base Load is the operating system for the controller. While changes to the base load are more likely than changes to the
boot loader, they still occur infrequently.
• Firmware provides the controller functionality. It can be updated over the lifetime of the controller to incorporate new
features and bug fixes.
• Application Code contains the configuration of the controller as created in the ToolboxST application. Whenever a
change is made to the configuration, the application code must be downloaded. There are two types of application code
download, online and offline. An online download (very commonly performed) changes the configuration without
interrupting control and the new configuration takes effect between control frames. An offline download requires a
controller restart (performed less frequently).
• Parameters contain specific configuration for the excitation portion of the controller.
Boot loader, base load, firmware, offline application code downloads, and parameter
downloads all require the target device to be restarted. Before downloading new
software to a controller, take the necessary steps to secure the control equipment to
prevent equipment damage and personal injury.
Warning
Note The type of software download needed is determined by which changes have been made to the controller
configuration.
The Download Wizard is used to download software to a static starter control and its associated modules over an Ethernet
connection. The Download Wizard can automatically examine the system configuration to locate out-of-date software, or you
can manually select individual items to download.
Note Certain conditions do not allow a download, such as an incorrect platform type. Check the Component InfoView for
errors that may prohibit a download.
1. From the LS2100e Component Editor Device menu, select Download, and Download Wizard
2. If you have changed configuration settings since the last Build operation, a message box displays indicating that the
software is out of date. Click Yes to build the current configuration.
3. When the welcome wizard displays, click Next.
The APP_STATE block can prohibit a download and restart of the controller.
Attention
If the DOWNLOAD_OK input of the APP_STATE block is set to True, all downloads are allowed. If this value is set to
False, all downloads (except Update DDR and Device Backup) are prohibited. This condition also applies to an attempted
download of an I/O pack from the Hardware tab of the Component Editor. If the download is prohibited, a warning displays in
the Component InfoView, and the Download LS2100e Controller wizard displays the prohibited download. For additional
information, refer to the Mark VIe Controller Standard Block Library Instruction Guide (GEI-100682).
➢ To update the DDR: from the Device menu, select Update Dynamic Data Recorder and follow the instructions
on the ToolboxST windows.
➢ To view and set the controller time: from the Device menu, select View/Set Time... and follow the instructions
on the ToolboxST windows.
From the
View menu,
select
Reconcile
Parameter
Differences
Note From the Component Infoview, you can also double-click the Status tab to display the Reconcile Parameter
Differences dialog box.
➢ To display Controller Diagnostics: from the View menu, select Diagnostics and Controller Diagnostics.
The Controller Advanced Diagnostics View displays additional information from the controller.
➢ To display Advanced Diagnostics: from the View menu, select Diagnostics and Controller Advanced
Diagnostics.
Note Before modifying Totalizer values in a redundant controller, connect to the R controller and make sure all other
redundant controllers are healthy and communicating. (Refer to the section Connect to a Controller.)
Note Totalizer passwords are specific to the connected redundant controller (R, S, or T) and cannot be used on other
controllers.
Note Totalizer passwords are usually valid for 24 hours from time of creation.
2. From the Modify Totalizer Value dialog box, enter the new value and click OK.
➢ To open the Finder: from the toolbar, click the Find icon . Or from the Edit menu, select Find.
Click to display
Enter search text available wildcards
Click Replace
to display a
field to enter
replacement
text
Select Entire
System to
search every
configured
component
Select Open
Components
to search all
components
open in the
System Editor
Select to search
inside the
currently selected
item (in this case,
the Modbus tab)
Select the
search method
from the drop-
down list
Find Methods
The following Find methods are available to control how the text entered in the Find box is matched to text in the ToolboxST
application:
• Anywhere
• Begins With
• Ends With
• Match Exactly
• Match Whole Word
• Wildcards
• Regular Expressions
Anywhere finds the specified text anywhere within a searchable text string.
Anywhere
Begins With finds the specified text only at the beginning of a searchable text string.
Begins With
Ends With finds the specified text only at the end of a searchable text string.
Ends With
A search for: matches: but does not match:
abcde
abc
abdc
abc
ab
xyzabc
bc
Match Exactly finds the specified text only when it is exactly equal to an entire searchable text string.
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.
Wildcards is similar to Match Exactly, except any single letter can substitute for a ? character and any sequence of zero or
more letters can substitute for a * character.
Wildcards
A search for: matches: but does not match:
abdc
bc
abc
a?c abc cde
adc
abcde
xyzabc
abc
adc
abcde bc
a*
abdc cde abc
ab
abc cde
Regular Expressions processes the text entered in the Find box as a regular expression (sometimes abbreviated regex). A
regular expression is an advanced system of wildcards used to match a specific set of text. The ToolboxST configuration
supports a standard set of regular expression commands similar to many popular third-party tools.
Properties display in
the Property Editor
The following table describes the properties displayed in the Property Editor when a Network Adapter item is selected in the
Tree View.
Network Adapter Properties
Property Description
Adapter Settings
Enabled If set to False, disables the selected network adapter. Set to True to enable the network adapter.
Host Name Internet Protocol (IP) host name for the selected network adapter
IP Address IP address for the selected network adapter
Wire Speed Speed of the connected network
Network Settings
Network Name of the connected network
Subnet Mask Subnet mask associated with the connected network
➢ To delete a Produced Page from the Tree View, right-click the page to delete and select Delete.
➢ To configure a Produced Page: from the Tree View, select the EGD tab and expand the Produced Pages.
➢ To compress a single page: from the Tree View, right-click the page to compress and select Compress.
➢ To compress all Produced Pages in a component: from the Tree View, right-click Produced Pages and
select Compress All.
➢ To add a variable to a produced page: from the Tree View, right-click a Produced Page and select Add
Variable to display the Select a Variable window.
➢ To delete a variable from an EGD Page: from the Summary View, right-click the variable to delete and select
Delete Selected Row(s).
➢ To copy variable information from an EGD page to the clipboard: from the Summary View, right-click a
variable and select Copy Selection. The data is copied in .csv format.
Note To edit exchange signatures and configuration time, set the Layout Mode property to Manual. The Layout Mode
property displays when a Produced Page is selected in the Tree View.
The exchange signature is typically managed automatically. The major signature must be incremented when the exchange
content changes in any way other than additions to the end. If you are using the EGD Device Editor to configure EGD for a
device and the device signature changes only when the manufacturer updates the configuration, you may need to manually set
the signature.
3. Review the warning about manual Exchange Signature editing and click OK.
4. Make desired changes and click OK.
➢ To select referenced devices: from the Tree View, right-click Referenced Devices and select Select Devices.
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
select Refresh.
Once connected, the Produced Pages or Referenced Devices option displays the values. Use the Refresh button in the
column header to update the grid.
A CMP can be used to obtain the status of a Class 2 or higher EGD device. When any item from the EGD tab Tree View other
than a Referenced Device is selected, the EGD Statistics from [Device name] tab displays the statistics from the open
component. When Referenced Devices is selected, statistics are obtained from that referenced device, and the name of the tab
page changes accordingly.
Filter Toggle defaults to a filtered state. It displays items that have the same name but have a different Producer ID as
the open component.
Delete deletes the selected item(s). If the item(s) were saved as part of the configuration, they can be added again.
The EGD configuration server uses the producer ID to store all the documents for an EGD node.
If you open two systems, then point to the same configuration server and save a device of the same name with two different
producer IDs to that server, you can end up with two producer ID nodes with the same device name.
Transfer produced data, consumed data, symbols, implementation profiles, and GUI
device EGD configuration files to and from a variety of file formats
File Import and Export
The GE Rationalization report is the only report that can be imported to an external device.
Print the summary grid view with the column selection, order, and width currently visible in
Print
the view
Close Close the currently opened device
Paste Paste the copied item in the Tree View into the Summary View
Go Back Return to the view that immediately preceded the current view in the history
View
Go Forward Go to the view that immediately follows the current view in the history
Send CMP messages to EGD Class 2 or higher devices to view live values from the
Online
device
Refresh the consumed information for all referenced devices, automatically sets the layout
Device Bind and Build of any unassigned produced variables, and, if no errors occur, publishes the configuration
to the EGD configuration server
Store the current EGD configuration to the System Database (SDB). It is only available if
Put Device to SDB
the system has an SDB enabled and configured.
Send Problem
Display the Send Problem Report form to report system issues
Report
Help Release Notes Display the release notes for the current version of the application
Note Perform a Get System from Repository on any computer that has network connectivity to the computer on which
the Repository resides.
• Establishes a security model for the CMS Server. CMS security uses Windows (Domain and/or Workgroup) security for
user authentication (CMS users must exist as valid domain or workgroup users)
• Creates and deletes master locations known as CMS Repositories in which configuration files and revision history are
stored and maintained
• Adds and deletes CMS usernames and privileges to control access to the systems in the repositories
• Provides a mechanism to back up and restore repositories. Backups include revision history for a ToolboxST system in a
Repository. User information can be included or excluded from the backup copy.
• Starts and stops the CMS Server application
If you have upgraded from a previous version of the CMS Server, refer to the section
Upgrade from CMS to CMS – SVN.
Attention
The CMS Server is installed on a single computer and configured for the user’s specific location. Local Administrator
privileges are required to install and configure the CMS Server.
The CMS Server uses a Repository to track system changes and control client access. Each Repository contains a list of CMS
users and access permissions. The Repository maintains the revision change history for the ToolboxST systems that are added
to that Repository. A CMS Server can have one or more repositories, and each Repository can contain one or more
ToolboxST systems.
Note The user must be logged on as an Administrator to install and configure the CMS Server.
Typically, the CMS Server is only installed on one computer per site. When the CMS
Server installation option is selected, a Setup dialog box displays to confirm that the
CMS Server is only being installed on a single computer.
Attention
Note The ControlST software release and version numbers displayed in the Setup dialog box may differ from those
displayed during an actual installation.
1. Place the ControlST Software Suite DVD in the DVD-ROM drive and the installation automatically begins.
2. Review the Setup Notes and click Continue.
3. Install the CMS-SVN Server as follows:
a. Select the check box for CMS-SVN Server.
b. Click Yes to proceed with installation.
c. Click Install.
10. If you do not have a certificate from a CA, create a self-signed certificate.
Note The CMS Administrator Tool is automatically installed during CMS Server installation and a shortcut icon is placed on
the computer desktop. This tool is used to configure the CMS Server, including adding users and setting access permissions.
11. Click Finish to complete CMS Server installation, then click Yes to exit setup, or No to install additional ControlST
software installation options.
Note The Repository username is used by the user to log in to the CMS. The username and password default to your current
Windows username and password.
4. Copy the Repository URL address. (This address is manually entered during initial CMS Client configuration).
Click OK.
Attention
Backup Create a backup copy of the repository for Repository restore
Restore Restore a Repository from a backup copy
Add users and set user permissions
Add
Users with empty passwords cannot access the Repository.
Users
Delete Remove a user from the system
Edit Edit permissions for a user
Start and stop the server
Server
Stopping the server disables all repository operations.
Create Self-signed
Tools Create a server certificate for each client to accept
Certificate
Copy repository URL to the clipboard for use during configuration to connect clients
Copy Repository URL
to the Repository
File Exit Close the CMS Administrator Tool
Note The CMS Administrator Tool can only be accessed from the computer on which the server has been installed and
designated as the CMS Server. Administrator permissions are required on your computer to use the CMS Administrator Tool.
➢ To create a Repository
1. From the Start menu, select All Programs, GE ControlST, CMS Server, and CMS Administrator Tool.
2. Enter a Repository Name and click OK.
The CMS Administrator Tool displays a message notifying the user that the Repository was created successfully.
3. From the Repository drop-down menu, select the Repository to backup. Click Browse and navigate to and select the
location for the backup file, then click OK.
Note A backup copy of the Repository must have been previously created for use to restore the Repository.
4. When the Repository restore has completed successfully, a dialog box displays the location of the backup file used to
restore the Repository. Click OK.
2. From the drop-down menu, select the Repository and click Open.
The restored Repository displays users and permissions in the CMS Administrator window.
Note CMS menu items are disabled until a ToolboxST system is opened.
The CMS Client (in the ToolboxST application) is used to place ToolboxST systems under CMS control, get systems from the
Repository to the local drive, check out individual components in a master configuration, make edits, and check in
components.
The CMS Client provides the following functions:
Note Use the CMS Administrator Tool to assign or remove CMS users to and from the Repository.
The Working Copy is the CMS user’s local copy saved on a particular computer that contains the system .tcw file and all
related files and folders for the system within the CMS Server. A Working Copy is specific to a particular CMS user. Different
users cannot share a Working Copy.
When a user adds a system to the Repository, the current location of the ToolboxST
system .tcw file becomes the local Working Copy on that computer. Place the .tcw file
and configuration files in the desired Working Copy location before adding the
ToolboxST system to the CMS Server.
Attention
To prevent errors during check out and check in, network-shared folders should not
be used as a local Working Copy. Users should maintain the Working Copy on their
hard drive.
Attention
Get System
Add System from Repository
to Repository CMS Server
Get System
From Repository
Computer 1
Computer 3
Computer 2
Attention
1. Open the ToolboxST application system .tcw file.
2. Log in to the CMS Client.
HMI\GeMaint
Note If the user has already saved the certificate this dialog box will not display.
This operation only needs to be performed one time for each computer to get a local
Working Copy of the system on each computer.
Perform a Get System from Repository on any computer that has network connectivity
Attention to the computer on which the Repository resides.
1. From the ToolboxST application, get the system from the CMS Server.
HMI\GeMaint
Note If the user has already saved the certificate this dialog box will not display.
3. Save the Working Copy of the system to a designated location on the computer.
From the drop-down menu, select the system. Enter the folder path or
click Browse and select a location to save the system folder, then click OK.
Note Even if the folder path requires a new folder, the system will automatically create the new folder.
Note You must connect to the correct CMS Server to log on.
HMI\GeMaint
Browse to the local Working Copy and select the .tcw file (system opens in Read-only mode).
Note You must connect to the correct CMS Server to log on.
HMI\GeMaint
Browse to the local Working Copy and select the .tcw file (system opens in Read-only mode).
2. From the CMS Login window, click Cancel.
3. Work disconnected from the CMS Server to make all files writable.
Note It may be useful to perform a Compare... to verify your changes before checking in the component.
28.3.3.4 Refresh
Selecting Refresh updates the CMS status icons for the system and components.
Note CMS status does not update automatically. The user should periodically perform a Refresh to update the CMS status of
all components in the system.
Note You must be connected to the CMS Server for the Refresh feature to work properly.
HMI\GeMaint
The system name displays with a blue lock icon and the system is in Read-Only mode.
Note Components under CMS control will be in Read-Only mode until the component is checked out.
Tip � To check out multiple components at one time, press and hold [Shift] on the keyboard and select the components.
Use the View by Type option in the View menu at the system level to quickly select all Libraries and devices before performing
check in, check out and undo check out.
28.3.3.11 Check In
Selecting Check In checks in the user’s changes to the Repository, and allows other users to get the changes and check out the
system or component.
Tip � To check in multiple components at one time, press and hold [Shift] on the keyboard and select the components.
Use the View by Type option in the View menu at the system level to quickly select all Libraries and devices before performing
check in, check out and undo check out.
Tip � To undo check out of multiple components at one time, press and hold [Shift] on the keyboard and select the
components.
Use the View by Type option in the View menu at the system level to quickly select all Libraries and devices before performing
check in, check out and undo check out.
From the View History window, select a Version and click Get.
The component displays the out of date icon with the revision number.
Note Users can compare the current Working Copy to any previous version displayed in the history, including the latest
version in the Repository. Additionally, users can select and compare two versions displayed in the history.
Attention
Comparison Results
To select two versions, press and hold [Ctrl] on the keyboard and select the
appropriate versions , then click Compare to display comparison results.
Note To delete Library Containers or individual Libraries, right-click the item and select Delete.
To rename a Library Container, right-click the item, select Rename, and enter the new name.
To rename individual Libraries, enter the new name in the Property Editor.
Note CMS status does not update automatically. The user should periodically perform a Refresh to update the CMS status of
all components in the system.
Note You must be connected to the CMS Server for the Refresh feature to work.
3. A dialog box displays and ask if you want to check out all elements.
Tip � If the CMS status icons do not update immediately, click Refresh to update the CMS status icons and view checked out
libraries. You must be connected to the CMS Server for the Refresh feature to work.
A blue padlock icon for the library indicates it has been checked back in to the CMS Repository.
Tip � Use the View by Type option in the View menu at the system level to quickly select all Libraries and devices before
performing check in, check out, and undo check out.
4. Enter a brief description of the changes you made in the Comments field, then click OK.
A blue padlock icon next to the libraries indicate they have been checked back in to the CMS Repository.
➢ To undo checkout: right-click the item and select CMS, select Undo checkout, then click Yes.
The changes you made while the item was checked out will not be saved.
Tip � Use the View by Type option in the View menu at the system level to quickly select all Libraries and devices before
performing check in, check out, and undo check out.
History View
Note If there are no differences identified between the current Working Copy and the most recent copy in the Repository, the
system will display a dialog box to notify the user that there are no differences.
Attention
➢ To compare Library versions
OR
To select two versions, press and hold [Ctrl] on the keyboard and select the
appropriate versions , then click Compare to display comparison results.
➢ To configure the new Repository: add the system to the CMS Server.
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
Auto-Reconfiguration A feature that allows an I/O pack to be replaced and its configuration files downloaded when the
I/O pack is replaced
Baud A unit of data transmission. Baud rate is the number of bits per second transmitted
Bit Binary Digit. The smallest unit of memory used to store only one piece of information with two states, such as
One/Zero or On/Off. Data requiring more than two states, such as numerical values 000 to 999, requires multiple bits (see
Word).
Block Instruction blocks contain basic control functions, which are connected together during configuration to form the
required machine or process control. Blocks can perform math computations, sequencing, or continuous control. The
ToolboxST application receives a description of the blocks from the block libraries.
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.
CMS An application that provides revision control and history for ToolboxST application systems.
Collection A group of signals found on the same network. Trender can be configured by adding collections.
Configure To select settings for such things as the location of hardware jumpers or loading software parameters into
memory.
Control Constant Control Constant is a signal with an initial value that is read and never written.
Designated controller In a Mark VIe dual controller system, the designated controller is the controller to which the I/O
packs listen for outputs when they have the option to listen to multiple controllers. In a TMR system, the designated controller
initializes the other controllers.
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 conform to the IEEE 802.3 standard, developed by Xerox, Digital, and
Intel.
Fault code A message from the controller to the HMI indicating a controller warning or failure.
Fieldbus is a digital, two-way, multi-drop communication link among intelligent measurement and control devices. It
serves as a local area network (LAN) for advanced process control, remote input/output, and high-speed factory automation
applications.
Finder A subsystem of the ToolboxST application for searching and determining the usage of a particular item in a
configuration.
Font One complete collection of letters, punctuation marks, numbers, and special characters with a consistent and
identifiable typeface, weight, posture, and size.
Forcing Setting a variable signal to a particular value, regardless of the value that blockware or I/O is writing to that
signal.
Gateway A device that connects two dissimilar LANs or connects a LAN to a wide-area network (WAN), computer, or
mainframe. A gateway can perform protocol and bandwidth conversion.
A computer that translates another fieldbus-related protocol to FOUNDATION fieldbus protocol, for example, HART® or
Modbus® to FOUNDATION fieldbus protocol.
Heartbeat A signal emitted at regular intervals by software to demonstrate that it is still active.
Hexadecimal (hex) Base 16 numbering system using the digits 0-9 and letters A-F to represent the decimal numbers
0-15. Two hex digits represent 1 byte.
I/O Input/output interfaces that allow the flow of data into and out of a device.
Initialize To set values (addresses, counters, registers, and such) to a beginning value prior to the rest of processing.
Intrinsic variables Pre-defined variables used to display the status of various components and functions
Linking device Provides a standardized communications and control system for installing components from various
manufacturers.
Node In a local network, a component connected to other components that communicates with other network devices. In a
tree structure, a location on the tree that can have links to one or more nodes below it.
Non-volatile The memory specially designed to store information even when the power is off.
Online Online mode provides full CPU communications, allowing data to be both read and written. It is the state of the
ToolboxST application when it is communicating with the system for which it holds the configuration. Also, a download
mode where the device is not stopped and then restarted.
Physical Refers to devices at the electronic or machine level in contrast with logical. Logical implies a higher view than
the physical. Users relate to data logically by data element name; however, the actual fields of data are physically located in
sectors on a disk.
Register page A form of shared memory that is updated over a network. Register pages can be created and instanced in
the controller and posted to the SDB.
Relay Ladder Diagram (RLD) A ladder diagram has a symbolic power source. Power is considered to flow from the left
rail through a contact to the coil connected to the right.
Rubber block A block that can extend to include a variable number of pins.
Secure Sockets Layer (SSL) A cryptographic protocol used to transmit private data over a network.
Sequential Function Chart (SFC) A graphical programming model that allows you to organize an application by
creating a state machine with three types of components: steps, actions, and transitions.
Trender A subsystem of the ToolboxST application that monitors and graphs signal values from a controller.
Validate Makes certain that items or devices do not contain errors and verifies that the configuration is ready to be built
into application code.
Variable The basic unit for variable information. Variables are the placeholders for memory locations in the toolbox’s
different platforms.
Word A unit of information composed of characters, bits, or bytes. It is treated as an entity, and can be stored in one
location. Also, a measurement of memory length, usually 32 bits in length, but can also be 4, 8, or 16 bits long.
WorkstationST A ControlST application that provides a user interface for configuring various features such as alarm
management, control system health, Historians, and data interfaces.
U
T Universal Analog (PUAA) I/O 768
tab unlink
Alarms 1103 permanently 345, 883, 1350, 1490, 1635
Channel Diagnostics 704 property 161
Control System Health 1167 Unlinked Programs / Userblocks Report 469, 962
Device Diagnostics 703 upgrade 1242, 1463, 1611
Diagnostics 797 component 295, 1309
diagrams 1252–1253, 1324 I/O modules 295, 1309
Diagrams 1475, 1623 VME boards 807
Dynamic Data Recorder (DDR) 360, 1361, 1505, Upgrade
1650 component 841
EGD configuration server 374, 895, 1258, 1374, I/O modules 841
1519, 1664 I/O pack firmware 297
Ethernet Global Data 369, 890, 1168, 1370, 1514, upload parameter values 1290
1659 upload wizard 1020
Ethernet Global Data (EGD) 1257 Upload Wizard 1725
general 848, 1246 Use Block
General 1087, 1468, 1616 find all uses 184
GSM 1166 instance 179
hardware 318, 852, 1328 instance script 179
Historian 1166 property editor 185
history 283, 830, 1063, 1231, 1298 validate 179
HMI Config 1121 user block
W
Watch Window
add variable wizard 491, 977, 1206, 1267, 1395,
1543, 1686
export 494, 980, 1209, 1270, 1398, 1547, 1689
open existing 490, 976, 1205, 1266, 1394, 1542,
1685
organize columns 493, 979, 1208, 1269, 1397,
1546, 1688
Web report 398, 914
wizard
add module 854
controller setup 1010
create system 73
creation 827
download 1287
replication 70
upload 1020
Wizard