PAC8000 Workbench Getting Started Guide: GE Intelligent Platforms, Inc. 2500 Austin Drive Charlottesville, VA 22911

PAC8000 Workbench
Getting Started Guide
GE Intelligent Platforms, Inc.

2500 Austin Drive
Charlottesville, VA 22911
www.ge-ip.com
Downloaded from www.Manualslib.com manuals search engine

The information in this manual is subject to change without notice and does not represent a commitment on the
part of GE Intelligent Platforms, Inc. The software described in this manual is furnished under a license or
nondisclosure agreement. This software may be used or copied only in accordance with the terms of this
agreement. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording, for any purpose other than the purchaser's personal use
without the written permission of GE Intelligent Platforms, Inc.
© Copyright 2010 by GE Intelligent Platforms, Inc.

All rights reserved. All brand names and product names are trademarks or registered
trademarks of their respective companies.
SA06-120-111110
The text and screen shots in this document are compatible with Workbench Version 8.4.0 and subsequent releases. If you
are running a previous version, please contact Technical Support.

PAC8000 Workbench Getting Started Guide 3
Contents
Section 1 - Introduction 5
SCOPE .............................................................................................................................. 5
INTENDED READERS .......................................................................................................... 7
ACCESSING ADDITIONAL HELP ........................................................................................... 7
Drawing Templates ..................................................................................................... 7
Help Files..................................................................................................................... 8
Frequently Asked Questions (FAQ) ............................................................................ 9
Training........................................................................................................................ 9
Website...................................................................................................................... 10
Technical Support...................................................................................................... 10
Section 2 – Workbench Software Components 11
WORKBENCH .................................................................................................................. 11
TAG EDITOR .................................................................................................................... 13
8000 IO CONFIGURATOR ................................................................................................ 14
CONTROLLER MODULES .................................................................................................. 15
STRATEGY BUILDER ........................................................................................................ 16
STRATEGY VIEWER ......................................................................................................... 17
DISCRETE CONTROL ........................................................................................................ 18
SIMULATOR ..................................................................................................................... 19
REPORTS ........................................................................................................................ 20
CONTROLLER STATISTICS ................................................................................................ 21
NETWORK CONFIGURATION UTILITY ................................................................................. 22
SECURITY FEATURES ...................................................................................................... 23
Section 3 – Installation 24
PRE-INSTALLATION INFORMATION..................................................................................... 24
INSTALLING THE PAC8000 CONTROL CENTER WORKBENCH ............................................. 26
POST-INSTALLATION ACTIVITIES ....................................................................................... 42
REPAIRING THE INSTALLATION .......................................................................................... 42
Section 4 – Additional Product CD Features 43
ADDITIONAL PROGRAMS .................................................................................................. 43
INFORMATION .................................................................................................................. 46
Section 5 – Licensing 51
Section 6 – Project Tutorial 52
LAUNCHING THE WORKBENCH.......................................................................................... 54
CREATING A PROJECT ..................................................................................................... 55
INITIAL CONTROLLER SET UP ........................................................................................... 57
CONFIGURING IO MODULES ............................................................................................. 69
CREATING AND ASSIGNING PROJECT TAGS....................................................................... 77
GE Intelligent Platforms, Inc. September 2010

4 PAC8000 Workbench Getting Started Guide
WORKING WITH PROCESS CONTROL STRATEGIES ............................................................. 85
Creating a Process Control Strategy......................................................................... 85
Downloading to the Process Simulator ..................................................................... 89
Downloading to the Controller ................................................................................... 91
Process Control Strategy Checkout .......................................................................... 93
WORKING WITH DISCRETE CONTROL STRATEGIES ............................................................ 94
Creating a Discrete Control Strategy......................................................................... 94
Downloading to the Logic Simulator........................................................................ 106
Downloading to the Controller ................................................................................. 108
Discrete Control Strategy Checkout ........................................................................ 110
RETRIEVING DATA FROM OTHER 8000 CONTROLLERS .................................................... 112
MAPPING POINTS FROM REMOTE MODBUS DEVICES ....................................................... 119
LINKING TO INTOUCH ..................................................................................................... 122
Connecting to DesignerSim..................................................................................... 122
Connecting to the Universal IO Server.................................................................... 126
IMPORTING TAGS INTO HMIS ......................................................................................... 130
Importing Tags into Cimplicity ................................................................................. 130
Importing Tags into iFIX .......................................................................................... 130
Importing Tags into Wonderware ............................................................................ 130
ADDITIONAL INFORMATION ............................................................................................. 132
Glossary 133

Section 1 - Introduction
The PAC8000 Control System provides a fully integrated, open solution for process
control, discrete automation, strategy development, and process visualization. The
process engineer is supplied with the tools to design, implement, document, and maintain
a process control system using advanced control strategies or the IEC 61131-3
programming languages.
The PAC8000 Control System consists of a number of open system components,
including:
Workbench - an integrated project development environment that centralizes
and coordinates project engineering, including instrument index, control
strategies (process and discrete), process visualization, (operating faceplates),
history (alarming and trending), and project management.
HMI - components for the PAC8000 Operator Interface (HMI), plant historian,
and batch recipe management.
Control Platform - a rugged, field-mountable system consisting of the controller
and the 8000 Process IO system.
The Workbench is an integrated engineering environment, which automatically configures
the operator interface and historian. Due to the open nature of the system, other
components that make use of industry standards such as Modbus, OPC, Ethernet, and
HART can be easily integrated.
Note: PAC8000 Open Control components can be used with any HMI software that
communicates via Modbus or OPC.
Scope
The intent of this Getting Started Guide is to provide assistance in building your first
application using the PAC8000 Workbench; it is not intended to replace any of the
available training courses. However, working through these procedures leads to a greater
understanding of the Workbench, thereby enhancing the lessons in the training class. It is
also assumed that readers have a basic understanding of Microsoft Windows and the
features of their operating system. The Workbench system components are described,

the product installation procedure is explained, the licensing and registration process is
discussed, and a full project tutorial is provided. The installation process assumes that
you are installing the product for the first time. If you are upgrading an existing
installation, please refer to the Upgrade Instructions that were shipped with your
product CD.
This is not a hardware manual and no attempt is made to explain the details of the
hardware components of the system. For additional installation information, please refer
to:
• 8000 Controllers Hybrid, Process, Logic, & EBIM Instruction Manual Document
number: INM8521
• 8000 – 2/x I/O modules Instruction Manual (General Purpose and 2/2
Applications)
Document number: INM8100
• 8000 – 2/x I/O modules Instruction Manual (2/1 Applications) Document number:
INM8200
• 8000 – 2/x Power Supplies – Configurations and Installation Document number:
INM8900
An HMI is an integral part of any control system. While some aspects of Wonderware’s
InTouch are described in this guide, any HMI that can communicate via OPC, Modbus
RTU, or Modbus TCP can be used with the control system. For detailed HMI information,
please refer to the documentation provided by your HMI vendor.

Intended Readers
This Getting Started Guide is intended for those users who are:
• Installing the PAC8000 Workbench for the first time.
• Upgrading an existing application of the PAC8000 Workbench.
• Learning how to use the PAC8000 Workbench.
• Currently using the PAC8000 Workbench, but wish to expand their knowledge in
key areas, such as the IEC 61131-3 programming language.
Accessing Additional Help

In addition to the Project Tutorial provided in this guide, there are various documents and
help files to assist in the successful operation of the PAC8000 Workbench. Some
examples are identified in this section.
Drawing Templates
Programming elements, such as basic PID loops, cascaded PID loops, adaptive
tuning PID loops, motor control functions, and time pulse controllers are frequently
used to implement control strategies. A set of template drawings is delivered and
installed with the system so that each customer will not have to build these common
elements.
When creating a drawing, you will notice a From Template option. Select this option
to display the system’s available templates. Once the appropriate template is chosen,
the new drawing is created using the blocks in this template. (You then have to
renumber the blocks so that they are appropriate for your project. The tag names
used in the template also need to be replaced with tag names that are appropriate for
your project.)
A detailed description of each template, as well as the blocks used, can be found in
the PAC8000 Workbench Help. To access Help, open the PAC8000 Workbench and
select the Help | Contents menu item. Pre-defined templates are listed in the
Templates | Available Templates section. Select the template for which you would
like additional information. You are presented with a description of the template
detailing the blocks used, as well as the template drawing.

Help Files
Application Help
A full set of Help files is delivered and installed with the system. From any
application, (PAC8000 Workbench, Network Configurator, etc.) you may select Help
from the pull down Help menu item, click the Help option, if one is present on the
form, or press the F1 key on the keyboard to view the Help. Each Help file has a
detailed index, table of contents, and search function to expedite locating additional
information for a particular topic.
Function Block Manual
Detailed Help is also available for each function block in the Strategy Builder. Double-
click on a function block in Edit mode to access the Block Attributes dialog. Click
Help to display the Help for the block, including a description of the block, block
attributes, input parameters, and output parameters.
If this is your first time using the PAC8000 product, it is very likely that you are not
familiar with the blocks included in the Workbench. Though blocks may have similar
names among different products, each product implements blocks in a unique way.
To clarify the implementation of the PAC8000 product function blocks, a user’s
manual is installed in the product’s Documentation directory:
<installation_directory>\Documentation\Function Blocks Document.pdf
This document lists each available function block and a brief description of the
block’s function. From this high-level description, you can determine the correct block
to use and then access the function block online Help to understand the block’s
attributes, as well as its input and output parameters.
Workbench Wizards Manual
This manual lists the Wizards included with the PAC8000 Workbench that allow you
to quickly produce graphics in Wonderware’s InTouch. This manual is located at the
following path: <installation_directory\Documentation\Workbench Wizards.pdf

Frequently Asked Questions (FAQ)

