SafetyNet Logic Workbench Getting Started Guide
SafetyNet Logic Workbench Getting Started Guide
The text and screen shots in this document are compatible with Workbench Version 8.3.0 and subsequent releases. If you
are running a previous version, please contact Technical Support.
SafetyNet Logic Workbench Getting Started Guide 3
Contents
CONTENTS ........................................................................................................................ 3
SECTION 1 – INTRODUCTION ......................................................................................... 5
Scope .......................................................................................................................... 7
Intended Readers ........................................................................................................ 8
Accessing Additional Help........................................................................................... 8
Help Files ................................................................................................................. 8
Frequently Asked Questions (FAQ)......................................................................... 8
Training .................................................................................................................... 9
Website .................................................................................................................... 9
Technical Support.................................................................................................... 9
SECTION 2 – WORKBENCH SOFTWARE COMPONENTS.......................................... 11
Workbench ................................................................................................................ 11
Tag Editor .................................................................................................................. 13
8000 IO Configurator................................................................................................. 14
Controller Modules .................................................................................................... 15
Discrete Control......................................................................................................... 16
Reports ...................................................................................................................... 17
Controller Statistics ................................................................................................... 18
Network Configuration Utility ..................................................................................... 19
Security Features ...................................................................................................... 20
SECTION 3 – INSTALLATION ........................................................................................ 21
Pre-Installation Information ....................................................................................... 21
Installing the PAC8000 Control Center Workbench .................................................. 23
Post-Installation Activities.......................................................................................... 38
Repairing the Installation........................................................................................... 38
SECTION 4 – ADDITIONAL PRODUCT CD FEATURES............................................... 39
Additional Programs .................................................................................................. 39
Information................................................................................................................. 42
SECTION 5 – LICENSING ............................................................................................... 47
SECTION 6 – PROJECT TUTORIAL .............................................................................. 48
Launching the Workbench......................................................................................... 50
Creating a Project...................................................................................................... 51
Section 1 – Introduction
Note: PAC8000 Open Control components can be used with any HMI software that
communicates via Modbus or OPC.
The safety controller is certified by TÜV to IEC 61508 for use in SIL2 applications. It
provides the same hardware functionality as standard controllers (lock step redundancy,
Ethernet redundancy, Peer to Peer data communication, and communication with other
Modbus devices), but limits programming functionality to a subset of the IEC61131-3
languages. The supported languages include Structured Text (ST), Ladder Diagram (LD),
and Function Block Diagram (FBD). In addition, the set of standard operators, functions,
and function blocks are limited to a set that is easily verified to ensure correct operation.
Scope
The intent of this Getting Started Guide is to provide assistance in building your first
application using the SafetyNet Logic Workbench. 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. This guide 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
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 or safety manual and no attempt is made to explain such details.
For additional installation information, please refer to:
• 8000 Controllers Hybrid, Process, Logic, and 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
• SM 8800 – Safety Manual
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 SafetyNet Logic Workbench for the first time
• Upgrading an existing application of the SafetyNet Logic Workbench
• Learning how to use the SafetyNet Logic Workbench
• Currently using the SafetyNet Logic Workbench, but wish to expand their
knowledge in key areas, such as the IEC 61131-3 programming languages.
Help Files
Application Help
A full set of Help files is delivered and installed with the system. From any
application, (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.
Workbench Wizards Manual
This manual lists the Wizards included with the 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
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.
• Basic 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: support.emea@ge-ip.com
This section provides a high-level view of the SafetyNet Logic 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 Workbench software includes the following system components:
Workbench
The 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:
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 Project Tags section in the Project Tutorial of this guide or refer to the labs in
the Modules section of the Workbench Core Components Training Guide.
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 Project Tags, or
Configuring IO Modules sections in the Project Tutorial of this Getting Started 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.
The SafetyNet system is delivered with the Standard report LogChangeReport, which
generates a list of logged changes to the Workbench projects.
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.
Section 3 – Installation
This section describes the process of installing the Workbench. If the 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 Workbench, please ensure the following:
• The drive where the 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 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 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
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 Workbench or the Universal IO server have
been stopped. If they have not, you are prompted to stop them during the
installation process.
Note: The text and screen shots in this document are compatible with Workbench
Version 8.3.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.
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.
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 Control Center 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.
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.
b. Select the desired location for installation from the Change Current
Destination Folder screen and click OK.
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 previously indicated, 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.
17. 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.
18. The Welcome to the InstallShield Wizard for the Universal IO Server (Limited
Edition) screen appears briefly.
19. The Installing Universal IO Server (Limited Edition) screen appears. A progress
bar indicates the status of the installation.
21. When the installation is complete, the PAC8000 Control Center InstallShield
Wizard Completed screen appears. Click Finish.
22. 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.
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 full 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.
• 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.
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.
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 Workbench.
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.
The SafetyNet Logic Workbench is the single engineering environment used to configure
and program safety controllers. The Project Tutorial walks through the steps that are
necessary to program a simple control strategy for a safety controller.
This project tutorial provides instruction for creating tags, configuring IO modules,
assigning tags to the modules, creating a simple discrete control strategy, downloading
the strategy, downloading the strategy to both the simulator and the controller, viewing
the data online, and authorizing devices for access to the controller. At the end of the
tutorial, you will have experience with each of the tools in the Workbench and have a
rudimentary knowledge of how they are used.
This tutorial assumes that you have a new safety controller or set of safety 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.
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
1. Select the File | New Project menu item to create a new project.
2. Enter SIS_Project in the Project Name field and click Apply.
3. Select the Attributes tab and enter 192.168.0.50, 192.168.0.51, and 192.168.0.52
in the Master IP address, Direct A IP address, and Direct B IP Address fields,
respectively, to configure the addresses in the databases.
Configuring IO Modules
1. Right-click the controller node and select New Module to configure modules. The
safety modules for the safety controller are the 8810-HI-TX and 8811-IO-DC
modules.
• Select 8810-HI-TX from the drop down list and place the module into Slot 1.
• Select 8811-HI-TX from the drop down list and place the module into Slot 2.
2. The controller remains in BOOTP mode until IP addresses have been assigned.
The Network Configurator is used to assign the IP addresses to the controller.
Expand the Project folder and double-click the Launch Network Configurator
node.
3. 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.
4. 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
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.
5. Double-click this icon to start the configuration dialog. Alternatively, you may select
the Tools | Assign IP Address menu item.
6. 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.
8. 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 Configurator
database.
9. 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.
10. 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
Configurator database.
11. 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.
12. 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.
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.
14. Return to the 8000 IO Configurator. Click the green traffic light from the toolbar
( ) and select the Download button ( ) to download the configuration to the
controller. Click OK on the Download Configuration Options window.
4. Once all tags have been assigned, right-click the controller in the Project Explorer
and select Compile IO.
3. Once all tags have been mapped, click Save. Right-click on the controller node in
the Project Explorer and select Compile IO.
3. Once the Program Organizational Unit (POU) is created, compile using File | Build
Program menu item in the editor.
One of the Graphical language editors (LD, FBD) can also be opened to view a live
representation of the strategy executing and displaying real-time data.
7. Once you have completed the simulation and are satisfied that the strategy is
executing correctly, you are ready to download the strategy to the controller using
the PAC8000 Workbench.
For more information on building strategies in Discrete Control, refer to the Discrete
Control Training Guide.
1. Before launching the analyzers, select the Project | Build Project/Library menu
item in the Discrete Control Interface to perform a build (if this has not already been
done).
2. Once the build is complete, click the Browser button ( ) in the toolbar to launch
the browser. The browser is used to create a usage map (Cross Reference table)
for all variables in the strategy.
3. The Browser dialog appears. Click the Browse button to build the usage map.
5. Once the usage map build is complete, the Browse button appears as normal and
the Browser window can now be closed.
6. Now that the browser has been built, the strategy can be analyzed. The analyzer
tools can be run in any order. In our example, we will run the Integrity Analyzer
first. To launch this analyzer, select Integrity Analyzer from the Tools menu.
The Integrity Analyzer compares the language, size, functions and function blocks,
IO Types, and variables in each POU to the predefined safety rules. These rules
define the “safe” languages, size, functions, and function blocks, as well as the
allowable number of inputs to the functions and function blocks, I/O types, and
variable types. The color of the POU indicates the level of non-compliance as
follows:
• Red - Integrity analysis error. Until the non-compliance is corrected, the
strategy cannot be downloaded to the safety controller.
For example, if a POU is written in an unsupported language, the Language
node icon on the Integrity Analyzer turns red.
• Yellow - Integrity analysis warning. A non-compliant structure exists, but can
be authorized as safe once its use is reviewed on the Authorize dialog. The
strategy cannot be downloaded to the safety controller until all warnings are
authorized.
For example, the ADD function is considered “safe” when it has between 2
and 16 input parameters; in which case, the Functions node icon turns
green. However, the Functions node icon turns yellow with an ADD of 1, 17,
or more input parameters, necessitating review and authorization for use.
• Green - No non-compliances were found when analyzing the POU section.
10. Click OK to return to the IEC61131 Integrity Analyzer dialog. Click Save to
commit the acknowledgement of the non-compliant POUs.
11. Since the analysis is complete, you may close the dialog and return to the Discrete
Control Interface. To complete the analysis, select Cross Reference Analyzer
from the Tools menu.
12. The Cross Reference Analyzer flags, in red, any POU that has changed since the
last analysis, as well as any POU that is dependent upon a changed POU. Before
a download is permitted, all flagged POUs must be acknowledged, indicating that
all changes are known and have been fully tested. To accept the changes made to
the flagged POUs, select Authorize from the Analyze menu.
14. Select the box next to each POU if the change is acceptable. Once the boxes for
all POUs are checked, ensure that the Authorize download box is checked and
click OK to close the dialog.
15. Click Save in the IEC61131 Cross Reference Analyzer to commit the change
acknowledgements.
16. Close the IEC61131 Cross Reference Analyzer once the changes are saved.
• If there is no error message displayed upon exiting the analyzer, you may
proceed to the Download form in the Workbench to download the logic to
the safety controller.
Note: Use the Tools | Authorize Safety Build menu option to automate
the processes of launching the Integrity Analyzer followed by the Cross
Reference Analyzer.
2. Click Get Servers, and select the Universal IO Server in the Server drop down list.
4. Click Download to begin the download process. Answer Yes when asked to
confirm the download.
Note: The Debugger can only attach to the controller in configuration mode
(see Changing Controller Modes).
2. Enter the MAC Address(es) for the devices. If this is for your PC, click the Browse
button and enter Me in the resulting box. The MAC address for your PC will be
automatically filled in. If you wish to declare one or both of the controller COM ports
to be permitted to read data from other devices, enter COM1 or COM2, as
appropriate. If you wish to authorize another PC to write, enter this PC’s MAC
address.
In most cases, you will only enter the LAN A address. However, if you have a PC
with two network cards and both have permission to write data to the controller,
enter one in the LAN A field and the other into the LAN B field. If you wish to grant
access to all devices, use a MAC address of 000000000000 (twelve zeros).
3. For each MAC Address entered, you must decide what types of writes are
permitted:
• Allow Modbus Writes - The device can write Modbus data to the
controller in configuration mode.
• Allow HART Maintenance - The device can use HART passthrough to
make changes to the controller, such as use AMS software.
• Save Retained Variables - The controller monitor changes to data values
from the selected HMI and when any changes occur, saves the values to
flash memory using the internal controller algorithms.
• Allow Workbench Full Control - The device can use the Workbench to
perform downloads and other writes that affect data in the controller.
• Allow Discrete Control Debugger - The device can launch the Discrete
Controller Debugger to view and change data in the controller.
5. Type COM1 into the box and then click Apply and Save to add the COM1 port to
the list of authorized devices.
Note: If the controller has been password protected, the password must be
entered before the download will successfully complete.
Assigning a Keyswitch
The Keyswitch is a physical digital input that can be used to lock the controller so that
mode (between safe and configuration or between configuration and safe) or password
changes cannot be made.
1. Right-click the controller and select Security | Assign/Edit Keyswitch.
2. Double-click the point that you would like to use as the keyswitch from the list of
tags displayed. For our example, use KEYSWITCH, with Key Switch health of
KEYSWITCHOK. Click Apply to make the assignment.
3. You are informed if the assignment is successful and that the configuration must be
downloaded to the controller. You are also asked if you would like to launch the IO
Configurator to download the configuration. Answer Yes at this prompt.
4. When the IO Configurator is launched, click the green traffic light from the toolbar
( ) to go online and then download the configuration to the controller.
5. The status of the keyswitch can now be seen on the Trusted Hosts Table. Open
this form in the Workbench and click Connect. The keyswitch will be shown as
locked or unlocked based on its value when Connect was clicked. If the state
changes, the status will not be automatically updated. You must click Connect
again to initiate the update.
2. Enter the appropriate password and click Switch Mode. If the mode change is
allowed, the alternate mode will automatically be entered. If not, an error message
is displayed to indicate why the mode change was not allowed.
The controller cannot go from configuration mode to safe mode under the following
conditions:
• A channel of a safety module is forced.
• A safety module is unhealthy.
• The keyswitch is unlocked.
• The password is entered incorrectly.
• The Master or Standby controller is unhealthy.
• The Discrete Control Debugger is active.
• The Trusted Hosts table is missing.
• Strategy files and tables were downloaded at different times.
2. Enter the Old Password (or leave blank if no password is currently set).
3. Enter the New Password of at least six characters and then confirm the entry by re-
typing the password and click OK.
4. Answer Yes when asked if you would like to proceed and the password will be set.
This password must now be used when downloading the trusted hosts table or
changing the controller’s mode.
2. Map the tag to Discrete Control. (We have already done this in our example.)
5. The tags are now ready for use in the HMI. Import the tags into the HMI. When a
write is needed, write the appropriate value to the <tag_name>_RQT field. The
<tag_name>_CNF becomes 1. To confirm the value change, set the
<tag_name>_CNF to 0. If you wish to cancel the change, set the
<tag_name>_RQT back to its original value or wait for the confirmation process to
time out.
The following are other tags of interest in the HMI when writing to digitals in safe
mode:
• <controller_name>_AXE_THT has a value of 1 if it is okay for the HMI
to write to a safe digital tag. This means that the HMI PC is in the trusted
host table for the controller and that the keyswitch is unlocked. If these
conditions are not met, the tag has a value of 0 indicating that writes are
not permitted.
• Override Min: The number of seconds before the confirm coil becomes
logic 1 after a new value is given to the corresponding request coil. The
default value for this parameter is 2 seconds.
• Override Max: The timeout period for the safe write process. When a
request coil is given a new value, the confirm coil must transition from
logic 1 to logic 0 in order for the write to be confirmed. The default value
for this parameter is 10 seconds.
Once changes are made to these parameters, the IO configuration must be
downloaded to the controller for activation.
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 – Automatic backups are created for projects every time a
download to a safety controller is performed. Please refer to the Help topic How
to Download a Strategy for more information.
• 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.
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.
Trusted Hosts – The Trusted Host table prevents unauthorized TCP devices from
making changes to data in the controller.
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.