In addition to the online Help, the Workbench also contains a Frequently Asked
Questions section. From the PAC8000 Workbench, select the Help | Frequently
Asked Questions menu item; a list of commonly asked questions and their answers
is displayed.
In addition to the documentation provided within the product, various services are also
available to assist in accessing help. These services are described below.
Training
In the Americas:
PAC8000 offers three distinct training programs with formalized, instructor-led,
hands-on training to familiarize customers with the systems they have purchased.
• Core Components Training - This four-day class is designed to give students
the necessary skills to engineer, configure, and maintain a PAC8000 system.
Students create several projects during the class, allowing them to work
through the complete project development cycle multiple times during the class
(project configuration, tag creation, IO module configuration, control strategy
development, downloading, and debugging).
• Maintenance Training - This one-day class is designed to give students the
necessary skills to maintain and troubleshoot all areas of a PAC8000 system,
including hardware and control strategies.
• SafetyNet Workbench Training - This three-day class is designed to teach
students the skills necessary to configure, program, analyze, and troubleshoot
a safety system strategy. This class is not a class in functional safety, but how
to use our system, which is certified for use in an SIL2 application.
• On-site Training - In addition to the above training courses, on-site training is
also available, as needed. This allows the course to be customized for your
application needs.

Website
The Website (www.ge-ip.com/support) contains links to data sheets and other
information that can help you find solutions to potential issues when building and
commissioning your control system.
Technical Support
Europe, the Middle East, and Africa (EMEA)
Online Technical Support: www.ge-ip.com/support
Phone: +800-1-433-2682
Technical Support Email: [email protected]
Customer Care Email: [email protected]
Primary languages of support: English, French, German, Italian, Czech
Support in the Americas (Americas)
Online Technical Support: www.ge-ip.com/support
Phone: 800-433-2682
Technical support email: [email protected]
Customer care email: [email protected]
Primary Languages of support: English

Section 2 – Workbench Software Components
This section provides a high-level view of the PAC8000 Workbench software

components. Further details for each software component can be found in the Project
Tutorial section of this guide or the Workbench online Help.
This section of the guide is intended for those users who are:
• Installing the product for the first time
• Interested in a broad overview of the product
The PAC8000 Workbench software includes the following system components:
Workbench
The PAC8000 Workbench provides the foundation for defining a project and all of its
components: tags, hardware configuration, tables, and control logic. The Workbench,
with components indicated, appears as follows:

The Workbench consists of two main sections – the Project Explorer and the Data
Entry Panel.
The Project Explorer, located in the left-hand pane of the Workbench, provides
assistance with adding controllers, drawings, tags, modules, etc. You will browse the
Project Explorer tree to configure projects and controllers, as necessary.
Projects are defined using the menu items displayed when the Project Explorer is active.
Once created and defined, projects are displayed in the Project Explorer with three
nodes: Project Tag Index, Project Reports, and Launch Network Configurator.
After creating a project, project tags are defined through the Project Tag Index. A
project tag is a name that refers to a channel on a physical IO card. As each tag is
created, it is saved in a database allowing for subsequent data retrieval through the
report manager.
Controllers are the next project component to be added and configured. Controllers are
abstractions of the physical hardware. Once a controller is created, the following nodes
appear beneath the controller node in the Project Explorer: Controller Modules,
Controller Reports, Controller Statistics, Launch 8000 IO Configurator, and
Create/Edit Discrete Control Interface. Control Strategy Drawings are also displayed
in the controller node once they have been created.
Each controller contains zero or more IO modules to which physical devices, such as
transmitters and valves, are connected. The physical hardware is configured using the
8000 IO Configurator. Project tags that were created earlier are then linked to channels
of the IO modules.
Control logic can now be written. Process control logic is written using the Strategy
Builder and IEC 61131-3 logic is written using the Discrete Control Interface. The
Discrete Control Interface enables you to download compiled logic to a simulator.
Downloading to the simulator allows logic to be checked out before it is downloaded to
the controller. (The PAC8000 Workbench allows for downloads to the controller.)
Regardless of the download type, both the Strategy Builder and the IEC 61131-3 logic
editor support real time viewing so that logic can be viewed with data to assist in
troubleshooting.
Network information and controller diagnostic information can be viewed in either the
Network Configurator or Controller Statistics.
The Data Entry Panel occupies the right-hand pane of the Workbench. As specific tasks
are selected in the Project Explorer, the Data Entry Panel changes to facilitate data entry.
Each panel is specifically designed to provide intuitive and consistent data entry fields.

Tag Editor
Project tags are names and attributes assigned to channels on IO modules. These tags
are created through the Tag Editor. In addition to collecting the basic data for the tag (via
the IO Definition tab), information required to populate the HMI database, such as alarm
limits, can also be specified (via the HMI tab). If a complete instrument index is needed,
specific information for the instrument, such as transmitter manufacturer, can also be
entered (via the Manufacturer tab).
The Tag Editor has two views: single tag and multi-tag display. When multi-tag display is
selected, all tags are displayed in a spreadsheet format. This mode is useful when
making changes that affect multiple tags.
The Tag Editor also supports searching for tags based on one or more criteria. Tags
matching the search criteria are displayed in Project Explorer under the Project Tag Index
node.
For more information regarding tag definition, please refer to the Creating Project Tags
section in the online Help. If you wish to gain experience in defining tags, see the
Creating and Assigning Project Tags section in the Project Tutorial of this guide or refer
to the labs in the Modules section of the PAC8000 Workbench Core Components
Training Guide.

8000 IO Configurator
The 8000 IO Configurator is launched to configure the system hardware (controllers and
IO modules) when a controller is added to the project or the Launch 80000 IO
Configurator node is double-clicked (for existing controllers). When the controller node
( ) is selected, the network attributes of the controller can be specified and IO modules
can be added or deleted. Once a module is added, the specific attributes for each module
can then be configured. Once the required data for the controller and each IO module is
entered, the configuration data is downloaded to the controller using this utility.
For more information regarding the 8000 IO Configurator, please refer to the IO
Configurator Training Guide located in the documentation directory
(<installation_directory>\Documentation\IO Configurator Training Guide.pdf) or the
IO Configurator online Help (<installation_directory>Documentation\IOConfig.chm).

Controller Modules
Project tags are associated with IO module channels in the Controller Modules form.
When a Spare channel is selected, a drop down list appears and all tags of the
appropriate IO type that have not been assigned to another IO module channel are
displayed. Select the tag and click Apply to assign the tag to the channel.
You may also choose to create new tags from this screen by selecting the New Tag
option from the Tagname drop down list. This allows new tags to be created without
exiting the Assign Points form.
For more information regarding Controller Modules, please refer to the Assigning
Modules to Controllers section in the online Help or the Creating and Assigning Project
Tags, or Configuring IO Modules sections in the Project Tutorial of this Getting Started
Guide.

Strategy Builder
Process control logic diagrams are developed using the Strategy Builder. Select the
appropriate function blocks, assign symbolic tags, and then connect the blocks with
analog or digital lines to create the control strategy. Function blocks and connectors are
selected from the right hand pane and placed on the drawing using the drag and drop
method.
For more information regarding the available function blocks in the PAC8000 product,
please refer to the Function Block manual. For more information regarding the function
block editor, please refer to the Creating a Drawing Strategy section in the online Help,
the Working with Process Control Strategies section in the Project Tutorial of this guide,
or the labs in the Strategy Builder section of the Process Control Training Guide.

Strategy Viewer
The Strategy Viewer facilitates the animation of logic diagrams with either simulated or
live real time process data. The Strategy Viewer is also used for tuning and operator
control purposes. Module and IO diagnostic tags are provided for troubleshooting
assistance via the operator interface, allowing logic to be debugged quickly and
effectively.
For more information regarding the Strategy Viewer, please refer to the Viewing Live
Data section in the online Help, the Process Control Strategy Checkout section in the
Project Tutorial, or the labs in the Viewing Live Data section of the Process Control
Training Guide.

Discrete Control
The Discrete Control Interface is used for IEC 61131-3 Programming. Once launched,
programs, functions, and function blocks are built in any of the IEC languages: Ladder
Diagram, Structured Text, Instruction List, Function Block Diagram, Sequential Function
Chart, and/or Flow Chart. Any mix of languages can be used, allowing you to choose the
language that is appropriate for your application.
For more information regarding Discrete Control, please refer to the online Help that is
accessible in the Discrete Control Interface (select the Help | Contents menu item within
the Discrete Control Interface), the Working with Discrete Control Strategies section in
the Project Tutorial, or the Using InTouch Technical Note.

Simulator
The Simulator (DesignerSim) enables the control system designer to test process control
strategies in a single controller without the need of physical hardware or any additional
code. It can also be used to train operators and maintenance personnel. Instead of
loading the control strategy configuration file into the controller, the file is loaded into the
Simulator for debugging and testing. The Simulator operates as a controller,
communicating with the operator interface and batch scheduling engine, as well as the
Workbench.
For more information regarding the Simulator, please refer to the Simulator section in
the online Help, the Downloading to the Process Simulator section in the Project
Tutorial, or the Downloading a Strategy to a Simulator section in the Process Control
Training Guide.

Reports
All project data is saved in a SQL Server database. Since this is a standard Microsoft
database used by many other products, it is simple to create queries and reports for data
presentation. The Reports feature contains a number of predefined reports at the project
and controller level that aid in producing project documentation. If preferred, you may
also create your own custom reports.
Once the form is launched, select the appropriate report from the drop down list and click
Run Report. The relevant data is retrieved and presented. Once the report has been run,
it can be saved, printed, or emailed.
The Workbench provides support for Standard and Custom reports. Standard reports
are shipped with the product and pertain to either a project or a controller. Custom
reports are user-created, enabling you to customize the output to fit your documentation
needs. Standard reports include tags assigned to controller modules, all tags and their
corresponding addresses, and tags and where they are used. Standard reports can be
tailored to meet your needs and you can also write your own reports.
For more information regarding Reports, please refer to the Reports section in the online
Help or the Reports section in the Workbench Core Components Training Guide.

Controller Statistics
The Controller Statistics feature displays scan time breakdown, system parameters, and
event logs. To access the Controller Statistics screen, expand the controller node In the
Project Explorer and double-click to display the screen below.
The top portion of the Statistics tab shows the breakdown of the controller scan time so
that the most time consuming portion of the execution cycle can be determined. Other
diagnostic data is also displayed, including the number of controller failovers, refreshes,
and warm starts. The bottom portion of the screen shows the controller event log. The
event log shows the last 512 events that have occurred in the controller. Such events can
be triggered by channel failures, module failures, downloads, etc.
The System Parameters, Control Package Params, Comm Stats, and
Module/Channel Health tabs contain parameters that relate to execution and timeouts.
These parameters do not normally need to be changed. If you feel it is necessary to
make changes to any of these settings, please contact Technical Support before doing
so, as unexpected results may occur.
For more information regarding Controller Statistics, please refer to the Controller
Statistics section in the online Help.

Network Configuration Utility
The Network Configuration Utility is a network management tool that is used to assign IP
addresses to unconfigured controllers and show network information for all controllers on
a process network. When the utility is launched, the network is queried for all controllers
and those found are presented, as shown below. Double-click a controller name to
access detailed network information and send commands to the controller.
For more information regarding the Network Configurator, please refer to the Network
Configuration section in the online Help, the section on Initial Controller Setup in the
Project Tutorial, or Network Configuration lab in the Workbench Core Components
Training Guide.

Security Features
Since the PAC8000 system is used to monitor and control potentially dangerous
processes, it is important to prevent unauthorized changes to the data and programs
running in the controller. The PAC8000 Workbench provides the following security
features:
Security Privileges - Each Workbench user has a user id and password with which to
logon. This logon indicates the types of changes that are permitted, as well as which
data can be accessed and modified.
Trusted Hosts Table - The Trusted Hosts Table prevents unauthorized devices
(computers, COM ports, etc.) from making changes to data in the controller. Each
device that is permitted to make data changes must have its MAC address listed in
the controller’s Trusted Hosts Table. This feature is only available for a controller with
Version 2 Firmware.
Keyswitch - The keyswitch is a digital input that can be used to “lock” the controller.
When the controller is “locked” no writes, configuration changes, strategy changes,
etc., can be made to the controller. When “unlocked,” data can be changed as long
as the correct privileges have been assigned in the Trusted Hosts Table. This feature
is only available for a controller with Version 2 Firmware.
Controller Password - For additional security, the controller can be given a password,
which must be entered before the Trusted Hosts Table can be downloaded or the
Mode can be changed. This feature is only available for a controller with Version 2
Firmware.
Configuration Mode and Protected Mode - In Configuration Mode, changes can be
made to the data in the controller as long you are authorized to make the change
(based on the security level of the login and the access granted to the computer by
the Trusted Hosts Table) and the keyswitch is unlocked. In Protected mode, changes
are only permitted to the mode, i.e. changes from Protected mode back to
configuration mode, and to the Trusted Hosts Table, as allowed by the keyswitch
setting. This feature is only available for a controller with Version 2 Firmware.
Change Log - Change tracking can be enabled for a controller. You can then run a
report to view the changes that have been made. Each change gives a description of
the change made, the logon id of the user making the change, and the date and time
the change was made.
Difference Tools - When a strategy is downloaded to the controller, a backup of the
project is automatically made if this option is selected. The Workbench provides a
File Differences Utility that allows you to see the changes made between versions.

Section 3 – Installation
This section describes the process of installing the PAC8000 Workbench. If the PAC8000
Workbench is already installed on your computer and you need to upgrade your
installation, please refer to the Update Instructions that were shipped with your CD.
Pre-Installation Information
Before installing the PAC8000 Workbench, please ensure the following:
• The drive where the PAC8000 Workbench will be installed has been identified.
• You have administrative privileges on the machine. If you do not, the installation
procedure will fail.
• The proper operating system is installed. The PAC8000 Workbench can only be
installed on Windows 2000 SP4 (or later) or Windows XP SP1 (or later). Earlier
versions of these operating systems or operating systems not mentioned will
cause the installation to end with an error.
• Your PC hardware meets the hardware requirements of the software. You
computer must be a Pentium III 700 or greater with at least 125 MB of RAM and
680 MB of free hard drive space. If you intend to install the PAC8000 Workbench
on a drive other than the operating system root, you must still have at least 540
MB of disk space available on the drive where the operating system is installed.
In addition, you must have at least 135 MB of disk space available on the drive
on which the PAC8000 Workbench is installed.
• Virus protection software has been disabled. If it has not, errors may occur during
the installation or the installation may take longer than expected. As soon as the
installation completes, you may re-enable the virus protection software.
• All processes associated with the PAC8000 Workbench or the Universal IO
server have been stopped. If they have not, you are prompted to stop them
during the installation process.
Note: If Wonderware’s InTouch is your HMI, it must be installed before you install
the PAC8000 Workbench. This is necessary because the Universal IO Server,
which is installed along with the PAC8000 Workbench, requires InTouch’s
common components in order to properly install SuiteLink.

During the installation of the PAC8000 Workbench, other components are installed.
These components include:
• Universal IO Server Limited Edition - In order to communicate with the
controller, the Workbench requires a Modbus TCP driver. The Universal IO
Server is installed for this purpose.
• .NET Framework - Some of the PAC8000 Workbench components are built
using .NET technology. In order to take advantage of these components, the
.NET Framework is required.
• MSDE - The Microsoft Desktop Engine allows the PAC8000 Workbench to
access MS-SQL type databases. If you already have a later version of MSDE or
another compatible MS-SQL database driver installed, this component will not be
installed.
• Sequence of Events - Sequence of Events (SOE) data gives an accurate time
for event occurrence, along with the event value and other useful information.
This data can then be used to help determine a specific order of occurrences or
"Sequence of Events." There are two different kinds of events that can be
recorded: data change events from SOE modules based on channel inputs or
data change events from analog or digital registers found in the controller. Data
change events can be recorded no faster than the cycle time of the controller
while SOE module events are recorded in accord with times in the module’s data
sheet (order of milliseconds).

Installing the PAC8000 Control Center Workbench

1. Insert the product CD into the appropriate drive.
2. The PAC8000 Product Installation window appears. Click Next Page.

3. The Options screen appears. Select the PAC8000 Control Center option and click
Go.
Note: The text and screen shots in this document are compatible with PAC8000
Workbench Version 8.4.0 and subsequent releases. Version x.x.x on the screen shots
refers to the current version number of the product that is being installed.

4. If Microsoft .NET Framework Version 1.1 SP1 is not installed on your computer,
the following dialog appears while this version is installed. Proceed to the next step to
continue.
If you already have the current version of Microsoft .NET Framework, skip to step 6
in this section.
5. You are prompted to restart your computer. Click Restart on the following screen and
the installation will automatically resume upon startup.

6. The Windows Installer screen appears.
Note: If a standalone version of Sequence of Events (SOE) is installed on this

computer, the following error occurs. Remove the existing version of SOE via the
Control Panel. Once SOE has been removed, begin the Workbench installation again
and an upgraded version of SOE will automatically be installed.

7. The Welcome to the InstallShield Wizard for PAC8000 Control Center screen
appears. This screen may be visible for several minutes while the InstallShield
Wizard is being prepared. If a previous installation of the Workbench exists on this
computer, you may notice a reference to the current application.

8. If a Workbench-related service or program is currently running, the Test State of

Listed Services/Programs screen appears. A checkmark indicates which
services/programs are running. Click Terminate Running Services/Programs to
stop the services/programs. It may be necessary to click this button more than once
to stop all occurrences. Be sure to scroll through the entire list to view all programs.
When all services/programs have stopped, the option to Continue is enabled. Click
Continue to proceed with the installation. You may also click Cancel to prematurely
exit the installation and manually stop the services/programs from running if they
cannot be stopped from this screen. If Cancel is selected, an error message is
displayed to report that the installation cannot continue. Manually stop the running
services/programs and restart the installation process.

9. The Welcome screen appears. Click Next to continue.
10. The License Agreement screen appears. Review the License Agreement and select
the I accept the terms in the license agreement option. Click Next to continue.

11. If the PAC8000 Workbench has already been installed on this computer, the
PAC8000 Control Center Database screen appears. (Otherwise, proceed to the
next step.) This screen prompts for the PAC8000 Workbench User Name and
Password, as they may have been changed from the default sa and ocpcc2003. The
fields on this screen retain the default values so you only need to click Next to
proceed.
Note: If incorrect values are entered, a message is displayed informing you to

attach the databases using the Database Maintenance Utility. You may do so
once the installation is complete. (You must have administrative privileges.)

12. The Setup Type screen appears. Select the appropriate installation type.
Complete - To install the Workbench to the C drive, select the Complete option and
click Next to continue. Proceed to the next step.
Custom - To install the Workbench to a location other than the C drive, select the
Custom option and click Next. Proceed to step a, below.

a. The Custom Setup screen appears; click Change.
b. Select the desired location for installation from the Change Current
Destination Folder screen and click OK.

c. The Custom Setup screen appears again. Click Next to continue with the
installation.
Note: This procedure only installs the PAC8000 software on the selected
drive. Other files are installed to Program Files on the drive where the
operating system is installed. As indicated earlier, 680 MB of disk space is
required for the complete installation. However, when an alternate drive is
selected, 135 MB is required on the selected drive and 540 MB is required
on the drive where the operating system is installed.

13. The Ready to Install the Program screen appears. Click Install.
14. The Installing status screen appears.

15. The M4 Common Licensing screen appears.
16. The Microsoft SQL Server (OCPCC Instance) installs if it is not currently installed
on your machine. Otherwise, skip to the next step.
17. The Universal IO Server (Limited Edition) installer screen appears.

18. The Preparing to Install Universal IO Server (Limited Edition) screen appears
briefly. If it is necessary to upgrade your current version or if you do not already have
the Universal Server installed, a limited edition of this program is automatically
installed. If you already have the current version, skip to step 21 in this section.
19. The Welcome to the InstallShield Wizard for the Universal IO Server (Limited
Edition) screen appears briefly.

20. The Installing Universal IO Server (Limited Edition) screen appears. A progress
bar indicates the status of the installation.
21. Once the Universal IO Server installation is complete, the Installing PAC8000
Control Center status screen reappears. A progress bar indicates the status of the
installation. Please be patient, as this installation may take several minutes.

22. When the installation is complete, the PAC8000 Control Center InstallShield
Wizard Completed screen appears. Click Finish.
23. You may be prompted to restart your computer to enact configuration changes. If so,
you must do so before attempting to run the Workbench.
Note: If you are not prompted to restart your computer, it is considered good
Windows operating system practice to do so at this point.
24. The Installation process is now complete.

Post-Installation Activities
Once the installation process has finished, you may add accounts to the Universal IO
Server. The Universal IO Server is configured so that only the user who installed the
software can add and communicate with devices. If other users require this ability,
appropriate user accounts should be added in the Universal IO Server. For information
on adding these accounts, please refer to the Security Accounts section in the
Universal Server Getting Started Guide.
Repairing the Installation

The PAC8000 Workbench is shipped with a set of Dynamic Link Libraries (dll) and
Executable files (exe). There may be times when installing another program changes the
version of a dll or exe file. When this happens, the PAC8000 Workbench may no longer
function correctly. To fix any problems caused by installing other programs, go to Add or
Remove Programs within Control Panel, select PAC8000 Control Center, and click
Change.
Complete the ensuing process to repair your installation of the PAC8000 Workbench.

Section 4 – Additional Product CD Features
The Product Installation CD installs and accesses items that can be used to supplement
the Workbench. Such items include Communication and Maintenance Tools as well as
Product and Contact Information.
Additional Programs
The Additional Programs feature on the Product Installation CD allows you to install
optional programs. These programs can be used to access Sequence of Events (SOE)
data in the controller, install the limited edition Universal IO Server, or run a support
program, if instructed to do so by Technical Support.
Select the Additional Programs option from the Options screen and click Go to install
additional Tools and Maintenance Programs.

Tools
Additional tools may be installed to assist in communicating with other devices, such
as retrieving the order in which certain IO events occurred and communicating with
other devices via Modbus and/or OPC.
• Sequence of Events – Install this application if you are using a Discrete Input
Module with SOE capability or you are using the Event Recording Feature in
the controller. Please refer to the Sequence of Events Getting Started Guide
for installation information.
• IAS Object Manager – Install this application if you are using Industrial
Application Server from Invensys Wonderware and you would like the
Workbench to automatically generate objects. Please refer to the IAS Object
Manager Getting Started Guide for installation information.
• 8000 IO Configurator (Standalone Version) – The 8000 IO Configurator is

installed as part of the PAC8000 Workbench. Install this standalone version if
you would like to configure IO on a machine, but do not require the additional
functionality of the Workbench. Please refer to the IO Configurator Getting
Started Guide for installation information.
• AXE Comm Stats (Standalone Version) – AXE Comm Stats is installed as

part of the PAC8000 Workbench. Install this standalone version if you need to
perform network troubleshooting on a machine where other Workbench
functionality is not required. Please refer to the AXE Comm Stats Online
Help for additional information.
• Universal IO Server (Limited Edition) – A limited edition of the server is
installed with the PAC8000 Workbench; this version is only authorized to
communicate with PAC8000 Controllers. Install the full version if you are
authorized to communicate with other device types. Please refer to the
Universal Server Getting Started Guide for installation information.
• Engineering Library – Install this application if you want to install a set of DXF
files that can be used to create panel drawings or other drawings to show the
layout and dimensions of the PAC8000 Hardware.
• Communication DTM – Installs Communication DTM for 8000 controllers.

Maintenance Programs
Support Programs may be installed to repair components that were damaged by the
installation of another application. Select this option and click Go for a list of available
programs.
Warning: Do not attempt to run any of the Maintenance Support Programs without
instruction from technical support.

Information
Select Information from the Options screen and click Go.

The Information screen displays the available options for obtaining additional
information concerning the PAC8000 product and GE.

a. Select the Contact Us option and click Go to display contact information for GE.
Note: It is not necessary to use this screen when contact information is needed,
as company information is also available on the website (www.ge-ip.com) and
the Help | About menu item within the PAC8000 Workbench.

b. The Documentation option invokes the Documentation screen. Select a product

and click Go to view the corresponding manual.

c. The CD Browser option allows you to view the contents of the Installation CD in an
Explorer Window.

Section 5 – Licensing
The license procedure is detailed in the Proficy Common Licensing Help. This file is
located in Start | Programs | Proficy Common | License Documentation.
To run the license viewer, select Start | Programs | Proficy Common | License Viewer.

Section 6 – Project Tutorial
The PAC8000 Workbench is the single engineering environment used to configure

Ethernet BIMs, as well as configure and program Hybrid, Process, and Logic controllers.
The Project Tutorial walks through the steps that are necessary to program a simple
control strategy for a Hybrid controller. If you have another type of controller, not all steps
apply to your project. Each section denotes the controller type to which the instructions
apply.
This project tutorial provides instruction for creating tags, configuring IO modules,
assigning tags to the modules, creating a simple Process control strategy, creating a
simple discrete control strategy, downloading the strategies to both the simulator and the
controller, and viewing the data online. At the end of the tutorial, you will have experience
with each of the tools in the PAC8000 Workbench and have a rudimentary knowledge of
how they are used.
This tutorial assumes that you have a new controller or set of controllers and IO modules.
Feel free to substitute the modules that you have for those used in the tutorial. If you do
not have hardware, skip the steps that require hardware interaction.
New controllers are shipped from the factory in BOOTP mode, meaning they are
assigned MAC addresses, but not IP addresses. When the controller is in this
configuration, the Healthy, Fault, and Failsafe LEDs flash in unison. If you are using
existing controllers and intend to follow all of the steps in this tutorial, put the controllers
into BOOTP mode. To do this, hold down the change state button next to the controller,
power cycle the controller and continue to hold down the button until the Healthy, Fault,
and Failsafe LEDs flash in unison.
Setting up controller hardware requires three distinct IP addresses that are located on the
same subnet. Before setting up the controller with these IP addresses, ensure that your
PC has a compatible address, i.e. it is on the same subnet as the controllers.
There are a number of steps to follow when developing a project that results in a defined
and tested application. The following diagram provides a pictorial overview of the steps
that are discussed in this project tutorial.


Launching the Workbench

1. Once the software has been installed, start the PAC8000 Workbench by selecting
the Workbench application from the Start menu.
2. The Connect to Database form is displayed requesting that you log on.
3. Enter Nodename\ocpcc into the Server Name field. (The Nodename is the name
of the computer.) The default Username is sa and the password is ocpcc2003.
Logging on as such grants you full access to all features in the PAC8000
Workbench. It is possible to create your own users with specific passwords and
access levels. For more information, please refer to the Workbench | Workbench
Components Overview | Project Explorer Menu topic in the online Help. Then
select the links Administrative Tools | Administer Users.
Note: The Workbench defaults to the last username that was used to log on. If
this is the first time connecting to the database, the default username is sa.

Creating a Project
Applies to: All Controllers
1. Click in the Workbench Project Explorer and the Create new project form appears
if there are no other projects configured. If this is not your first project, select the
File | New Project menu item. The Create new project form appears.

2. Enter a name for the project in the Project Name field; for our example, use the
project name MyFirstProject. The project name can be up to twenty characters in
length and must not contain spaces. Ensure that the desired location is selected,
and click Apply. The project is added to the Project Explorer and the Workbench
appears as follows:

Initial Controller Set Up

1. In the Workbench Project Explorer, right-click the project name and click New
Controller from the resulting menu. The Create new controller form appears.
2. Enter a name for the controller in the Controller Name field; use the name Ctrl1
for our example. The controller name can be up to sixteen characters in length and
must not contain spaces.
3. Select Model 8521 from the Controller Type drop down list. Model 8521 is the
basic controller type. Model 8851 (SafetyNet) is certified for use in SIL2
applications. In this case, Controller Type indicates the register allocation scheme,
not the type of controller being used. The Model 8521 controller types apply to
Hybrid, Process, and Logic controllers, as well as Ethernet BIMs. Select Hybrid for
our example.
4. Select the External Power option and enter the number 5 in the resulting box to
indicate that 5 amps of external power are available to power IO modules. As
modules are added, power requirements are subtracted from this amount and the
amount remaining is displayed on the Controller Modules form.

5. Select the Version 2 Firmware option if you will be downloading your project to a
controller that has Version 2.00 or higher of the Firmware. Doing so allows you to
take advantage of the features that were not available in previous versions of the
controller. Version 2 features include: Retained Variables, Trusted Hosts Table,
Keyswitch, Controller Password, and the Register Protection Table. These features
are discussed in greater detail in the Core Components Training Guide.
6. The Create new controller form should now appear as follows:
7. Click Apply and the 8000 IO Configurator utility is launched.

8. The Create Controller dialog appears. Enter the Node Number and click OK.
(The default Node Number is 126.) For our example, use a node number of 50.

9. The controller appears in the 8000 IO Configurator as follows:

10. Click the controller name in the IO Configurator and select the Attributes tab.
11. Enter the appropriate Master IP address, Direct A IP address, Direct B IP

address, and Subnet Mask for the controller. (All three IP addresses must be
entered even for simplex controllers.) For our example, enter the following IP
addresses and Subnet Mask:
Master IP address: 10.1.29.50
Direct A IP address: 10.1.29.51
Direct B IP address: 10.1.29.52
Subnet Mask: 255.255.0.0

12. Set the Type field to match your controller type (Logic, Process, Hybrid, EBIM or
SafetyNet Logic). This field should match the controller type chosen when the
controller was created. The First Control Package field must be set correctly
based on your controller type:
Logic Controller (Logic 8521-LC-MT): Set First Control Package to Logic IEC-
61131-3.
Process Controller (Process 8521-PC-MT): Set First Control Package to
Process Control.
Hybrid Controller ( (8521-HC-MT): Set First Control Package to either Logic
IEC-61131-3 or Process Control, based on which control strategy executable
you want to run first.
Ethernet BIM (8521-EB-MT): Set First Control Package to No Control
Packages.
SafetyNet Logic (8851-LC-MT): Set First Control Package to Logic IEC-71121-
3.
For our example, select a Type of Hybrid (8521-HC-MT) and set the First Control
Package to Logic IEC-61131-3. Once the above data is entered, the screen
appears as follows:

13. Continue entering the information appropriate for this controller on each of the tab
sheets (Properties, Attributes, COM Attributes, System, Device Mask, Dynamic
Data, Module Detail). For our example, we assume that no additional data is
required.
14. Select the File | Save menu option.
15. Select the File | Exit menu option and return to the Workbench.

16. Expand the Project folder and double-click the Launch Network Configurator
node. The Network Configuration Utility is launched.
17. The configuration database for the new controller is automatically loaded and the
network is interrogated to determine which controllers are currently responding.
This query takes approximately 10 seconds from the time of launch.

18. Because the new controller has not been configured, it is not “seen” on the
network, and does not appear in the list view box. The Network Config Tool begins
to “listen” for controllers that are broadcasting their MAC addresses. When it
determines that a controller is broadcasting, the icon in the lower right corner of the
form shows a disconnected network. If your new controller is installed correctly on
the network, the following icon appears in the bottom, right corner of the utility with
a yellow background and a red X:
Note: If there are multiple new controllers, only one should be put on the network
at a time so that it is clear which controller is being assigned IP addresses. In
addition, if your controllers are a redundant pair, only one controller
should be powered up at this time. Once the IP address configuration is
complete, power up the second controller. The IP addresses of the second
controller are automatically set by the first controller.

19. Double-click this icon to start the configuration dialog. Alternatively, you may select
the Tools | Assign IP Address menu item.
20. The Assign MAC Address form is displayed, showing all of the controllers that are
currently defined in the 8000 IO Configurator database. If the database has a MAC
address that matches the unconfigured controller, that line is selected. Otherwise,
no lines are selected.
Note: The unassigned MAC address appears in the title of the form.

21. Select an entry and click Apply or double-click an entry to display the Assign IP
Address dialog:
22. Click Cancel or Apply. If you click Apply, the network is queried to ensure that the
selected IP addresses are not in use on the network. If they are in use, you are
made aware of this and have the option to cancel the assignment. If the IP
addresses are not in use, the IP addresses and Modbus Node Number are sent to
the unconfigured controller. If the original MAC addresses were not entered, the
MAC address of the unconfigured controller is written to the 8000 IO Configurator
database.

23. If the All Controllers option is selected on the Assign MAC Address form, you
may receive a warning message upon assigning the IP addresses to the controller.
This is due to the fact that the MAC address of the controller does not match the
MAC address with which the IP address was previously associated.
24. Click Yes (No is the default) to assign the IP Addresses to the unconfigured
controller and write the unconfigured controller’s MAC address to the 8000 IO
Configurator database.
25. Once the IP Addresses are assigned to the controller, the Network Configurator
checks to see if any configuration exists in the controller. If it does, the
configuration items are listed and you are asked if the items should be cleared.
26. Click Yes to clear the information, thereby making the controller configured as it
was when it left the factory. Click No to leave the information intact.

27. Once the IP addresses are assigned, select Check Network | Wait 2 Seconds
from the Tools menu. This causes the network to be queried for controllers and all
controllers found on the network are presented. In our example, one controller is
found:
Note: If controllers do not appear in the list view box, it may be necessary to
select the appropriate Network Interface Card, if there is more than one in your
PC. Select the Tools | Check Network | Select Network Card pull down menu
and choose the desired card.

Configuring IO Modules
Once the IP addresses are assigned, the remaining configuration can be entered and
then downloaded to the controller through the use of the 8000 IO Configurator.
1. In the Project Explorer expand the controller node and double-click Launch 8000
IO Configurator.

2. Right-click the controller node (the tree branch named 50Ctrl1 in our example) and
select New Module from the resulting menu to add IO Modules. The following
dialog appears.
3. Select the correct module type from the Type drop down list and pick the
appropriate slot for the module from the Slot number drop down list. For our
example, select the 8101-HI-TX and place it in Slot number 1. Click OK.

4. Click the to the left of the controller name to expand the list and display the
module that was just added.
5. Click on the module and select the Channel Attributes tab to configure the
module’s channels. The fields are defined as follows:
• Active - If this field is checked, the module scans the channel for an input
value. For our example, leave all channels active.
• Alarm Limits -These settings correspond to hardware alarms, not operator
interface alarms, as the operator interface alarms are configured as part of
the project tag definition. The hardware alarms are set in terms of percent,

with 0% being 4mA and 100% being 20mA. Set the Hi Alarm field to 105%
and the Lo Alarm field to -5% for all channels. This causes the channels to
fail if the transmitters fluctuate a threshold below 4mA or above 20mA.
• Deadband - The hysteresis for the alarm. Leave as 0% for our example.
• Deadzone - The smallest change in input reported by the module. Leave as
0% so all changes are reported.
• Failstate Condition - The value applied by the module when the controller
and module lose communication. This can be Hold Last Value, Fail High, Fail
Low, or Fail to a Predefined Value. Leave this set to Hold Last Value.
• HART Comms - If a HART-capable smart transmitter is connected to the
channel, set to Enabled to cause the module to retrieve the four HART
variables via universal command 3. If the transmitter does not support HART,
leave as Disabled or the channel will be unhealthy. Leave this field as
Disabled for our example.

6. Repeat the process above to add an 8102-HO-IP to Slot 2, an 8115-DO-DC to Slot

3, and an 8105-TI-TC to Slot 4. When the 8105-TI-TC is added, the following
warning appears to notify you that the 8105-TI-TC does not require bussed field
power, but the 8115-DO-DC does. Click Yes.
7. The IO Configurator appears as follows:

8. The IO configuration must now be downloaded to the controller to become active.
Click the green traffic light in the toolbar to place the controller online.
9. Select the Configuration | Download Controller menu item to initiate the download.
The Download Configuration Options dialog appears. Leave the options as
default. (Save configuration to NVM after download and Continue Module
Scanning selected.)
As these options are appropriately defaulted based on the changes made to the
configuration, we recommend that you leave the options set at default. The options
are defined as follows:
• Save configuration to NVM after download – Causes the hardware
configuration to be saved to flash memory once the download is complete.
Therefore, if power to the controller is cycled, the configuration is retained.
• Restart controller after download – Once the download is complete, the
controller is restarted. This is only necessary if address changes are made
(IP addresses or node numbers) and should not be done on a running plant.
• Continue Module Scanning – If this option is not selected, each module is
restarted once the configuration is downloaded. Therefore, selecting this
option allows the modules to continue scanning during the configuration
download, ensuring that configuration changes can be made to a running
plant.

10. Once the options are set, as appropriate, click OK to start the download. The
Download progress dialog indicates completion. Click OK once the transmission is
complete.
11. Select the controller node in the IO Configurator and select the Module Detail tab.
The modules configured in the IO Configurator match the modules in the controller;
the modules should all have the Module State of Running as shown here:

Note: If the module state is something other than Running, the wrong modules
were probably selected during the configuration process. Verify that the modules in
the IO carrier match the modules in the configuration, make changes as
appropriate, and download again.
12. Close the IO Configurator. If you have not saved the changes, you are prompted to
do so at this time.

Creating and Assigning Project Tags

1. In the Workbench Project Explorer, right-click the Project Tag Index node and
select New Tag.
2. A name for the tag is requested.
3. Enter TE101 for the name and click OK. To complete the tag definition, fill in the
fields on the IO Definition tab, as follows:
Description 1: Temp element 101
Engr Min or DI0 State: 0
Engr Max or DI 1 State: 250
Engr Units: DEG C
Signal Type: TCK
Signal Min: 0
Signal Max: 100
Assigned: NA
Click Save Data to commit the changes.


4. Repeat the above process to add the following tag:

Tagname: MotorStarter
Description 1: Starts the motor
Engr Min or DI0 State: OFF
Engr Max or DI 1 State: ON
Engr Units: NONE
Signal Type: DO
Signal Min: 0
Signal Max: 24
Assigned: NA
Notes:
• Tags that are already defined in a spreadsheet can be imported. Save the
spreadsheet data in CSV format and use the Data Import Utility. Open
the Window Explorer; the Data Import Utility is located at the following
path: <installation_drive>\Program Files\8000\Control
Center\DataImportUtility.exe. For more information, please refer to the
Data Import Utility Help file or the Importing Tags lab in the Core
Components Training Guide.
• Workbench version 8.4 and subsequent releases support the creation of
arrays. Please refer to the How To | Project Tags | How to Create and
Use Arrays section of the online Help for more information.

5. Double-click Controller Modules under the controller node in Project Explorer to
associate tags with modules. Click the to the left of the controller name in the
middle pane to expand the list and display the modules that were added in the
8000 IO Configurator.

6. Select a module (be sure to click a channel) and choose the appropriate tag for the
channel. For our example, choose the TI, TCH/mV, 4-Ch, 2/2 (4) and click Get
Assigned IO in the Assign points pane.

7. On the channel to which the point is to be assigned, select the appropriate signal
type in the Signal drop down list for the channel. Click on the word Spare for the
appropriate channel and pick the tag to be assigned. For our example, select the
TCK signal for Point 2 and the TE101 tagname.

8. Click Apply to assign the tag to the channel.

9. Repeat these steps for each tag to be assigned. For our example, assign the tag
MotorStarter to channel 1 of the DO module.
10. To compile the IO, right-click the controller in Project Explorer and select Compile
IO.

Working with Process Control Strategies

This section describes the necessary steps to create a process control strategy, compile
the strategy, download to the simulator and/or the controller, and then debug the strategy
using real time data. If you do not have a Hybrid or Process controller, this section does
not apply to you.
Creating a Process Control Strategy

Applies to: Hybrid and Process Controllers
To create a process control strategy, start by creating a new drawing; add blocks and
connectors to the drawing, and then compile the drawing.
1. Right-click the controller and select Drawings | New Drawing. The Create New
Drawing dialog appears.
Note: This process creates a blank drawing. The Workbench has a number of
predefined templates to assist in quickly creating drawings for common
operations (PID, Motor Control, etc.). Click From Template to utilize this feature.
For more information about using the From Template feature, refer to the
Creating a Drawing from a Template lab in the Templates section of the
Process Control Training Guide.

2. Specify a name and description for the drawing and click OK. For our example, use
the name AddBlock with a description of My first drawing.
3. The Strategy Builder is launched and the drawing can be created.

4. The Zoom icon ( ) is used to expand a section of the drawing. Blocks and
connectors are added to drawings by dragging them from the toolbars and
dropping them onto the grid. Each end of the connector must be placed on an
appropriate connection point. When the connector is properly anchored at an end
point, the arrow disappears. When both ends are properly anchored, the connector
changes from red to green. For our example, drag an ADD block from the Math
blocks catalog ( ) and drop it onto the drawing. Enter ADDRESULT in the
Output Symbol field and Integer in the Output Type field of the Enter ADD
Attributes dialog. Click Save.
5. Drop a FIXED block from the Logic catalog ( ) next to the ADD block and enter
a Value of 1 on the Enter FIXED Attributes dialog.

6. Click Save and then use connectors to connect inputs to outputs as shown here:
7. Once all drawing elements have been added, save and compile the drawing using
the File | Save/Compile menu item. Errors are reported as they are encountered.
8. Repeat this process if you have additional drawings.
9. Once the drawings are compiled, the drawing icon should be yellow when viewed
in the Project Explorer. If a drawing icon is red, the compile was not successful.
Return to the drawing, fix any errors, and recompile.
Note: For more information about Function Blocks, please refer to the Function
Blocks manual located at the following path:
<installation_directory>\Documentation\Function Blocks Document.pdf.

Downloading to the Process Simulator

Now that the drawings have been compiled, they can be checked out in the simulator
before downloading to the controller.
1. From the Workbench Project Explorer, right-click the controller and select
Download Control Strategies to invoke the download screen.
2. Click Get Servers and select DesignerSim.

3. Click Connect to launch DesignerSim.
4. Select the Process option. The Process status is displayed as Not Current. Click
Download to initiate the download.
Note: The Perform Initialization option resets all register values in the simulator
or controller to their appropriate initial values. Therefore, this option should not
be checked when performing an online download.

5. Following a successful download, the Process status label is displayed with a
green background.
Note: Ensure that the number in the Per Scan field is one greater than the
number in the To field. If it is not, enter the appropriate number into the Per Scan
field and then click Update.

Downloading to the Controller

When a strategy is downloaded, all relevant drawings for a controller are combined into a
single, downloadable strategy called a .PRG file.
1. Launch the Workbench.
2. Right-click the controller and select Download Control Strategies.
3. Click Get Servers and select Universal IO Server from the Server drop down list.
If the Get Servers option is disabled, click in the Node field and press the space
bar to enable the button.
4. Ensure both the node number and IP Addresses are correct by selecting Modify
Node Number and Modify TCP/IP Address from the Panel menu. If either is
incorrect, return to the IO Configurator and specify the correct address. Click
Connect.

5. To initiate a download, select the Process option and then click Download.
Following a successful download, the strategy that was marked Not Current is
displayed as Current.

Process Control Strategy Checkout

Now that a download has been completed, the strategy can be viewed in real time so that
tuning parameters can be modified and logic execution can be viewed.
1. In the Project Explorer, right-click the drawing and select View Strategy Realtime.
2. The Strategy Builder is launched and the drawing is displayed with data.
3. To tune data or modify settings, double-click a block and change the values on the
tuning dialog.
4. The Strategy Builder can only be open for one mode: edit or view real time.
Therefore, if drawing changes are required, close the drawing, return to the
Workbench, and double-click the drawing to open it in edit mode.
5. This completes the development of the Process Control Strategy.

Working with Discrete Control Strategies

This section describes the necessary steps to create a discrete control strategy, build the
strategy, download it to the simulator and/or the controller, and then debug the strategy
using real time data. If you do not have a Hybrid or Logic controller, this section does not
apply to you.
Creating a Discrete Control Strategy

Applies to: Hybrid and Logic Controllers
To this point, all tags have been created in the Workbench. Because the IEC 61131-3
programming software is a separate application from the Workbench, tags must be
mapped before they can be used in Discrete Control.
1. In the Workbench Project Explorer, right-click the controller node and select Map
Data | Map Discrete Control Points.

2. The Discrete Control Data Mapping form is displayed. The Available Tags
panel, on the right, shows all created tags that can be used in the Discrete Control
application. The Mapped Tags panel, on the left, shows all tags that have been
mapped in the Discrete Control database.

3. To map a tag, click the tag in the Available Tags panel, drag it into the Mapped
Tags panel and release the mouse. (You can also double-click the tag in the
Available Tags panel.) Once all desired tags have been mapped, click Save to
commit the changes. In our example, map the tag MotorStarter and then click
Save. The screen appears as follows:

4. Double-click Create Discrete Control Interface in the Project Explorer to launch

the Discrete Control Interface. Programs, functions, and function blocks can now
be created or modified.
Note: If a project has already been created in Discrete Control, the Workbench
Project Explorer node is labeled Edit Discrete Control Interface.

To create a Program:
1. Right-click the Programs item; select Add Programs and the desired language
from the resulting menu. For our example, select LD: Ladder Diagram.
2. Once the language is selected, a new Program node is shown.

Note: For correct system behavior, do not rename the Resource or

Configuration nodes.
3. The program can now be renamed. Right-click the new program and select
Rename Program. Type SampleLD in the Name field and click OK.
4. Double-click the SampleLD program to launch the editor.
5. Click Yes when prompted to save the changes.
6. The appropriate language editor is launched and logic can now be written.

7. Click the Contact on the left icon from the toolbar to drop a contact. You
are prompted for the name.
8. Since no discrete input points have been mapped, we can create an internal
variable to complete the example. Type In1 in the top, left field and click OK. You
are prompted to complete the variable definition:

9. Click OK to accept the definition and then click OK again to assign the variable to
the contact.
10. To change the contact or coil type, select the Logic element and press the space
bar to cycle through the available contact/coil types.

11. Once logic has been written, select the File | Build Program menu item to compile
the program and determine if any errors exist. If so, the errors are displayed in the
output window as follows:

12. Correct any errors and do not proceed until there are no errors produced. In our
example, the error occurred because no variable was assigned to the contact. To
correct this error, double-click the coil and assign it a variable. Select the tag
MotorStarter for this purpose. Build the program again and no errors should result.
13. Close the language editor and return to the Discrete Control Interface.

14. Before the program(s) can be downloaded, they must be built so that all programs,
functions, and function blocks are linked together into one downloadable image.
Select the Project | Build Project/Library menu item to build the program(s) in the
Discrete Control Interface.

15. If all errors have been eliminated from the individual programs, the output window
appears as follows:
16. If errors are displayed, return to the appropriate program and correct the errors
before returning the Discrete Control Interface to build the project again.
17. Once all errors are removed, you are ready to download the program(s) to the logic
simulator or the controller.

Downloading to the Logic Simulator
Now that the drawings have been compiled and the IEC 61131-3 logic built, they can be
checked out in the simulator before downloading to the controller.
The Discrete Control Interface has its own simulator, which does not interface with the
Process simulator. Therefore, process control strategies and discrete control strategies
are simulated on their own. To test the interactions between the two, an actual controller
must be used.
To download to the Logic Simulator:
1. Launch the Discrete Control Interface.
2. Select the Debug | Simulation menu item. Several DOS windows are launched
and the Discrete Control Interface appears, as shown below, once the Logic
Simulator is successfully launched. (Do not close the DOS windows; they close
when the simulator is stopped.)

3. Once logic has been debugged, it is necessary to stop the simulation before a
program, function, or function block can be changed. To stop the simulation, select
the Debug | Stop Simulation menu item.

Downloading to the Controller
When a strategy is downloaded, all relevant drawings for a controller are combined into a
single, downloadable strategy called a .PRG file.
1. Launch the Workbench.
2. Right-click the controller and select Download Control Strategies.
3. Click Get Servers and select Universal IO Server from the Server drop down list.
4. Ensure both the node number and IP Addresses are correct by selecting Modify
Node Number and Modify TCP/IP Address from the Panel menu. If either is
incorrect, return to the IO Configurator and specify the correct address. Click
Connect.

5. To initiate a download, select the Process and/or Discrete Control option and
then click Download. Process and Discrete Control can be downloaded
independently or simultaneously. If both are being used and one has not changed,
only the changed strategy must be downloaded to the controller. Following a
successful download, the strategy that was marked Not Current is displayed as
Current.

Discrete Control Strategy Checkout
Now that a download has been completed, the strategy can be viewed in real time so that
tuning parameters can be modified and logic execution can be viewed.
As with Process Control Strategies, Discrete Control strategies can be viewed with data
from either the simulator or the controller.
1. Open the Discrete Control Interface.
2. If the logic will be verified using the simulator, select the Debug | Simulation menu
item. Select this option for our example.
If the logic will be verified using the controller, select the Debug | Debug menu
item.
3. After starting the appropriate data collector, data can be viewed in the Dictionary or
the appropriate logic editor. Using our original ladder diagram example, the real
time view appears as follows:

4. To change the values of logic elements in a ladder diagram, double-click the

element. A Spy List can be used to monitor the value of one or more tags. This
occupies the lower portion of the ladder diagram editor window. To select the
variables to display in this window, double-click on the ellipses (…) in the Spy List
and select Resource; then select the desired variable. If both In1 and
MotorStarter were put into the Spy List, the window appears as follows:
5. After debugging the logic, the simulator or debugger must be stopped before logic
changes can be made. Select either Stop Debug or Stop Simulation from the
Debug menu to stop the debugging process. For our example, select Stop
Simulation.
6. This completes the development of the Discrete Control Strategy.

Retrieving Data from Other 8000 Controllers

8000 Controllers share data through peer to peer communications, thereby allowing an
8000 controller to read data from other 8000 controllers. Rather than configuring the
producer to send data to each consumer, the consumer is configured with the data it
needs from each producer. The following example assumes that a project named Boiler
has been created and that the controller Blrcc1_v1, within this project, has a number of
tags defined including a tag called ADDRESULT.
Note: If you do not wish to create the Boiler project from scratch, use the previous
steps in this tutorial to create the project, controller, and tags. Alternatively, create a
new project from the backup project Boiler. After restoring the project, create the
AddBlock drawing you made earlier in the Boiler project.
1. Right-click the consumer controller node and select Map Data | Map Points from
Remote 8000 Controllers.

2. The Map Peer to Peer Points form is displayed.
3. The right-hand portion of the form lists the tags that can be mapped from
controllers defined in any project. To map a tag, select the Project and Controller
containing the desired data from the available fields. In our example, data from the
Blrcc1_v1 controller in the Boiler project is retrieved.

4. Once the producer Project (Boiler) and the Controller (blrcc1_v1) are selected,
click Get Tags to list all tags defined in the controller.

5. The left-hand portion of the form lists the tags from other controllers that are being
referenced by the current controller. To select a tag for retrieval, drag and drop the
tag from the Available Remote Tags panel into the Currently Mapped Remote
Tags panel or double-click the tag in the Available Remote Tags panel. In our
example, map the tag AddResult, as shown below.

6. Repeat this process for each tag to be mapped. Tags can be retrieved from any
number of controllers in any number of projects. Once all tags have been mapped,
click Save to commit the changes.
7. Perform a controller download to initiate the data exchange. (Please refer to the
Downloading to the Controller section of this document for more information.) Once
this is complete, the producer controller(s) send(s) the data to the consumer
controller(s) on an exception basis.

8. The data exchanged can also be used on control strategy drawings or in IEC
61131-3 logic. In control strategy drawings, computed analog results that come
from other drawings via peer to peer data are referenced on a CNCA block.
Similarly, digital results from operations are referenced on a CNCD block. The
name of the tag is not the same as the tag mapped from the remote controller.
Rather, the prefix for the original tag name is RMT<remote_node_number>_. In
our example, the tag ADDRESULT was mapped from a controller with a node
number of 50. Therefore, the remote ADDRESULT tag would be referenced in the
local controller using the name RMT050_ADDRESULT and shown as below on a
control strategy drawing. Open an existing drawing or create a new drawing and
drop the CNCA or CNCD block from the Connector catalog, as needed, to use the
peer to peer tags.
Note: If IO values are to be retrieved from other drawings, REMOTE_SAIF,

REMOTE_SAOF, and REMOTE_D blocks are used for this purpose. These
blocks use the project tag definitions in the source controller to scale the values,
rather than displaying the values in raw units.

9. Tags can also be mapped to the Discrete Control Interface and then used in IEC
61131-3 programs, functions, and function blocks. Invoke the Discrete Control
Data Mapping form to map the peer to peer tags to the Discrete Control Interface.
(Refer to the Creating a Discrete Control Strategy section of this guide for more
information.)
Note: Because peer to peer is a read-only mechanism, to write data, the

destination controller must read from the source controller. For more information,
please refer to the Troubleshooting | Tech Notes | Writing Values to E-BIMs
section of the Workbench online Help.

Mapping Points from Remote Modbus Devices

Many applications require data from external sources, such as a flow meter or a turbine
governor. In most cases, these devices have an interface through which data can be
retrieved from the device or written to the device. If the data can be accessed through
Modbus RTU or Modbus TCP, the 8521 controllers can be configured as a Modbus
Master and used to read and write the data.
Such points are mapped using the Map Remote Device Points form in the Workbench.
For a specific example of mapping remote device points, please refer to Mapping Points
from Remote Modbus Devices lab in the Training Guide.
1. To launch this form, right-click the controller and select Map Data | Map Points
from Remote Modbus Devices.

2. The Map Remote Device Points form is displayed.
3. Before points can be added, the device must be precisely defined. Enter the
appropriate information into the following fields.
• Device Name – The name you are giving to the device.
• Remote Device Node No. – The Modbus address of the remote device.
• Scan Rate – The frequency at which each remote tag is written to or read
from.
• Controller Port – The port that is used by the controllers to communicate
with the remote device. This can be one of two serial ports on the controller
or over TCP. If TCP is used, the Remote IP address must contain the IP

address of the remote device and the Remote Socket Port No. must
contain the socket that the remote device uses to communicate over TCP.
• Response Timeout – The maximum time that the controller awaits a
response once the command is sent to the remote device. If the response
is not received within this time period, a timeout for the message occurs.
Note: The items above define a logical device. There may be times when some
points need to update at one scan rate, while other points need to update at a
different scan rate. To meet this need, add another device with the same
communication parameters (node number, port settings, packing, command
delay, etc.) and modify only the scan rate. This works because a physical
device can correspond to one or more logical devices. However, if
communication parameters are modified, these changes are ignored. While the
device supports multiple scan rates, it only supports one set of communication
parameters.
4. Once the device is defined, points for reading and writing data can be defined.
Select the appropriate command in the Function drop down list of the Remote
Register section.
5. Specify the 1-based offset (NOT full address) in the Offset field. (For example, you
would enter 1 for a remote point at 030001.) The system builds the appropriate
address by specifying the command and the offset.
6. The Local Register section can now be completed. Select the Register Space for
the data and leave the Offset as System Assigned so that the Workbench selects
the next available memory area to deposit the data.
Note: For more information regarding configuring the system for these points
(configuring the serial ports on the controller for Modbus Master, configuring
tabs, and troubleshooting device data), please refer to the Troubleshooting |
Tech Notes | Mapping Points from Remote Modbus Devices section of the
Workbench online Help.

Linking to InTouch
This section describes the process of linking InTouch screens to the Simulator. To do
this, InTouch must be configured to pull data from the simulator provided as part of the
PAC8000 Workbench (DesignerSim). This association allows you to preview the graphic
screens in the absence of actual hardware.
The steps listed below assume that you have InTouch version 7.11, 8.0, or 9.0 installed
and that you are familiar with creating projects and windows in InTouch. If you are not,
please refer to InTouch online documentation for assistance. Screen shots shown use
InTouch version 9.0. If you are running a different version, the screens may be somewhat
different.
Connecting to DesignerSim
1. Open the Application Manager.

2. Create a new Wonderware application called WonderwareDemo1. Double-click

the new application to open WindowMaker.
3. Once WindowMaker is open, select Special | Access Names.

4. Click Add to create a new Access Name. For our example, use the name Ctrl1
to match the name of the controller created earlier in the Project Tutorial.
5. Fill in the of the fields as follows:

Node Name: The node name references the computer on which the IO
Server runs. In our example, this is the local computer, so leave it blank.
Application Name: The name of the IO Server used to provide data to
InTouch. For the Simulator, the application name is DesignerSim.
Topic Name: The controller from which data is retrieved. This must match
the controller name created in the PAC8000 Workbench in both spelling and
capitalization. For our example, use Ctrl1.
Which protocol to use: The simulator supports DDE; select this option for
our example.
When to advise server: Select Advise only active items for our example.

Once the data has been entered, your screen appears as follows:
6. Click OK and then click Close on the Access Names window. You are now
ready to import tags and create windows.

Connecting to the Universal IO Server
This section describes the process of linking InTouch screens to the controller. To do
this, InTouch must be configured to pull data from the Universal IO Server (also known as
StacServer). This association enables the HMI screens to be updated with live data from
the controller.
The steps listed below assume that you have InTouch version 7.11, 8.0, or 9.0 installed
and that you are familiar with creating projects and windows in InTouch. If you are not,
please refer to InTouch online documentation for assistance. Screen shots shown use
InTouch version 9.0. If you are running a different version, the screens may be somewhat
different.
1. Open the Application Manager.

2. Create a new Wonderware application entitled WonderwareDemo1. Double-click

the new application to open WindowMaker.
3. Once WindowMaker is open, select Special | Access Names.

4. Click Add to create a new Access Name. For our example, use the name Ctrl1 to
match the name of the controller created earlier in the Project Tutorial.
5. Fill in the of the fields as follows:

Node Name: The node name references the computer on which the IO
Server runs. In our example, this is the local computer, so leave it blank.
Application Name: The name of the IO Server used to provide data to
InTouch. For the controller, the application name is StacServer.
Topic Name: The controller from which data is retrieved. This must match
the controller name created in the PAC8000 Workbench in both spelling and
capitalization. For our example, use Ctrl1.
Which protocol to use: When linking InTouch to the controller using the
Universal IO Server, the preferred protocol is SuiteLink.
When to advise server: Select Advise only active items for our example.

Once the data has been entered, your screen appears as follows:
6. Click OK and then click Close on the Access Names window. You are now ready
to import tags and create windows.
Note: Configuration of the Universal IO Server is not required, as this occurs

when Connect is clicked on the PAC8000 Workbench download form. (See
Downloading to the Controller.) Ensure that you set the Universal IO Server to
start automatically, using the services program available from Control Panel |
Administrative Tools.

Importing Tags into HMIs
Importing Tags into Cimplicity

Included with your purchase of PPS is a utility (CLIE_Tool.exe) that automates the import
of PAC8000 tags into the Cimplicity system. This utility can be executed manually or
automatically following a download to a controller to generate a csv file with all of the HMI
tag data. The tag data can be imported either in offline or dynamic mode. In dynamic
mode, the data will be updated in a running system. Since the import is slower in dynamic
mode, an option is available to only update those tags that have been added or edited
since the last successful import. For further information, please refer to the online Help
file included with the CLIE_Tool.
Importing Tags into iFIX

Included with your purchase of PPS is a utility (8000_to_iFIX_CSV.exe) that automates
the import of PAC8000 tags into the iFIX system. This utility can be executed manually or
automatically following a download to a controller. Following the generation of the
standard csv file, the file is converted into iFIX format using the 8000_to_iFIX_CSV.exe
utility. Following the conversion, this data can optionally be exported to iFIX
automatically. For further information, please refer to the user guide (8000_to_iFIX CSV
File User Guide.pdf) included with the utility.
Importing Tags into Wonderware

1. Start the Wonderware InTouch application.
2. Click the DBLOAD icon in the toolbar.

3. When the dialog box appears, browse for the CSV file that was created for the
controller. This file is located at the following path: <installation_drive>:\Program
Files\8000\Control
Center\Projects\Proj_MyFirstProject\Ctrl_Ctrl1\CTRL1.CSV. For non-EBIM
controller types, this file is named CCCC.CSV, where CCCC is the controller name.
For EBIM controller types, this file is named IO_ONLY_WW.CSV.
4. Click OK to import the data values.

5. WindowMaker and WindowViewer cannot be running when performing a
DBLOAD. If tags must be imported with InTouch active, use the Tag Import
Wizard.
Note: For more information regarding Wonderware Wizards, please refer to the
Workbench Wizards manual.

Additional Information
The Project Tutorial has taken you through the process of creating, downloading, and
troubleshooting a basic control strategy. Due to the high-level nature of this Getting
Started Guide, you will certainly require additional information as you become more
familiar with the Workbench. Some common functions for which you may require
additional resources include:
• Project Backups - Once the project is complete, it should be backed up so that
a zip file of the backed up project can be placed in a safe location for subsequent
use. This process is discussed in the online Help topic How to Backup a Project
and the Backing up a Project lab in the Training Guide.
• Reports - Please refer to the Reports section in the online Help or Reports
section in the Training Guide for a complete discussion of the reporting functions
that are built into the Workbench.
• Diagnostics and Troubleshooting - A detailed discussion of troubleshooting
and maintenance features is available in the Maintenance course. For more
information about this course, please visit the Website: www.ge-ip.com/support.
• HMI Graphics and Alarming - Please refer to the documentation that comes
with your HMI for a detailed discussion of these features. If your HMI is InTouch,
IO and Controller tags are set up to automatically alarm. A detailed discussion
can be found in the External Application/HMI Interface section of the online
Help.
• Training - GE offers a comprehensive set of training classes for those who will
be using the PAC8000 products. For more information about these courses,
please visit the Website: www.ge-ip.com/support.

Glossary
8000 IO Configurator – Configures the system hardware (controllers and IO modules)
for a controller.
8000 Process IO System – Control system comprised of a controller and IO modules.
8521 – Product number of the controller.
.NET Framework – Microsoft technology used in some of the PAC8000 Workbench
components.
Basic Input/Output System (BIOS) – Area of the PC that monitors and controls all
system hardware.
Basic Support – PAC8000 support program that provides responses to your product
questions on the next business day.
Coil – Basic discrete output element in IEC 61131-3 Ladder Diagram programming.
Consumer – Uses data from one or more producing controllers.
Contact – Basic discrete input element in IEC 61131-3 Ladder Diagram programming.
Control Platform – Controller hardware upon which control strategies execute.
Control Strategy – Logic that executes within a controller to perform a task, e.g.
controlling a valve, starting and stopping a motor, etc.
Controller – Processor that executes control strategies and process IO.
Controller Statistics – Workbench feature that displays scan time breakdown, system
parameters, and event logs.
Custom Reports – User-created reports with customized output to fit all documentation
needs
Data Entry Panel – Right-hand pane of the Workbench. As specific tasks are selected in
the Project Explorer, the Data Entry Panel changes to facilitate data entry.
Database Maintenance Utility – Workbench utility that allows for maintenance tasks on
the database, e.g. reload, attach, de-attach, etc. This utility should only be used with
assistance from technical support.
Demo mode – Workbench mode that executes when no license file has been obtained.
In this mode, downloads to the controller are disabled, but all other functions are
available.

DesignerSim – Enables the control system designer to test control strategies in a single
controller without the need of physical hardware.
Discrete Control – The IEC 61131-3 programming environment.
Dynamic Link Libraries (dll) – Programming unit that provides functions or information
to other programs.
Ethernet BIM – Controller type that functions as a remote IO scanner, as no control
strategies are supported.
Executable File (exe) – File that can run directly on a computer.
Floating Point – IEEE precision numbers that are represented in two consecutive
registers.
Function Block – Unit of code that uses inputs to compute one or more output(s).
Examples of function blocks include PID and motor control.
HART – Communication protocol that places digital information on top of a 4-20mA
signal, allowing a transmitter to send up to four data values in addition to the normal 4-
20mA signal.
Human Machine Interface (HMI) – Graphical view of the process normally presented to
the operator, consisting of items such as value displays, animation, and trends.
Hybrid Controller – Controller type that supports both Process (Advanced Function
Blocks, such as PID and Motor Control) and Logic (IEC 61131-3) control strategies.
Hybrid Workbench – Licensed version of the workbench that supports creating control
strategies in both Process (Advanced Function Blocks, such as PID and Motor Control)
and Logic (IEC 61131-3) languages.
Hysteresis – Prevents alarms from recurring when the value is hovering close to the set
point.
IEC 61131-3 – International standard that defines how certain programming languages
and their attributes should behave.
IEC languages – Ladder Diagram, Structured Text, Instruction List, Function Block
Diagram, and Sequential Function Chart.
InBatch – Invensys’s S88 compliant batch execution engine.
Industrial SQL Server – Invensys’s historian.
Integer – Number that can be represented in a single register.

InTouch – Invensys’s HMI product.

IP Address – An identifier for a computer or other device (printer, plotter, etc.) on a
TCP/IP network.
Logic Controller – Controller type that executes only Discrete Logic.
Logic Workbench – IEC 61131-3 programming environment included in Hybrid and
Logic Controllers.
Matrikon – OPC client that is installable from the Additional Programs section of the
Product Installation CD.
Media Access Control Address (MAC Address) – Unique address that identifies each
device on a network.
Microsoft Desktop Engine (MSDE) – Allows the PAC8000 Workbench to access MS-
SQL type databases.
Modbus RTU – Serial communication protocol widely used in the industrial automation
industry.
Modbus TCP/IP – Modbus over Ethernet.
Module – Physical IO device that provides data to the controller.
Module Channel – Portion of a module that is connected to the physical field device, i.e.,
transmitter, positioner, etc.
Network Configurator – Network management tool used to assign IP addresses to
unconfigured controllers and show network information for all controllers on a process
network.
Node Number – Modbus address of the controller.
OPC – Object Linking and Embedding (OLE) for Process Control.
Peer to Peer – Mechanism that allows controllers to exchange data without the need for
additional programming.
PID Loop – Process control function block that drives an output based on the difference
between the measured process variable and the desired setpoint.
Premium Support – PAC8000 support program that routes your calls, emails, or faxes to
an engineer as soon as one is available within normal business hours.
Process Controller – Controller type that supports Process control strategies (Advanced
Function Blocks, such as PID and Motor Control).

Process Workbench – Version of the Workbench that supports creating strategies in the
Process language (Advanced Function Blocks, such as PID and Motor Control).
Producer – Supplies data to one or more consuming controllers.
Project Explorer – Located in the left-hand pane of the Workbench; assists in adding
controllers, drawings, tags, modules, etc.
Project Tags – Names and attributes assigned to channels on IO modules.
Real Time – Viewing control strategies with data updating as soon as it is available from
the controller or simulator.
Redundant Controller – Two controllers running in lockstep. The standby controller
continually monitors the health of the master controller so it can take over within the
same scan if the master controller fails.
Sequence of Events (SOE) – Sequence of Events data gives an accurate time for event
occurrence, along with the event value and other useful information. This data can then
be used to help determine a specific order of occurrence.
Simplex Controller – Single controller used to execute control strategies and process
IO. Systems can be made redundant by adding a second controller.
Simulator (DesignerSim) – Enables the control system designer to test control
strategies in a single controller, without the need of physical hardware.
StacServer – Application name for the Universal IO Server. The Modbus TCP/IP and
OPC server that comes with the PAC8000 Workbench.
Standard Reports – Reports that are shipped with the product and pertain to either a
project or a controller.
Strategy Builder – Process control logic diagrams are developed here by selecting the
appropriate function blocks, assigning symbolic tags, and then connecting the blocks with
analog or digital lines.
Strategy Viewer – Facilitates the animation of logic diagrams with either simulated or live
real time process data.
SuiteLink – Communication protocol used within InTouch to communicate with devices
on either a local machine or a remote node.
Universal IO Server – Modbus TCP/IP and OPC server that comes with the PAC8000
Workbench.

Wizard – Mechanism for gathering operator input to some of the more complex function
blocks of Process Control.
Wonderware – Suite of products that include InTouch, InSQL, and InBatch.
Workbench – Application that provides the foundation for defining a project and all of its
components: tags, hardware configuration, tables, and control logic.

PAC8000 Workbench Getting Started Guide: GE Intelligent Platforms, Inc. 2500 Austin Drive Charlottesville, VA 22911

Uploaded by

Copyright:

Available Formats

PAC8000 Workbench Getting Started Guide: GE Intelligent Platforms, Inc. 2500 Austin Drive Charlottesville, VA 22911

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PAC8000 Workbench Getting Started Guide: GE Intelligent Platforms, Inc. 2500 Austin Drive Charlottesville, VA 22911

Uploaded by

Copyright:

Available Formats

PAC8000 Workbench

Getting Started Guide

GE Intelligent Platforms, Inc.

Downloaded from www.Manualslib.com manuals search engine

© Copyright 2010 by GE Intelligent Platforms, Inc.

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

Accessing Additional Help

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

Frequently Asked Questions (FAQ)

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

Section 2 – Workbench Software Components

This section provides a high-level view of the PAC8000 Workbench software

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine

Installing the PAC8000 Control Center Workbench

GE Intelligent Platforms, Inc. September 2010

Downloaded from www.Manualslib.com manuals search engine