Product Manual 26712

(Revision NEW, 7/2013)

Original Instructions

ProTech® GAP™ Manual

A graphical tool for programming the SX, TPS, and MSM

versions of the ProTech® product family

Software Manual
 Read this entire manual and all other publications pertaining to the work to be
performed before installing, operating, or servicing this equipment.
Practice all plant and safety instructions and precautions.
General
Precautions Failure to follow instructions can cause personal injury and/or property damage.

This publication may have been revised or updated since this copy was produced.
To verify that you have the latest revision, check manual 26311 , Revision Status &
Distribution Restrictions of Woodward Technical Publications, on the publications
Revisions page of the Woodward website:
www.woodward.com/publications

The latest version of most publications is available on the publications page. If

your publication is not there, please contact your customer service representative
to get the latest copy.

Any unauthorized modifications to or use of this equipment outside its specified

mechanical, electrical, or other operating limits may cause personal injury and/or
property damage, including damage to the equipment. Any such unauthorized
Proper Use modifications: (i) constitute "misuse" and/or "negligence" within the meaning of
the product warranty thereby excluding warranty coverage for any resulting
damage, and (ii) invalidate product certifications or listings.

If the cover of this publication states "Translation of the Original Instructions"

please note:
The original source of this publication may have been updated since this
Translated translation was made. Be sure to check manual 26311 , Revision Status &
Publications Distribution Restrictions of Woodward Technical Publications, to verify whether
this translation is up to date. Out-of-date translations are marked with . Always
compare with the original for technical specifications and for proper and safe
installation and operation procedures.

Revisions—Changes in this publication since the last revision are indicated by a black line
alongside the text.

Woodward reserves the right to update any portion of this publication at any time. Information provided by Woodward is
believed to be correct and reliable. However, no responsibility is assumed by Woodward unless otherwise expressly
undertaken.
Manual 26712
Copyright © Woodward 2013
All Rights Reserved
Manual 26712 ProTech GAP Manual

Contents

WARNINGS AND NOTICES ............................................................................ 4

ELECTROSTATIC DISCHARGE AWARENESS .................................................. 5
CHAPTER 1. OVERVIEW ............................................................................... 6
Introduction .............................................................................................................6
General Information ................................................................................................6
CHAPTER 2. INSTALLATION OF SOFTWARE TOOLS FOR PROTECH ................ 8
Tools Required for using GAP for ProTech ............................................................8
Installing ToolKit Components ................................................................................8
Installing ProTech/MicroNetSM Editor and NetSim Coder 1.0 & 2.0 .....................9
Installing NetSim ...................................................................................................12
Installing Visual C++ .............................................................................................15
CHAPTER 3. BUILDING AN APPLICATION .................................................... 18
Introduction ...........................................................................................................18
System Overview Diagram ...................................................................................18
Choosing a Template ...........................................................................................19
Starting a New GAP Project .................................................................................20
Structuring Your GAP Program ............................................................................24
Creating Settings Files for ProTech .....................................................................25
CHAPTER 4. LINKING THE GAP PROGRAM TO THE HARDWARE ................... 28
Communicating via GAP with the ProTech ..........................................................28
CHAPTER 5. LOGIC SIMULATION USING NETSIM......................................... 31
Sequence Steps to Simulate Using NetSim .........................................................31
CHAPTER 6. APPLICATION EXAMPLES ....................................................... 39
Overview ...............................................................................................................39
Example #1—Application SX_PROG1_DI – ........................................................39
Example #2—Application SX_PROG1_AI – ........................................................41
Example #3—Application TPS_VI_PROG1 – ......................................................44
CHAPTER 7. SERVICE OPTIONS ................................................................. 46
Product Service Options .......................................................................................46
Woodward Factory Servicing Options ..................................................................47
Returning Equipment for Repair ...........................................................................47
Replacement Parts ...............................................................................................48
Engineering Services............................................................................................48
How to Contact Woodward ...................................................................................49
Technical Assistance ............................................................................................49
APPENDIX. PROTECH TEMPLATE GAP BLOCKS ......................................... 50
Configure Blocks ..................................................................................................50
Process Blocks .....................................................................................................59

Woodward 1
ProTech GAP Manual Manual 26712

Illustrations and Tables

Figure 1-1. Programming & Configuration Tool......................................................7

Figure 1-2. GAP Programming & Configuration .....................................................7
Figure 2-1. GAP Setup Screen ...............................................................................9
Figure 2-2. GAP Confirmation Screen ....................................................................9
Figure 2-3. GAP License Screen ..........................................................................10
Figure 2-4. GAP Installation Screen .....................................................................10
Figure 2-5. GAP Installation Complete Screen ....................................................10
Figure 2-6. GAP Templates Screen .....................................................................11
Figure 2-7. GAP Templates Screen .....................................................................11
Figure 2-8. NetSim Extracting Screen ..................................................................12
Figure 2-9. NetSim Setup Screen.........................................................................12
Figure 2-10. NetSim Shortcut Screen ..................................................................12
Figure 2-11. NetSim License Screen....................................................................13
Figure 2-12. NetSim Destination Folder Screen...................................................13
Figure 2-13. NetSim Ready to Install Screen .......................................................13
Figure 2-14. NetSim Installing Screen ..................................................................14
Figure 2-15. NetSim Setup Complete Screen ......................................................14
Figure 2-16. NetSim Control Executive ................................................................14
Figure 2-17. Visual C++ Setup Screen .................................................................15
Figure 2-18. Visual C++ License Screen ..............................................................15
Figure 2-19. Visual C++ Installation Options ........................................................16
Figure 2-20. Visual C++ Destination Folder Screen .............................................16
Figure 2-21. Visual C++ Installation Progress Screen .........................................16
Figure 2-22. Visual C++ Setup Complete Screen ................................................17
Figure 3-1. Software Functional Interfacing Overview .........................................18
Figure 3-2. Selecting a Template .........................................................................19
Figure 3-3. New GAP Project ...............................................................................21
Figure 3-3a. New GAP Project .............................................................................21
Figure 3-4. SYS_INFO block ................................................................................22
Figure 3-5. SYS_INFO block parameters .............................................................22
Figure 3-6. Logic blocks .......................................................................................23
Figure 3-7. Open/Save Project Dialog Box ..........................................................24
Figure 3-8. Failed completeness check ................................................................26
Figure 3-8a. Failed completeness check ..............................................................26
Figure 3-9. Successful completeness check ........................................................26
Figure 3-10. Successful completeness check ......................................................27
Figure 4-1. Programming & Configuration Tool....................................................28
Figure 4-2. Successful GAP upload to ProTech...................................................29
Figure 4-3. CRC Fingerprint Module C (B not loaded) .........................................29
Figure 4-4. CRC Fingerprint on All Modules ........................................................30
Figure 5-1. GAP Menu Selection to Create NetSim Code ...................................31
Figure 5-2. GAP Completeness Check and coder Launch ..................................32
Figure 5-3. GAP Coder Dialog Box ......................................................................32
Figure 5-4. NetSim Keystone Box ........................................................................33
Figure 5-5. NetSim Keystone Build Complete ......................................................33
Figure 5-6. Keystone Error Pop-Up ......................................................................33
Figure 5-7. NetSimCE Window (Windows XP OS) ..............................................34
Figure 5-8. NetSimCE Window (Windows 7 OS) .................................................34
Figure 5-9. NetSimCE Start and Stop Communications ......................................34
Figure 5-10. NetSimCE Communication Window ................................................35
Figure 5-11. GAP in Monitor/Simulate Mode........................................................35
Figure 5-12. GAP in Monitor/Simulate Mode........................................................36
Figure 5-13. Cybersecure Pop-up & Error Box ....................................................36

2 Woodward
Manual 26712 ProTech GAP Manual

Illustrations and Tables

Figure 5-14. SOS Servlink OPC Server Window .................................................36

Figure 5-15. SOS Servlink OPC Server Window .................................................37
Figure 5-16. NetSim Multi-View Variables Window ..............................................37
Figure 5-17. NetSim Multi-View Variables Window ..............................................38

The following are trademarks of Woodward, Inc.

GAP
MicroNet
NetSim
ProTech

The following are trademarks of their respective companies:

Modbus (Schneider Automation Inc.)
Windows (Microsoft Corporation)

Woodward 3
 ProTech GAP Manual Manual 26712

Warnings and Notices

Important Definitions
This is the safety alert symbol. It is used to alert you to potential
personal injury hazards. Obey all safety messages that follow this
symbol to avoid possible injury or death.
 DANGER—Indicates a hazardous situation which, if not avoided, will result
in death or serious injury.
 WARNING—Indicates a hazardous situation which, if not avoided, could
result in death or serious injury.
 CAUTION—Indicates a hazardous situation which, if not avoided, could
result in minor or moderate injury.
 NOTICE—Indicates a hazard that could result in property damage only
(including damage to the control).
 IMPORTANT—Designates an operating tip or maintenance suggestion.

The engine, turbine, or other type of prime mover should be

equipped with an overspeed shutdown device to protect against
runaway or damage to the prime mover with possible personal injury,
Overspeed / loss of life, or property damage.
Overtemperature / The overspeed shutdown device must be totally independent of the
Overpressure prime mover control system. An overtemperature or overpressure
shutdown device may also be needed for safety, as appropriate.

The products described in this publication may present risks that

could lead to personal injury, loss of life, or property damage. Always
wear the appropriate personal protective equipment (PPE) for the job
Personal Protective at hand. Equipment that should be considered includes but is not
limited to:
Equipment
 Eye Protection
 Hearing Protection
 Hard Hat
 Gloves
 Safety Boots
 Respirator
Always read the proper Material Safety Data Sheet (MSDS) for any
working fluid(s) and comply with recommended safety equipment.

Be prepared to make an emergency shutdown when starting the

engine, turbine, or other type of prime mover, to protect against
runaway or overspeed with possible personal injury, loss of life, or
Start-up property damage.

4 Woodward
Manual 26712 ProTech GAP Manual

Electrostatic Discharge Awareness

Electronic controls contain static-sensitive parts. Observe the
following precautions to prevent damage to these parts:
 Discharge body static before handling the control (with power to
the control turned off, contact a grounded surface and maintain
Electrostatic contact while handling the control).
Precautions  Avoid all plastic, vinyl, and Styrofoam (except antistatic versions)
around printed circuit boards.
 Do not touch the components or conductors on a printed circuit
board with your hands or with conductive devices.
To prevent damage to electronic components caused by improper
handling, read and observe the precautions in Woodward manual
82715, Guide for Handling and Protection of Electronic Controls,
Printed Circuit Boards, and Modules.

Follow these precautions when working with or near the control.

1. Avoid the build-up of static electricity on your body by not wearing clothing
made of synthetic materials. Wear cotton or cotton-blend materials as much
as possible because these do not store static electric charges as much as
synthetics.
2. Do not remove the printed circuit board (PCB) from the control cabinet
unless absolutely necessary. If you must remove the PCB from the control
cabinet, follow these precautions:
 Do not touch any part of the PCB except the edges.
 Do not touch the electrical conductors, the connectors, or the
components with conductive devices or with your hands.
 When replacing a PCB, keep the new PCB in the plastic antistatic
protective bag it comes in until you are ready to install it. Immediately
after removing the old PCB from the control cabinet, place it in the
antistatic protective bag.

Woodward 5
ProTech GAP Manual Manual 26712

Chapter 1.
Overview

Introduction
This manual will provide the following information for the user regarding the use
of the ProTech GAP tool which is an enhanced (optional) way to program and
configure additional safety logic functions into the ProTech family of Overspeed
Protection products.
 Installation of the additional Woodward software tools required
 Step by step instructions to build custom logic for the ProTech
 Details on how to load & confirm (graphical vs. hardware) the device
settings
 How to simulate & test graphical logic on a PC and generate settings files
 Numerous application examples to help users with custom logic designs for
safety related functions, or just additional monitoring parameters

General Information
GAP is Woodward’s Graphical Application Programmer, (3rd Generation),
software tool. It is a Windows based, high-level, block-oriented programming
language designed for simple and quick implementation of difficult control
strategies. GAP blocks are proven pieces of software, and you don’t have to be a
computer programmer to program in GAP. GAP is part of the Woodward
Integrated Development Environment which includes ToolKit and NetSim, and is
the primary programming tool for our high-end electronic control products.

The ProTech family has some products that allow you to add site-specific
input/output signals and implement unique software logic related to these signals.
This can be done through the Programming and Configuration Tool (PCT), based
on Woodward’s ToolKit program. There are however, some limitations with this
method:
 No graphical view of the application program
 No ability to simulate and test/debug the program
 No error checking prior to loading the program into the ProTech device

As an enhancement to the ProTech family, a tool based on Woodward’s GAP

application programming environment has been created. This tool provides the
following:
 Graphical view of entire application
 Completeness check to ensure the program will be accepted by the device
 Documented feedback of the ProTech CRC codes to ensure program
‘fingerprint’ verifying laptop GAP program & installed ProTech settings
 GAP Block help clarifying function and input/output fields of each block
 Built-in simulation on the user PC to allow testing/debugging of logic
 Simulation that allows manual entry (control) of Input signals

6 Woodward
Manual 26712 ProTech GAP Manual

Figure 1-1. Programming & Configuration Tool

Figure 1-2. GAP Programming & Configuration

Woodward 7
ProTech GAP Manual Manual 26712

Chapter 2.
Installation of Software Tools for ProTech

Tools Required for using GAP for ProTech

The ProTech GAP is a special application of the Woodward GAP tool specifically
for ProTech. It is a combination of Woodward’s ToolKit software and a special
ProTech application program.

To install the GAP Tool, locate/obtain the ProTech GAP Installation CD provided
with each ProTech (ProTech-SX, ProTechTPS, or MicroNet Safety Module
[MSM]). Alternatively, the ProTech/MicroNetSM Editor and NetSim Coder 1.0 &
2.0 can be downloaded from Woodward’s Internet website:
www.woodward.com/software

In order to use the ProTech GAP tool, the following Woodward programs must
first be loaded on the target PC.
 ToolKit version 3.6 or later
 ProTech Service Tool
 ProTech/MicroNetSM Editor and NetSim Coder 1.0 & 2.0
 NetSim 1.5 Control Executive or later
 Microsoft Visual C++ version 6.00 2010 Express compiler

Installing ToolKit Components

It is important to load the ToolKit components first, and establish a connection
with your unit. This will insure that the user is able to communicate with the
device, and allow them to load the .wset file that the GAP programming tool will
create (which is described in detail in the following chapter).

A version of ToolKit install is available on the CD, but the latest version can
always be downloaded from the Woodward website. The service tool for your
particular device will need to be downloaded from the Woodward website.

 Install ToolKit version 3.6 ToolKit version 3.6 or later (installed in default
directory) with at a minimum an Advanced-Runtime license (Woodward
Part# 8447-5002).
ToolKit Developer license (Woodward Part# 8928-5016) will work as well,
but is not required.
NOTE: This program must be opened at least one time before GAP can
use it. The correct ToolKit version is supplied with the installer CD,
provided with the product.

 Install the service tool for your particular device (SX, TPS, MSM) again
allowing the install program to install in the default directory.
o SX (Woodward Part# 9927-1837)
o TPS (Woodward Part# 9927-1684)
o MSM (Woodward Part# 9927-1838)

Once these tools have been installed, refer to “Using the Programming and
Configuration Tool” section in Chapter 10 of the service manual to connect to the
device.
 SX service manual 26546V2
 TSP service manual 26501V2
 MSM service manual 26547V2
8 Woodward
Manual 26712 ProTech GAP Manual

Installing ProTech/MicroNetSM Editor and NetSim

Coder 1.0 & 2.0
This section will step the user through the process of installing the
ProTech/MicroNetSM Editor and NetSim Coder 1.0 & 2.0. The GAP tool will
allow the user to graphically program the ProTech for system trips, alarms, and
any custom logic need to configure the ProTech protection device.

 Start the executable program by double clicking

GAPProTech307P1_NEW.exe
(or selecting Run, if installing from the Woodward Software page)

 On the Setup screen select Next

Figure 2-1. GAP Setup Screen

 On the Confirmation screen select Next

Figure 2-2. GAP Confirmation Screen

Woodward 9
ProTech GAP Manual Manual 26712
 On the License Agreement screen select I Agree, and then next

Figure 2-3. GAP License Screen

 The installation will begin

Figure 2-4. GAP Installation Screen

 When Installation is Complete, select Close

Figure 2-5. GAP Installation Complete Screen

10 Woodward
Manual 26712 ProTech GAP Manual
 After the GAP tool has been installed, find it in All Programs – Woodward
– GAP3 and click on the GAP3 Icon . This will open up
the GAP program to verify that it was installed correctly.
 In the GAP3 program select File – New – Project and verify that the ProTech
TPS, ProTech SX and MicroNet SM (MSM) are available (versions numbers
can advance so there might be more than shown below)

 On the template Pop-Up select the “More” tab and check show all templates.

Figure 2-6. GAP Templates Screen

 Now all templates should be visible.

Figure 2-7. GAP Templates Screen

Woodward 11
ProTech GAP Manual Manual 26712

Installing NetSim
This section will step the user through the process of installing NetSim, which
can be used to run a simulation, to debug a configuration, prior to loading it into
the ProTech.

Installing NetSim Control Executive (1.5 or later)

 Start the executable program by double clicking netsim_x_x_x.exe

(Or selecting Run, if installing from the Woodward Software page)

 NetSim setup will begin Setup

Figure 2-8. NetSim Extracting Screen

 On the Welcome screen select Next

Figure 2-9. NetSim Setup Screen

 On the Configure Shortcuts screen check the box if you want a shortcut
installed on your desktop

Figure 2-10. NetSim Shortcut Screen

12 Woodward
Manual 26712 ProTech GAP Manual
 On the End User License Agreement screen select, I accept the term in
the License Agreement

Figure 2-11. NetSim License Screen

 This screen determines where NetSim will be installed. It is

recommended to use this default path

Figure 2-12. NetSim Destination Folder Screen

 NetSim is ready to be installed, select Install

Figure 2-13. NetSim Ready to Install Screen

Woodward 13
ProTech GAP Manual Manual 26712
 NetSim is being installed

Figure 2-14. NetSim Installing Screen

 Select Finish to complete the installation

Figure 2-15. NetSim Setup Complete Screen

 After the GAP tool has been installed, find it in All Programs – NetSim –
NetSim CE, or on the desktop if that option was selected earlier. Click on
the NetSim CE icon to open up NetSim Control Executive to verify that it
was installed correctly
.

Figure 2-16. NetSim Control Executive

 This competes the installation of NetSim. How to use this tool is

explained in detail one of the following chapters.

14 Woodward
Manual 26712 ProTech GAP Manual

Installing Visual C++

Installing Microsoft Visual C++ version 6.00 2010 Express compiler, free from
Microsoft.

This will allow the user to ‘compile’ the ProTech GAP application settings
program to be executed on their PC by NetSim. Using NetSim the user can
perform program debugging on their application, prior to loading the settings into
the ProTech.

 Follow the link below to download Visual C++ 2010 Express

http://www.microsoft.com/visualstudio/eng/products/visual‐studio‐express‐products

 Welcome screen. Uncheck the box to decline setup experiences

Figure 2-17. Visual C++ Setup Screen

 License Terms, select I have read and accept the license terms

Figure 2-18. Visual C++ License Screen

Woodward 15
ProTech GAP Manual Manual 26712
 Installation Options. Suggest to uncheck SQL server option, it is not
needed

Figure 2-19. Visual C++ Installation Options

 Destination Folder. Suggest to use default location, but it is not

necessary

Figure 2-20. Visual C++ Destination Folder Screen

 Download in Progress

Figure 2-21. Visual C++ Installation Progress Screen

16 Woodward
Manual 26712 ProTech GAP Manual
 Setup complete, select exit

Figure 2-22. Visual C++ Setup Complete Screen

 This competes the installation of Microsoft Visual C++

Woodward 17
ProTech GAP Manual Manual 26712

Chapter 3.
Building an Application

Introduction
The ProTech GAP template allows you to create a custom application program
and code it for simulation on your PC. Once you are satisfied with the program, a
valid Settings File (.wset) can be created from the application. This file can then
be uploaded into the target ProTech device through the ToolKit Service tool.
Upon successful completion of the loading of the settings file, the ProTech will
return to the GAP application the exact CRC (cyclical redundancy checksum)
values related to each program section (in addition to an overall CRC).

Below is a system overview diagram of how the GAP created application

interfaces with the current ProTech hardware and service tool.

System Overview Diagram

Figure 3-1. Software Functional Interfacing Overview

It is important to note a few key points about this process:

1. Only “settings” files are loaded into the ProTech (unlike other Woodward
products using GAP programs where a compiled/executable program is
loaded into the device).
2. The GAP template requires the Service Tool to send/retrieve information
to/from the device.
3. ProTech GAP tool has NO safety related requirements or specifications – all
of these requirements are met by the ProTech hardware.
4. The compiling of a ProTech GAP application will be for NetSim only, since
there is no compiling for the ProTech hardware.
5. Current templates exist for the SX, TPS, and MicroNet Safety Module.

18 Woodward
Manual 26712 ProTech GAP Manual

Choosing a Template
The first step in creating a new project (program) in GAP is to select the desired
Template. Templates contain the available program blocks that the user can
select to create program logic for a specific target hardware product.

Figure 3-2. Selecting a Template

NOTE: This Template list likely contains many more template options than you
will see.

Version 1.00 Templates

For the ProTech family the version 1.00 templates are for the non-voted input
(original released) versions. These templates do not have any Redundancy
Manager type blocks available because those products did not have the ability to
share input values & status between the kernel modules. For the SX Product line
there is only a 1.00 template at this time – if additional block types and functions
are added in the future, then a new template version will be released.

The ProTech SX application examples will be in this template.

Version 2.00 Templates

For the ProTech family the version 2.00 templates are for the voted input
versions (released in 2013). These products have the ability to share input signal
information between the isolated kernel modules (A, B & C) of the TPS and MSM
products.

Woodward 19
ProTech GAP Manual Manual 26712
The ProTech TPS application examples will be in this template.

NOTE: This manual will proceed with instructions using the Version 2.0
template, but the same steps will work for either template.

Version 2.00 Templates

In the ProTech templates, categories and block names are automatically created
for each block as it is placed on the sheet. This is convenient for a few reasons.

1. For each type of block, there is only a specific number of blocks available
(for example there are only 30 total delay blocks).
2. This naming convention is used by the ToolKit service tool programming,
therefore it must be followed.
3. Each individual block can be viewed during runtime on the ProTech front
panel monitor screen.

Starting a New GAP Project

Differences of ProTech GAP versus other GAP programmable
platforms
For those users who have experience using GAP on other Woodward products,
there are some major difference in the ProTech GAP tool that make in unique.

ProTech GAP -
 User does not define Block names or Categories – these are pre-defined
to match the display screen at runtime. Use block descriptions &
comments to describe functions where needed.
 There are NO Rate groups – all blocks execute in each cycle of the
minor frame timer. The identifier in parenthesis give the module that
block is found in (A, B, or C)
 There are NO tunables, values are changed in configuration mode only
via the front panel display or the service tool
 Different block colors reflect which module they are in, not rate group
 Does not link to a compiler for creating executable code to run in the
ProTech – it will only produce “setting” files (.wset files) that are identical
to the Service Tool settings files and are what is loaded into the
hardware
 Does support a compiler for creating a simulation file that is supported by
Woodward’s NetSim product.
 Does NOT support monitoring of live values from the ProTech hardware
– you must use the front panel display to see live block values on a
powered unit, however NetSim will support the monitoring of live values
during simulation (via SOS)

Getting Started
When you first Launch the GAP tool, you may see a dialog box as in figure 3.3
below, and will be prompted for a file name and location, this for opening an
existing project. If you get this box hit Cancel and you should see the GAP tool
open and be ready for a new project/program as shown in Figure 3-3a below.

20 Woodward
Manual 26712 ProTech GAP Manual

Figure 3-3. New GAP Project

Figure 3-3a. New GAP Project

After reaching this point Select File/New/Project. You should now be prompted
for the selection of a template as shown previously in Figure 3-1. For our
example we selected ProTech TPS 2.00.

If this is the only Woodard GAP product you have, or just want to have all new
programs start with this template you can set this up as the default template by
using the “Startup Options/Select Default Startup Template” under the File menu.
Note that you need to restart GAP to get the ProTechTPS 2.00 Template to
display in the RH window.

Next go to the Block Template Tree window, expand the Configure group and
drag the SYS_INFO_TPS block into the Active Sheet window as shown in the
Figure below.

NOTE: More detail about individual GAP blocks can be found in the
Appendix of this manual and in the GAP Help pull-down tab under Block
Help.

Woodward 21
ProTech GAP Manual Manual 26712

Figure 3-4. SYS_INFO block

You will notice the block name (top) and the block type (bottom) are in RED. This
is because you must select which module (A, B, or C) this block is assigned to
(shown in red as xx). To do this double click on the block to open it and select A,
B or C for the ProTechModule field.

Figure 3-5. SYS_INFO block parameters

22 Woodward
Manual 26712 ProTech GAP Manual
Doing this will automatically name the block, convert the color and eliminate the
Red errors.

Some blocks are unique and must be assigned to a specific module (such as this
one) while others can be declared as (ALL) meaning that they will be duplicated
automatically in each of the 3 kernel modules.

The default colors for each module declaration are:

ALL Black
A Green
B Blue
C Purple

Select this block and Copy/Paste 2 more of these blocks on the page and
change them to be assign to modules B and C.

Additional blocks are added in the same way. The input fields will first appear as
Red X’s (required input fields) or with default values.
These input fields must be programmed with one of the following:
1. Fixed Value
2. Output from another block

There are two ways to program these input fields.

Clicking on the input field, will allow the user to enter a value or select a valid
input option. GAP will only show valid inputs for the field type (Boolean or
analog), such as Boolean values for logic gates.

The user can also click on the output stem of a block and drag a ‘net’ line to the
input of another block, if it is the correct field type. If it is not the correct data type
then GAP will not allow the user to make the connection. A given block can have
its stem branch to many other blocks.

Figure 3-6. Logic blocks

NOTE: For more detail about how to use the GAP editor, use the Editor
Help found under the Help pull-down tab.

Woodward 23
ProTech GAP Manual Manual 26712

Saving a GAP Project

Now Select File/Save Project and you will get a dialog box as shown. In the
example below we used TPS_TEST as the file name and Woodward_ProTech
as the folder location.

NOTE: The words program and project both refer to the <filename>.GAP3 file
that GAP creates. For simplicity we will use the word program from here forward.

Figure 3-7. Open/Save Project Dialog Box

There will only be 1 GAP program to maintain that will contain all of the
application settings for the ProTech. Once complete, the program will generate 3
separate settings files, that each get loaded into the ProTech modules A, B & C.

To return to work on this program later, you can simply double click on the GAP3
file and it will automatically be associated with the GAP editor tool.

Quick Steps to Creating & Saving a GAP Program

1. Launch GAP to create a new project, or open an existing project/program
2. In the Palette window (upper right side), there are 2 groups of blocks,
Configure and Process, as well as a full list (alphabetic).
3. Begin building an application by dragging blocks onto the active sheet
(Sheet window) and connecting the inputs and outputs. Note: It may be
helpful to have the GAP Help window open if you want to check properties
of the blocks being placed on the active sheet. You can press the shortcut
keys F1 for Block Help or Ctrl+F1 for Editor Help.
4. You can save your project at any time during this process.

Structuring Your GAP Program

GAP is primarily used to program the logic section of the ProTech. However, the
entire application, which includes logic, speed, test conditions, and Modbus, is
available through GAP. In general, if using the GAP tool to maintain the program
it is best to follow the structure of the example programs included on the CD,
which include blocks that will contain some of the settings that are done typically
through the front display panel keypad (such as start logic, speed inputs and
overspeed settings).

24 Woodward
Manual 26712 ProTech GAP Manual

Logic Organization
The following is the general construction of the example programs that are
provided and shown in this manual. The sheet number refer to the TPS sample
program TPS_VI_Prog1.200

1. Project Cover sheet – use the title block to identify the project/jobsite/part
number – this will also provide revision control for changes
2. System Information blocks (sheet 1) that provide the CRC ‘fingerprint’
from the target hardware
3. Required/Recommended Blocks (sheet 2) good practice to have all of
these blocks present in your application so that all critical settings are
contained in the GAP program
4. Logic for Safety Instrumented Functions (SIF) – typical Input to Output
(left to right) flow of logic on the page – using ‘net’ connections between
block outputs and inputs for ease of readability (on a sheet)
5. Logic for non-critical use such as monitoring or test routines
6. Alarm and Trip summary Latches (sheets 7 & 8)

Programmer Comments
It is good practice to use good notes and programmer comments as much as
reasonable when creating a program. In the example programs provided all 3 of
the Comment types are utilized –
 Line Text - to outline and highlight a section of code
 Comment Text Box – beige box container for text
 Rich Text – Enhanced format (color/font/size ) text editor for

Therefore it is good programming practice to add the blocks shown on

the first sheets of each example to the ProTech GAP tool application, so
that ALL settings are documented on the GAP sheets and included in
the .wset file.

Creating Settings Files for ProTech

Completeness Check
Once the GAP program is complete the first step to making settings files for the
ProTech is to run a check that all required input fields have been programmed.
The completeness check can be performed after the application is built, or at any
time during the build of the application. To run a completeness check, select File/
Compile/Completeness Check Only. A dialog box will open, giving the results of
the completeness check. You can also press the shortcut key F5 to run a
completeness check.

This check will detect:

Warnings – shown with a yellow caution icon – items to be aware of, they may or
may not be a problem with your program, such as a block with no outputs used.
Faults – shown with a red icon – items that must be correct before a settings file
or a simulation file can be created.

Woodward 25
ProTech GAP Manual Manual 26712

Figure 3-8. Failed completeness check

A program will not compile with Faults, Red icon.

A program will compile with warnings, acknowledge screen below

Figure 3-8a. Failed completeness check

A successful completeness check, without warnings is shown below.

Figure 3-9. Successful completeness check

Build a .wset file with GAP

Before a .wset file can be created by GAP, you must have the correct ToolKit
service tool (Programming & Configuration Tool) installed on the PC. Refer to the
correct chapter in the ProTech manual to install this program and verify that the
service tool can correctly communicate to the ProTech.

Method 1—Only option if you are not connected to the unit.

To create a .wset file, select check File/Compile/Create .wset file. You will be
prompted to select the Sid Specification file. Select the correct Sid file for the
version of software running on your ProTech. The software version can be found
on the front panel display on the ProTech under the Monitor Menu/Module
Information. Once selected, a completeness check will be run first and, if passed,
a .wset file will be created for each module.

26 Woodward
Manual 26712 ProTech GAP Manual

Figure 3-10. Successful completeness check

For the ProTech SX one file will be created, for the TPS and MSM it will create 3
.wset files. It there were warnings found during the completeness check, then
there will be an additional prompt that pops-up to confirm that it is OK to make
the .wset files.

These settings files can now be loaded into the ProTech at any time with the use
of the ToolKit Programming & Configuration Tool.

Whenever the ProTech GAP tool is used to create the settings file (.wset), it will
overwrite all settings that exist in the ProTech device. It will not do a ‘partial’ load
of just the customer-specific logic that was created.

For Example: There is no requirement to have the SPEED_SX block in a

ProTech GAP tool application for a ProTech SX device. If there is no
SPEED_SX block created in the application, then the .wset file that gets
created will set all of these input field settings to default, such as the
Overspeed setting OVRSPD = 100 rpm. If this setting had been set to 1000
rpm on the device originally, then this setting will be overwritten with 100
when this .wset file is loaded.

Woodward 27
ProTech GAP Manual Manual 26712

Chapter 4.
Linking the GAP program to the Hardware

Communicating via GAP with the ProTech

As was previously mentioned, refer to the correct chapter in the ProTech manual
to install the ToolKit service tool (Programming & Configuration Tool) program
and verify that the service tool can correctly communicate to the ProTech.

Figure 4-1. Programming & Configuration Tool

Modules must be in the “Tripped” state in order to download a .wset file to a

ProTech module. You will have to enter a password to download the .wset file to
the ProTech. The default password for Config level changes is “AAAAAA”.

Loading the .wset file from GAP

Method 2—Ideal option if you are connected to the unit.
Once the service tool is connected to the ProTech the ideal method of loading
these settings files is to load them directly from GAP. This is done via the
File/Complie/Create and Upload .wset file.

To do this first setup an active serial communication link between the service tool
to the ProTech device.

Secondly in the GAP menu File/Compile/ProTech/MicroNetSM Port type in the

correct COM port number – this should be the same COM port that the service
tool is using. Typical laptops today do not have serial ports so usually a USB-to-
Serial convertor is used, which may be assigned to a port other than COM1.

Thirdly select File/Complie/Create and Upload .wset file and the GAP will run
through the following steps –
1. Prompt for the correct Sid specification (press OK)
2. Perform the completeness check
3. Prompt for the ProTech password (default = AAAAAA then OK)
4. Identify the module (A, B, or C) and Load the correct .wset file
5. Retrieve the CRC Fingerprint and load it into the GAP SYS_INFO
6. Show completeness check dialog box with 4 completed steps

28 Woodward
Manual 26712 ProTech GAP Manual

Figure 4-2. Successful GAP upload to ProTech

You will need to do this 1 module at a time on TPS/MSM, however the GAP tool
will know which settings file to load and return the “CRC Fingerprint” information
of the module that was loaded into the SYS_INFO block in the GAP program.

CRC Fingerprint
It can be extremely critical for a customer, especially an OEM with a unit under
warranty, to have absolute confirmation of the settings in a SIL3 safety device
protecting their rotating equipment. The ProTech CRC Fingerprint does this by
automatically documenting these verification codes in the GAP program.

Figure 4-3. CRC Fingerprint Module C (B not loaded)

Once all modules have been loaded and all CRC’s retrieved the GAP can the
Saved (via File/Save Project) and the SYS_INFO codes will be secure.

Woodward 29
ProTech GAP Manual Manual 26712
NOTE: If any change is made to the GAP after this and the GAP is saved
again, the CRC codes will be blanked out since there is no longer absolute
assurance that the GAP is identical to the settings in the ProTech.

CRC Differences
If all of the logic (including input & output signals, Home screen declarations,
alarm & trip latches….) is exactly the same, it is possible that the CRC codes
between the 3 modules (TPS/MSM) will be identical.

However, it is most likely that the CRC codes between the modules will be
different. This is due to the fact that there will likely be slight logic gate variations
between modules to correctly annunciate signal faults in the system and clarify
the health status of redundancy manager blocks in all modules.

As you can see from the screen shot below, the GAP date and time are identical,
but the Overview CRC code is different between the 3 modules. If you check
down the list of program sections, you will see that the only difference between
the 3 is the DISPLAY_CRC code, meaning that the Home Screen block has
some different assignments in their input fields.

Figure 4-4. CRC Fingerprint on All Modules

It should be noted that unique Signal identifiers, like DeviceTag ID’s or Input
descriptions are NOT considered in the CRC codes. These items are expected to
be different between the modules so that field signals can be clearly identified.

30 Woodward
Manual 26712 ProTech GAP Manual

Chapter 5.
Logic Simulation Using NetSim

Sequence Steps to Simulate Using NetSim

Compile the GAP
Once you have a complete application that passes the Completeness Check, you
are ready to create simulation code that can run on your laptop so you can test
the application you have created. This simulation package will give the developer
the ability to see live values in the GAP program. Using NetSim the developer
can manipulate inputs into the application, and view the results. This is useful in
de-bugging the application, before loading and testing it out on the actual
hardware. This simulation tool is NOT a substitute for testing all of the
functionality on the target device.

This Logic simulation package is intended to help the developer de-

bug and test the application. The final application MUST be tested on
the actual hardware to ensure that all safety functions operate as
intended.

Using the File menu, select Compile/Compile for Simulation/Code with

CoderSim.

Figure 5-1. GAP Menu Selection to Create NetSim Code

Woodward 31
ProTech GAP Manual Manual 26712
This tool will open a completeness check box and then coder box (like shown
below) and create a file that NetSim can use to simulate the GAP program that
was created.

Figure 5-2. GAP Completeness Check and coder Launch

Figure 5-3. GAP Coder Dialog Box

Constructing the Simulation IO Database

These next steps will create a database map for NetSim. This will provide
NetSim handles for manipulating inputs and observing outputs in NetSim during
simulation.
Launch the Keystone tool from the Start/All Programs/NetSim programs folder
and the following dialog box should appear.

NOTE: This step is only required when Input or Output Signal blocks have
been added or deleted. It is not necessary to re-run keystone if only logic
block changes have been made to the program.

Click the Location 1 button and use the browser window to locate the
directory/folder where your GAP program file is located. Click OK on the desired
folder and it will load that path into the window as shown below.

Note: If the path does not appear in the window to the right of the location
button, verify that you have compiled and that the location folder contains
the files tmp_itab & tmp_otab.

32 Woodward
Manual 26712 ProTech GAP Manual

Figure 5-4. NetSim Keystone Box

Click the Build button and Keystone will create the necessary files to use in the
following steps. Keystone builds input and output tabs for NetSim (shown in
Figure 5-16 below).

Figure 5-5. NetSim Keystone Build Complete

Note: If you have not programmed any RELAY_OUT block (relay outputs)
Keystone will display this error message below. This will not prevent the
simulation from working; it is only an indication that there will not be an
Output Switches tab in NetSim.

Figure 5-6. Keystone Error Pop-Up

When this is complete, close this dialog box, return to GAP.

Woodward 33
ProTech GAP Manual Manual 26712

Testing via Simulation with Monitor GAP

From the Monitor menu, Select Monitor/Simulate ► Simulate (NetSim).This will
open a NetSim Control Executive (NetSimCE) dialog box like one of the figures
below, depending on your operating system.

Figure 5-7. NetSimCE Window (Windows XP OS)

Figure 5-8. NetSimCE Window (Windows 7 OS)

To populate live values on your GAP program, follow one of the following
procedures, depending on your computer’s Operating System.

For both XP & Windows 7, Stop communications:

Click the ◄COM arrow if red, to stop communications
(If the ►COM arrow is green, then Communications are already stopped)

Figure 5-9. NetSimCE Start and Stop Communications

Go to the communications menu and select configure. In the Communication

Setup window click on Servlink port, click the Enable box and select TCP as the
medium as shown below.

34 Woodward
Manual 26712 ProTech GAP Manual

Figure 5-10. NetSimCE Communication Window

Click Apply, then OK. Now start communications (►COM)

For XP –
Nothing else is required, simulated values should appear in GAP.

For Windows 7 –
The Woodward SOS Servlink OPC Server must be used. This tool should launch
automatically when Simulate mode was launched above.

The GAP program should now show live values at the inputs/outputs of each
program block, as shown below.

NOTE: Monitoring of live values is only possible in simulate mode—it is not

possible to connect to the ProTech and see live values.

If there are not live values being displayed, follow the steps below.

Figure 5-11. GAP in Monitor/Simulate Mode

Woodward 35
ProTech GAP Manual Manual 26712

Manually Starting SOS Servlink OPC Server

First check and see if the SOS Servlink OPC Server is running. This program will
run in the icon tray.
If the icon is present in the tray, right click and select Show.

Figure 5-12. GAP in Monitor/Simulate Mode

If the SOS server did not launch, open the server under Start/All
Programs/Woodward/SOS Servlink OPC Server and select the
icon.

You may get a cyber-security pop-up box (required for connecting to secure
controls) that does not apply to the ProTech. Just click OK (no user name or
password needed) and ignore the error about finding no secure controls.

Figure 5-13. Cybersecure Pop-up & Error Box

NOTE: The SOS should automatically connect to the IP address that appears in
NetSimCE window (see Figure 5-8 above).

Figure 5-14. SOS Servlink OPC Server Window

If not click on the port and select Session/Modify. This will open a dialog box to
enter the IP (as shown in your NetSimCE window). If not automatically
connected, select Session/Connect.

36 Woodward
Manual 26712 ProTech GAP Manual

Figure 5-15. SOS Servlink OPC Server Window

To simulate the action of the logic, the input signals can be forced to desired
values using the NetSimCE.

Go to the NetSimCE window and Select Variables from the Edit menu. A dialog
box with multiple tabs will open. Select the Input Switches tab and you should
see a list of the input signals that have been programmed.

Analog example: to set the INPUTS.BLOCK_3 value to 50 (these are scaled

units based on the Val_Hi and Val_Lo values, 0-100% in this case), double click
on this block in the list and enter a value of 50 as shown below. The buttons at
the bottom of this window can be used to clear these manual override values.

Figure 5-16. NetSim Multi-View Variables Window

Discrete example: to set the INPUTS.BLOCK_1 value to True, double click on

this block in the list and enter a value of 1 as shown below (1 = True, 0 = False).
The buttons at the bottom of this window can be used to clear these manual
override values.

Woodward 37
ProTech GAP Manual Manual 26712

Figure 5-17. NetSim Multi-View Variables Window

38 Woodward
 Manual 26712 ProTech GAP Manual

Chapter 6.
Application Examples

Overview
The example programs that are provided are intended to help the programmer by
showing typical application functions that can be programmed into the ProTech.
There are examples using the SX (Simplex Module) and the ProTech TPS
(Triplicated Modules) units. The TPS logic can be easily used in an MSM as well.

The couple of pages of each of these programs contains:

 Speed Inputs & Settings
 Start Logic Options
 Dedicated Discrete Input Signals (Reset, Start, Speed Signal Override)

It is important that these settings be modified to correct values for your

installation. The settings in these examples are very simple, as the intent was to
provide focus on examples of Safety Instrumented Functions other than the
Overspeed Protection. The ProTech manuals should provide all details required
to configure these options to your system.

Example #1—Application SX_PROG1_DI –

Discrete Input Trips into an SX Unit

Inputs to the Unit

The following table shows the inputs configured for this Program. Under the
discrete input channel is the custom tag that was used in this program.

This program includes logic examples for:

 Simplex DI’s—Channel 1 and 2
 Redundant DI’s—Channels 3 &4 (Loss of both signals results in a TRIP – 2
of 2)
 Triplicated DI’s—Channels 5,6 &7 (Loss of any 2 signals results in a TRIP –
2 of 3)

Channel Description Primary Function Secondary Function

DI #1 Local ESTOP Pushbutton TRIP on Loss of input none
TRIP on Loss of input
DI #2 Low Lube Oil Pressure Switch Override when speed none
OVRD is True
DI #3 Vibration Summary Trip Switch A TRIP on Loss of both A &
Alarm w/ a 2 sec delay
B (2 of 2) inputs
DI #4 Vibration Summary Trip Switch B on s/w Diff
(immediate)
DI #5 Pressure Vessel Hi Level Switch A Alarm w/ a 2 sec delay
TRIP on Loss of any 2 out
DI #6 Pressure Vessel Hi Level Switch B on any s/w different
of 3 inputs (immediate)
DI #7 Pressure Vessel Hi Level Switch C than other 2

Woodward 39
ProTech GAP Manual Manual 26712
Custom Tags entered for these inputs:
DI #1 ESTOP
DI #2 Lube Oil Pressure
DI #3 VibSys_Trip_A
DI #4 VibSys_Trip_B
DI #5 HP Tank SHH1234_A
DI #6 HP Tank SHH1234_B
DI #7 HP Tank SHH1234_C

Three DI Safety Functions Detailed in This Example Program

ESTOP & Turbine Lube Oil Pressure Example (DI #1 & DI #2) ‐
Simplex Discrete Input for ESTOP
Simplex DI for Low Lube Oil Pressure

TRIP on the following scenarios:

 ESTOP DI goes Low (FALSE)
 Lube Oil Pressure DI goes Low (FALSE) AND the Speed Failed Override
Input is Low (FALSE)

ALARM the following conditions:

 NO Alarms related to these Inputs

Annunciations:
When TRIP for DI #1 - annunciate TRIP on “Local Panel ESTOP”.
When TRIP for DI #2 - annunciate TRIP on “Low Lube Oil Pressure SW”.

Trip from Vibration System Commands Example (DI #3 & DI #4) ‐

Redundant Discrete Inputs from a Vibration System

TRIP on the following scenarios:

 BOTH DI go Low (FALSE) AND the Speed Failed Override Input is Low
(FALSE) AND the Unit Speed is greater than 500 rpm

ALARM the following conditions:

 If the 2 DI’s are in different states for more than 2 seconds

Annunciations:
When TRIPPED - annunciate “Trip from VIB System”.
When ALARMING - annunciate “VIB Switch Difference”.

Trip from High Pressure Tank Level Switches Example (DI #5, #6 & #7) ‐
Triplex Discrete Inputs from a Vibration System

TRIP on the following scenarios:

 If any 2 out of the 3 DI’s go Low (FALSE)

ALARM the following conditions:

 If any of the 3 DI’s are in a different state than the other 2 for more than 2
seconds

Annunciations:
When TRIPPED - annunciate “High Pressure Tank Trip”.
When ALARMING - annunciate “Pressure Tank SW Diff”.
40 Woodward
 Manual 26712 ProTech GAP Manual

Outputs from the Unit:

The message indications below are custom messages that have been added to
the Trip and Alarm Latch and Log functions in the ProTech.

Custom TRIP indications:

Local Panel ESTOP
Low Lube Oil Pressure SW
TRIP from VIB System
High Pressure Tank TRIP

Custom ALARM indications:

VIB Switch Difference
Pressure Tank SW Diff

Example #2—Application SX_PROG1_AI –

Analog Input Trips into an SX Unit

Speed Settings, Start Logic & Dedicated Signals

Inputs to the Unit

The following table shows the inputs configured for this Program. Under the input
channel is the custom tag that was used in this program.

This program includes logic examples for:

 Redundant AI’s - Channels 1 &2 (TRIP on Loss of both signals)
 Redundant AI’s – Channels 3 &4 (TRIP on Loss of both signals)
 Triplicated AI’s – Channels 5,6 &7 (TRIP on Loss of any 2 signals / 2 of 3)

Channel Description Primary Functions Secondary Functions

Alarm w/ a 2 sec delay
single sensor fault
AI #1 Turbine Lube Oil Pressure A Alarm w/ a 1 sec delay
TRIP on Loss of both A & B (2
single sensor below low
of 2) inputs (immediate)
limit setpoint but not failed
TRIP if both signals fall below
Alarm & Energize relay
Low Limit Setpoint of 8 psia
AI #2 Turbine Lube Oil Pressure B output if either sensor falls
below alarm setpoint of
pressure < 12 psia
Alarm w/ a 2 sec delay
single sensor fault
AI #3 High Pressure Tank Level A TRIP on Loss of both A & B (2
Alarm w/ a 5 sec delay
of 2) inputs (immediate)
single sensor above high
TRIP if both signals rise
limit setpoint
above High Limit Setpoint of
Alarm if either sensor rises
AI #4 High Pressure Tank Level B 90%
above alarm setpoint of
80%
Alarm w/ a 1 sec delay
AI #5 HP Vessel Pressure Sensor A single sensor above high
limit setpoint
Alarm w/ a 2 sec delay
TRIP on Loss of any 2 out of
AI #6 HP Vessel Pressure Sensor B single sensor fault
3 inputs (immediate)
Alarm & Energize relay
output if any sensor rises
AI #7 HP Vessel Pressure Sensor C above alarm setpoint w/ 1
sec delay

Woodward 41
ProTech GAP Manual Manual 26712
Custom Tags entered for these inputs:
AI #1 Turb Lube Oil Pressure A
AI #2 Turb Lube Oil Pressure B
AI #3 Hi PressTank Level A
AI #4 Hi PressTank Level B
AI #5 HP Vessel Press A
AI #6 HP Vessel Press B
AI #7 HP Vessel Press C

Three Safety Functions Detailed in This Example Program

Turbine Lube Oil Pressure Example (AI #1 & AI #2) ‐ LUBEOIL
Redundant Analog inputs for this signal
Both analog inputs are ranged for 0–100 psia
Trip Level Setpoint = 8 psia
Alarm Level Setpoint = 12 psia

TRIP on 3 scenarios:
 Both signals Fail (2 out of 2 Vote to TRIP)
 Both signals fall below 8 psia
 Both signals in 1 of the above conditions

** For the second condition—If the requirement is for the Trip to occur if EITHER
signal falls below 8 psia, then the LOGIC_GATES.BLOCK_4.AND block can be
changed to an OR block.

ALARM the following conditions:

 Each sensor if out of range (2 ma & 22 ma) for > 2 seconds
 Each sensor if signal is below Trip level setpoint for >1 second

Additional functional requirements are as follows:

 When the Alarm level is reached, energize a Relay Output to turn on an
Auxiliary Lube Oil Pump.
 Keep this relay output on until the signal level is above 15 psia.

Annunciations:
When Alarm level is reached annunciate “Lube Oil Low / Aux Pump On”.

For Failed Sensors, annunciate “Lube Oil Press Sensor X (A or B) FLT”.

For one Sensor at Trip Level annunciate “Lube Oil Press Sensor X (A or B)
SD”.

For Trip annunciate “Low Lube Oil Press or 2 of 2 Failed TRIP”

Tank Level Indications (AI #3 & AI #4) ‐ TANKLVL

Redundant Analog inputs for this signal
Both analog inputs are ranged for 0–100 percent
Trip Level Setpoint = 90%
Alarm Level Setpoint = 80%

TRIP on 3 scenarios:
 Both signals Fail (2 out of 2 Vote to TRIP)
 Both signals rise above 90%
 Both signals in 1 of the above conditions

42 Woodward
Manual 26712 ProTech GAP Manual
** For the second condition—If the requirement is for the Trip to occur if EITHER
signal falls rises above 90%, then the LOGIC_GATES.BLOCK_15.AND block
can be changed to an OR block.

ALARM the following conditions:

 Each sensor if out of range (2 ma & 22 ma) for > 2 seconds
 Each sensor if signal is above Trip level setpoint for > 5 second

Annunciations:
When Alarm level is reached annunciate “Tank High Level ALM”.

For Failed Sensors, annunciate “Tank Level Sensor X (A or B) FLT”.

For one Sensor at Trip Level annunciate “Tank Level Sensor X (A or B) SD”.

For Trip annunciate “Tank Hi Level or 2 of 2 Failed TRIP”

Pressure Signals from a HP Vessel (AI #5, AI #6 & AI #7)‐TANKPR

Triplicated Analog inputs for this signal
All analog inputs are ranged for 0–500 psia
Trip Level Setpoint = 480 psia
Alarm Level Setpoint = 450 psia

TRIP on 3 scenarios:
 Any 2 out of 3 signals Failed
 Any 2 out of 3 signals above Trip Level setpoint
 Any 2 signals in 1 of the above conditions

ALARM the following conditions:

 Each sensor if out of range (2 ma & 22 ma) for > 2 seconds
 Each sensor if signal is above Trip level setpoint for > 1 second
 Any healthy sensor is > Alarm level setpoint for > 1 second

Additional functional requirements are as follows:

 When the Alarm level is reached, energize a Relay Output to turn on an
Pressure Relief Safety Valve.

Annunciations:
When Alarm level is reached annunciate “HP Vessel Hi Press ALM”.

For Failed Sensors, annunciate “Vessel Press Sensor X (A, B or C) FLT”.

For one Sensor at Trip Level annunciate “Vessel Hi Press Sensor X (A, B or C)
SD”.

For Trip annunciate “HP Vessel Hi Press or 2 of 3 Failed TRIP”

Outputs from the Unit

The message indications below are custom messages that have been added to
the Trip and Alarm Latch and Log functions in the ProTech.

Custom TRIP indications:

Lo Lube Oil Pressure SD
Tank High Level TRIP
Vessel High Pressure TRIP

Woodward 43
ProTech GAP Manual Manual 26712
Custom ALARM indications:
LubeOil Press Snsr A SD
LubeOil Press Snsr A FLT
LubeOil Press Snsr B SD
LubeOil Press Snsr B FLT
Tank Level Sensor A SD
Tank Level Sensor A FLT
Tank Level Sensor B SD

Tank Level Sensor B FLT

Vessel Press Snsr A SD
Vessel Press Snsr A FLT
Vessel Press Snsr B SD
Vessel Press Snsr B FLT
Vessel Press Snsr C SD
Vessel Press Snsr C FLT
Lo Lube Oil ALM/Aux Pump ON
HP Vessel Hi Press ALM
Tank High Level ALM

Relay Outputs Used

Relay Output #1 Turn ON Auxiliary Pump
Relay Output #2 Open Pressure Relief Safety Valve

Example #3—Application TPS_VI_PROG1 –

Analog & Discrete Input Trips into an TPS Unit

Inputs to the Unit

The following table shows the inputs configured for this Program. Under the input
channel is the custom tag that was used in this program.

This program includes logic examples for:

 Triplicated DI’s – Channels 1,2 and 4 on each Module
 Redundant DI’s – Channel 3 on Modules A & B
 Simplex DI – Channel 3 on Module C
 Triplicated AI’s – Channel 6 on each Module
 Redundant AI’s – Channel 7 pm Modules A and B

44 Woodward
 Manual 26712 ProTech GAP Manual

Channel Description Primary Functions Secondary Functions

DI #1 (ABC) ESTOP Emergency Stop
Alarm if 1 switch differs
from the others for more
DI #2 (ABC) Vibration System Trips TRIP on 2 out of 3 inputs lost than 2 seconds
Alarm if inputs are NOT True
DI #3 (AB) Generator Excitation OK and Speed is > 1000 rpm No Trips on these
DI #3 (C) Panel Door Limit Switch Alarm if Purge Door is Open Monitor via Modbus
Operator/DCS initiated auto
DI #4 (ABC) Run Auto/Periodic Test test of each kernel health
I #5 N/C No Connection / Not Used
TRIP on Loss of 2 out of 3
inputs (immediate)
TRIP if pressure < 8 psia Energize a relay output (to
Turbine Lube Oil Pressure Alarm each failed sensor with Turn on Aux Pump) if
AI #6 (ABC)
(Range 0-100 psia) a 2 second delay pressure falls below alarm
Alarm when Pressure is < 12 setpoint of 12 psia
psia & clear only when
pressure is >15 psia
TRIP on Loss of both A & B (2
of 2) inputs (immediate)
TRIP if average tank level
rises above Hi Hi Limit
Setpoint of 90% Energize a relay output (to
Alarm if average tank level Open a Vent Valve) if
High Pressure Tank Level
AI #7 (AB) rises above High Limit average tank level rises
(Range 0-100 %)
Setpoint of 85% above alarm setpoint of
Alarm each failed sensor with 85%
a 2 second delay
Alarm if sensors Differ by
more than 5% with a 2 second
delay,

Custom Tags entered for these inputs:

DI #1 ABC ESTOP Circuit
DI #2 ABC Vibration System Trip Signal A, B & C
DI #3 AB Generator Excitation OK Signal A & B
DI #3 C Enclosure Door Panel Limit Switch
DI #4 ABC Run Periodic Auto Test
AI #6 ABC Lube Oil Pressure Sensor A, B, C
AI #7 AB HP Vessel Level Sensor A & B

Woodward 45
ProTech GAP Manual Manual 26712

Chapter 7.
Service Options

Product Service Options

If you are experiencing problems with the installation, or unsatisfactory
performance of a Woodward product, the following options are available:
 Consult the troubleshooting guide in the manual.
 Contact the manufacturer or packager of your system.
 Contact the Woodward Full Service Distributor serving your area.
 Contact Woodward technical assistance (see “How to Contact Woodward”
later in this chapter) and discuss your problem. In many cases, your
problem can be resolved over the phone. If not, you can select which course
of action to pursue based on the available services listed in this chapter.

OEM and Packager Support: Many Woodward controls and control devices are
installed into the equipment system and programmed by an Original Equipment
Manufacturer (OEM) or Equipment Packager at their factory. In some cases, the
programming is password-protected by the OEM or packager, and they are the best
source for product service and support. Warranty service for Woodward products
shipped with an equipment system should also be handled through the OEM or
Packager. Please review your equipment system documentation for details.

Woodward Business Partner Support: Woodward works with and supports a

global network of independent business partners whose mission is to serve the
users of Woodward controls, as described here:
 A Full Service Distributor has the primary responsibility for sales, service,
system integration solutions, technical desk support, and aftermarket
marketing of standard Woodward products within a specific geographic area
and market segment.
 An Authorized Independent Service Facility (AISF) provides authorized
service that includes repairs, repair parts, and warranty service on Woodward's
behalf. Service (not new unit sales) is an AISF's primary mission.
 A Recognized Engine Retrofitter (RER) is an independent company that
does retrofits and upgrades on reciprocating gas engines and dual-fuel
conversions, and can provide the full line of Woodward systems and
components for the retrofits and overhauls, emission compliance upgrades,
long term service contracts, emergency repairs, etc.
 A Recognized Turbine Retrofitter (RTR) is an independent company that
does both steam and gas turbine control retrofits and upgrades globally, and
can provide the full line of Woodward systems and components for the
retrofits and overhauls, long term service contracts, emergency repairs, etc.

You can locate your nearest Woodward distributor, AISF, RER, or RTR on our
website at:
www.woodward.com/directory

46 Woodward
Manual 26712 ProTech GAP Manual

Woodward Factory Servicing Options

The following factory options for servicing Woodward products are available
through your local Full-Service Distributor or the OEM or Packager of the
equipment system, based on the standard Woodward Product and Service
Warranty (5-01-1205) that is in effect at the time the product is originally shipped
from Woodward or a service is performed:
 Replacement/Exchange (24-hour service)
 Flat Rate Repair
 Flat Rate Remanufacture

Replacement/Exchange: Replacement/Exchange is a premium program

designed for the user who is in need of immediate service. It allows you to
request and receive a like-new replacement unit in minimum time (usually within
24 hours of the request), providing a suitable unit is available at the time of the
request, thereby minimizing costly downtime. This is a flat-rate program and
includes the full standard Woodward product warranty (Woodward Product and
Service Warranty 5-01-1205).

This option allows you to call your Full-Service Distributor in the event of an
unexpected outage, or in advance of a scheduled outage, to request a
replacement control unit. If the unit is available at the time of the call, it can
usually be shipped out within 24 hours. You replace your field control unit with
the like-new replacement and return the field unit to the Full-Service Distributor.

Charges for the Replacement/Exchange service are based on a flat rate plus
shipping expenses. You are invoiced the flat rate replacement/exchange charge
plus a core charge at the time the replacement unit is shipped. If the core (field
unit) is returned within 60 days, a credit for the core charge will be issued.

Flat Rate Repair: Flat Rate Repair is available for the majority of standard
products in the field. This program offers you repair service for your products with
the advantage of knowing in advance what the cost will be. All repair work carries
the standard Woodward service warranty (Woodward Product and Service
Warranty 5-01-1205) on replaced parts and labor.

Flat Rate Remanufacture: Flat Rate Remanufacture is very similar to the Flat
Rate Repair option with the exception that the unit will be returned to you in “like-
new” condition and carry with it the full standard Woodward product warranty
(Woodward Product and Service Warranty 5-01-1205). This option is applicable
to mechanical products only.

Returning Equipment for Repair

If a control (or any part of an electronic control) is to be returned for repair,
please contact your Full-Service Distributor in advance to obtain Return
Authorization and shipping instructions.

When shipping the item(s), attach a tag with the following information:
 return authorization number;
 name and location where the control is installed;
 name and phone number of contact person;
 complete Woodward part number(s) and serial number(s);
 description of the problem;
 instructions describing the desired type of repair.

Woodward 47
ProTech GAP Manual Manual 26712

Packing a Control
Use the following materials when returning a complete control:
 protective caps on any connectors;
 antistatic protective bags on all electronic modules;
 packing materials that will not damage the surface of the unit;
 at least 100 mm (4 inches) of tightly packed, industry-approved packing
material;
 a packing carton with double walls;
 a strong tape around the outside of the carton for increased strength.

To prevent damage to electronic components caused by improper

handling, read and observe the precautions in Woodward manual
82715, Guide for Handling and Protection of Electronic Controls,
Printed Circuit Boards, and Modules.

Replacement Parts
When ordering replacement parts for controls, include the following information:
 the part number(s) (XXXX-XXXX) that is on the enclosure nameplate;
 the unit serial number, which is also on the nameplate.

Engineering Services
Woodward offers various Engineering Services for our products. For these services,
you can contact us by telephone, by email, or through the Woodward website.
 Technical Support
 Product Training
 Field Service

Technical Support is available from your equipment system supplier, your local Full-
Service Distributor, or from many of Woodward’s worldwide locations, depending
upon the product and application. This service can assist you with technical
questions or problem solving during the normal business hours of the Woodward
location you contact. Emergency assistance is also available during non-business
hours by phoning Woodward and stating the urgency of your problem.

Product Training is available as standard classes at many of our worldwide

locations. We also offer customized classes, which can be tailored to your needs
and can be held at one of our locations or at your site. This training, conducted
by experienced personnel, will assure that you will be able to maintain system
reliability and availability.

Field Service engineering on-site support is available, depending on the product

and location, from many of our worldwide locations or from one of our Full-
Service Distributors. The field engineers are experienced both on Woodward
products as well as on much of the non-Woodward equipment with which our
products interface.

For information on these services, please contact us via telephone, email us, or
use our website: www.woodward.com.

48 Woodward
 Manual 26712 ProTech GAP Manual

How to Contact Woodward

For assistance, call one of the following Woodward facilities to obtain the address
and phone number of the facility nearest your location where you will be able to
get information and service.

Electrical Power Systems Engine Systems Turbine Systems

Facility---------------- Phone Number Facility---------------- Phone Number Facility---------------- Phone Number
Brazil ------------- +55 (19) 3708 4800 Brazil ------------- +55 (19) 3708 4800 Brazil ------------- +55 (19) 3708 4800
China ----------- +86 (512) 6762 6727 China ----------- +86 (512) 6762 6727 China ----------- +86 (512) 6762 6727
Germany--------- +49 (0) 21 52 14 51 Germany------- +49 (711) 78954-510 India --------------- +91 (129) 4097100
India --------------- +91 (129) 4097100 India --------------- +91 (129) 4097100 Japan -------------- +81 (43) 213-2191
Japan -------------- +81 (43) 213-2191 Japan -------------- +81 (43) 213-2191 Korea -------------- +82 (51) 636-7080
Korea -------------- +82 (51) 636-7080 Korea -------------- +82 (51) 636-7080 The Netherlands - +31 (23) 5661111
Poland--------------- +48 12 295 13 00 The Netherlands - +31 (23) 5661111 Poland--------------- +48 12 295 13 00
United States ---- +1 (970) 482-5811 United States ---- +1 (970) 482-5811 United States ---- +1 (970) 482-5811

You can also locate your nearest Woodward distributor or service facility on our
website at:
www.woodward.com/directory

Technical Assistance
If you need to telephone for technical assistance, you will need to provide the following information.
Please write it down here before phoning:

Your Name
Site Location
Phone Number
Fax Number
Engine/Turbine Model Number
Manufacturer
Number of Cylinders (if applicable)
Type of Fuel (gas, gaseous, steam, etc)
Rating
Application
Control/Governor #1
Woodward Part Number & Rev. Letter
Control Description or Governor Type
Serial Number
Control/Governor #2
Woodward Part Number & Rev. Letter
Control Description or Governor Type
Serial Number
Control/Governor #3
Woodward Part Number & Rev. Letter
Control Description or Governor Type
Serial Number

If you have an electronic or programmable control, please have the adjustment setting positions or
the menu settings written down and with you at the time of the call.

Woodward 49
ProTech GAP Manual Manual 26712

Appendix.
ProTech Template GAP Blocks

Configure Blocks
All the Configuration Blocks can be configured for All modules, A module, B
module, or C module. Additional details on each Configure Block can be found in
the GAP Help menu under Block Help.

AUTO_TEST
This block is only available in the ProTechTPS or MicroNet SM system. This block
configures the Auto Sequence Test. For more detailed information see the
ProTechTPS/MicroNet SM manual.

FIELD DESCRIPTION:
Inputs
Time_ENABLEd:
This input enables the Auto Sequence Test timer. Possible values are “Yes” or
“No”. Default value is “No”.
INTERVAL:
This input configures the time interval in days. The Auto Sequence Test will
be started after every interval. Possible values are from 1 to 999. Default value
is 7.
ALLOW_DISABLE:
This input configures if the Operator can disable the Test from the Front panel.
Possible values are “Yes” and “No”. Default value is “Yes”.
CONtinue_TO:
This input configures the time to wait for the CONTINUE_INPUT to goes
TRUE.
START_INPUT:
If this input goes TRUE the Auto-Sequence-Test will be started.
CONTINUE_INPUT:
If this input goes TRUE before the CONTINUE_TO times out the Auto
Sequence Test at the next Module will be started.
Outputs
none

50 Woodward
Manual 26712 ProTech GAP Manual

HOME_SCREEN

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system.
This block is for Home Screen configuration.

FIELD DESCRIPTION:
Inputs
HOME_SCREEN:
This input sets the Home Screen the module switches to when pressing the
HOME key at the device. Possible values: see Home Screen List. The
default value is “Home”.
HS_ON_TRIP:
This input disables (“No”) or enables (“Yes”) switching to the Home
Screen on Trip. The default value is “Yes”.
Outputs
none

MODBUS

BLOCK DESCRIPTION:
This block is for the Modbus configuration.

FIELD DESCRIPTION:
Inputs
MODE:
This input sets the Connection Mode. Possible connections are RS485 or
RS232.
The default value is “RS232”.
Baud_RATE:
This input sets the Baud Rate in bit/s. Possible values are 19200, 38400,
57600 or 115200.
The default value is “19200”.
PARITY:
This input sets the Communication Parity. Possible values are “Even
Parity”, “Odd Parity” or “No Parity”.
The default value is “No Parity”.

Woodward 51
ProTech GAP Manual Manual 26712
SLAVE:
This input sets the Modbus Slave Address. Possible values are in the range
from 1 to 247.
The default value is “1”.
COMMANDS:
This input enables write commands. Possible values are “Yes” or “No”.

The default value is “No”.

Outputs
none

PWR_ALM

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system. It is for the
Power Supply Lost Alarm configuration.

FIELD DESCRIPTION:
Inputs
PS_1_ALARM:
This input defines if the loss of power supply 1 shall cause an alarm or
not. If set to “Yes” it will cause an alarm if set to “No” it won´t. The
default value is “Yes”.
PS_2_ALARM:
This input defines if the loss of power supply 2 shall cause an alarm or
not. If set to “Yes” it will cause an alarm if set to “No” it won´t. The
default value is “Yes”.
Outputs
none

SHARED_SFO

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system.
This block is for sharing the Speed Fail Override signals between the different modules.
When this block is used, it commands the system to use speed fail override signals from
other modules as well as the local speed fail override function. The input values are
OR-ed and connected to the speed fail trip and speed fail timeout trip functions, see
START_LOGIC.

52 Woodward
Manual 26712 ProTech GAP Manual
FIELD DESCRIPTION:
Inputs
INPUT_1:
This input can be set to one of the following values. “Module A Speed Fail
Override”, “Module B Speed Fail Override”, “Module C Speed Fail Override”
or “Not Used”. The default value is “Not Used”.
INPUT_2:
This input can be set to one of the following values. “Module A Speed Fail
Override”, “Module B Speed Fail Override”, “Module C Speed Fail Override”
or “Not Used”. The default value is “Not Used”.
INPUT_3:
This input can be set to one of the following values. “Module A Speed Fail
Override”, “Module B Speed Fail Override”, “Module C Speed Fail Override”
or “Not Used”. The default value is “Not Used”.
Outputs
None

SHARED_START

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system.
This block is for sharing the Start Input signals between the different modules. When this
block is used, it commands the system to use shared start signals from other modules as
well as the local start function. The input values are OR-ed and connected to the speed
fail trip and speed fail timeout trip functions, see START_LOGIC.

FIELD DESCRIPTION:
Inputs
INPUT_1:
This input can be set to one of the following values. “Module A Start”,
“Module B Start”, “Module C Start” or “Not Used”. The default value is “Not
Used”
INPUT_2:
This input can be set to one of the following values. “Module A Start”,
“Module B Start”, “Module C Start” or “Not Used”. The default value is “Not
Used”
INPUT_3:
This input can be set to one of the following values. “Module A Start”,
“Module B Start”, “Module C Start” or “Not Used”. The default value is “Not
Used”
Outputs
None

Woodward 53
ProTech GAP Manual Manual 26712

START _LOGIC

BLOCK DESCRIPTION:
This block configures the Speed Fail behavior.

FIELD DESCRIPTION:
Inputs
SETPOINT:
Speed Setpoint below which the speed signal is considered
failed. Valid values: 0-25000 rpm. Default value is 100 rpm.
SPD_FAIL_T:
When set to “Used”, this trip is activated when speed is
below the Speed Fail Setpoint and the Speed Fail Override
discrete input is not closed. Valid values: “Not Used” or
“Used”. Default value is “Not Used”.
SPD_FAIL_A:
When set to “Used”, this alarm is activated when speed is
below the Speed Fail Setpoint. Valid values: “Not Used” or
“Used”. Default value is “Not Used”.
SPD_TO_T:
When set to “Used”, this trip is activated if speed is below
Speed Fail Setpoint when the Speed Fail Timeout Time
expires. Valid values: “Not Used” or “Used”. Default value is
“Not Used”.
SPD_TO:
Max time for speed to exceed the Speed Fail Setpoint after a
‘start’ command. This setting is used in conjunction with the
Speed Fail Timeout Trip. Valid values: 1-28800 seconds.
Default value is 1 second.
Outputs
none

54 Woodward
Manual 26712 ProTech GAP Manual

SYS_INFO_MSM

BLOCK DESCRIPTION:
This block is only available in the MicroNet SM system. This block is mainly used as an
Information block. It can also be used to specify if configurations may be compared between
the three different modules.

FIELD DESCRIPTION:
Inputs
GAP_DATE:
This input shows the date of the latest application save.
CONF_COMP:
This input defines if the configurations of the three different modules are compared.
If “Yes” is selected, it compares the module settings. If “No” is selected, it doesn’t.
The default value is “Yes”.

Woodward 55
ProTech GAP Manual Manual 26712
CRCs:
If an application was successfully downloaded to the MicroNetSM, GAP receives
the CRCs from the MicroNetSM and saves each in the appropriate CRC input of
this block. This allows checking whether the application in GAP and in the
MicroNetSM match. If there is any change in the application, all CRCs are
considered invalid and will be deleted.
Outputs
None. Connection to the configuration compare alarm is provided as the CONF_MISM
output on the INT_ALARMS_MSM block.

SYS_INFO_TPS

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS system. This block is mainly used as an
Information block. It can also be used to specify if configurations may be compared
between the three different modules.

56 Woodward
Manual 26712 ProTech GAP Manual
FIELD DESCRIPTION:
Inputs
GAP_DATE:
This input shows the date of the latest application save.
CONF_COMP:
This input defines if the configurations of the three different modules are
compared. If “Yes” is selected, it compares the module settings. If “No” is
selected, it doesn’t. The default value is “Yes”.
CRCs:
If an application was successfully downloaded to the ProTechTPS, GAP
receives the CRCs from the ProTechTPS and saves each in the appropriate
CRC input of this block. This allows checking whether the application in GAP
and in the ProTechTPS match. If there is any change in the application, all
CRCs are considered invalid and will be deleted.
Outputs
none

TEST_MODE_TPS

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS system. This block configures the Test
Modes.

FIELD DESCRIPTION:
Inputs
OVRSPD:
This input defines the Temporary Overspeed Threshold in RPM. Possible
values are from 100 to 32000. Default value is 100.
OVRSPD_TO:
This input defines the Timeout for Temporary Overspeed Threshold in
seconds. Possible values are from 0 to 1800. Default value is 0.
SIMSPD_TO:
This input defines the Timeout for the Simulated Speed in seconds.
Possible values are from 0 to 1800. Default value is 0.
Permissive:
This input configures the test mode permissive function. Possible values
are “No InterModule Permissive”, “Module Not in Alarm” and “Module
Not Tripped”. Default value is “No InterModule Permissive”.
Outputs
none

Woodward 57
ProTech GAP Manual Manual 26712

TEST_MODE_MSM

BLOCK DESCRIPTION:
This block is only available in the MicroNet SM system. This block configures the Test
Modes.

FIELD DESCRIPTION:
Inputs
OVRSPD:
This input defines the Temporary Overspeed Threshold in RPM. Possible
values are from 100 to 32000. Default value is 100.
OVRSPD_TO:
This input defines the Timeout for Temporary Overspeed Threshold in seconds.
Possible values are from 0 to 1800. Default value is 0.
SIMSPD_TO:
This input defines the Timeout for the Simulated Speed in seconds. Possible
values are from 0 to 1800. Default value is 0.
Permissive:
This input configures the test mode permissive function. Possible values are
“No InterModule Permissive”, “Module Not in Alarm” and “Module Not
Tripped”. Default value is “No InterModule Permissive”.
Outputs
none

USR_TEST

BLOCK DESCRIPTION:
This block allows the users to configure custom test routines as needed to test their
system.

FIELD DESCRIPTION:
Inputs
ENABLE:
Set to “Yes” to use the function. Valid values: “Yes” or “No”. Default value is
“No”.
SET:
Input for selection to start the user-defined test.
RST:
Input for selection to stop the user-defined test.

58 Woodward
Manual 26712 ProTech GAP Manual
TIMEOUT:
Max test time setting. The test will abort after the timeout expires. Valid values: 0-
1800 seconds. Default value is 0.
Outputs
none

Process Blocks
All the Process Blocks can be configured for All modules, A module, B module,
or C module. Additional details on each Process Block can be found in the GAP
Help menu under Block Help.

ACCEL_RED_MGR
BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system.
This block is an Acceleration Redundancy Manager that performs a voting on two or
three connected remote acceleration inputs. The voting logic is described at the
ACCEL_OUT output description below.

FIELD DESCRIPTION:
Inputs
INPUT_1:
This input can be connected with a remote acceleration input from one of the
three Modules.
INPUT_2:
This input can be connected with a remote acceleration input from one of the
three Modules.
INPUT_3:
This input can be connected with a remote acceleration input from one of the
three Modules.
BASE_FUNC:
This input defines the voting logic if three inputs are connected and valid.
Default value is “Median”.
FALLBACK:
This input defines the voting logic if two inputs are connected and valid.
Default value is “HSS”.

Woodward 59
ProTech GAP Manual Manual 26712
Outputs
ACCEL_OUT:
If three inputs are connected and valid:
BASE_FUNC set to Median: This output will have the value of the input
value between the other two input values.
BASE_FUNC set to HSS: This output will have the value of the highest
input value.
BASE_FUNC set to LSS: This output will have the value of the lowest
input value.

If two/three inputs are connected and only two are valid:

FALLBACK set to HSS: This output will have the value of the highest
input value.
FALLBACK set to LSS: This output will have the value of the lowest input
value.

If one/two/three inputs are connected and only one is valid: This output will
have the same value as the valid input.

If one/two/three inputs are connected and no input is valid: This output will be
set to 0.

IN_1_INVALID:
This block's output will be TRUE if input INPUT_1 is invalid, else this output
will be FALSE.
IN_2_INVALID:
This block's output will be TRUE if input INPUT_2 is invalid, else this output
will be FALSE.
IN_3_INVALID:
This block's output will be TRUE if input INPUT_3 is invalid, else this output
will be FALSE.

60 Woodward
Manual 26712 ProTech GAP Manual

ALM_LATCH_MSM

BLOCK DESCRIPTION:
This block is only available in the MicroNet SM system. The output of this block goes TRUE
if any one of the Boolean INT_ALARMS or INPUT_X inputs is TRUE. The output remains
TRUE until the RST_FUNC input goes TRUE and all latch inputs are FALSE. The block has
predefined inputs and up to 75 user defined inputs.

FIELD DESCRIPTION:
Inputs
INT_ALARMS:
SPD_FAIL, SPD_LOSS, CONF_MISM, TIME_MON_1, TIME_MON_2,
INT_FAULT, PWR_FLT_1, PWR_FLT_2, OVRSPD_SP,
MAN_SPD_TST, AUTO_SPD_TST, AUTO_SPD_FAIL,
AUTO_SEQ_TST, AUTO_SEQ_TO, USR_TST_1, USR_TST_2,
USR_TST_3, IRIG_LOSS, SPD_RM_DIFF.
These inputs are predefined and may be blank or connected to the outputs of the
INT_ALARMS_MSM block. If left blank, the default values will be used. The
default values are the INT_ALARMS_MSM block outputs. They don’t have to be
connected for creating a wset file, these connections are provided only for
clarification and NETSIM purposes.
TRIP_LATCH:
This Input is predefined with the output of the TRIP_LATCH_MSM. If
TRIP_IS_ALARM is set to “Yes” this input will be OR-ed with the
INT_ALARMS. If it is left blank, the default value will be used. The default value
is the TRIP_LATCH_MSM block output.
TRIP_IS_ALARM:
This input configures if the TRIP_LATCH_MSM output shall be added to the
ALM_LATCH_MSM inputs. If set to “Yes”, it is included in the inputs, set to “No”
it is excluded. The default value is “Yes”.

Woodward 61
ProTech GAP Manual Manual 26712
RPT:
Add the desired amount of RPT fields (max 75). Each added RPT field include an
INPUT_X and a NAME_X input.
INPUT_X: This input may be blank or requires a Boolean input from one of the
allowed input connections.
NAME_X: This input can be used to define a 24 character name of the input X. If it
is left blank, the default value will be used. The default value is “Alarm Latch Input
X”. X is a number from 1 – 75
RST_FUNC:
This Input is predefined and may be blank or connected to the output of the
RST_FUNC block. If it is left blank, the default value will be used. The default
value is the RST_FUNC block output.
Outputs
ALM_LATCH:
This Boolean output goes TRUE if one of the INT_ALARMS inputs or one of the
INPUT_X inputs is TRUE.
ALM_INVALID:
This output can´t be connected to any input. The value of this output can be set
manually with NetSim and is for simulation only. If ALM_LATCH is connected to
a Redundancy/Shared Block and the value of this output is set to TRUE it simulates
an invalid ALM_LATCH value for the redundancy/shared block logic.

ALM_LATCH_TPS
BLOCK DESCRIPTION:
This block is only available in the ProTechTPS system. The output of this block goes
TRUE if one of the Boolean INT_ALARMS or INPUT_X inputs is TRUE. The output
remains TRUE until the RST_FUNC input goes TRUE and all other inputs are FALSE.
The block has predefined inputs and up to 75 user defined inputs.

62 Woodward
Manual 26712 ProTech GAP Manual
FIELD DESCRIPTION:
Inputs
INT_ALARMS:
SPD_FAIL, SPD_LOSS, CONF_MISM, TIME_MON_1, TIME_MON_2,
INT_FAULT, PWR_FLT_1, PWR_FLT_2, OVRSPD_SP, MAN_SPD_TST,
AUTO_SPD_TST, AUTO_SPD_FAIL, AUTO_SEQ_TST, AUTO_SEQ_TO,
USR_TST_1, USR_TST_2, USR_TST_3, SPD_RM_DIFF.
These inputs are predefined. They don’t have to be connected for creating a
.wset file. The values come from the outputs of the INT_ALARMS_TPS
block. See link below.
Internal alarm TPS.
TRIP_LATCH:
This Input is predefined with the output of the TRIP_LATCH_TPS. If
TRIP_IS_ALARM is set to “Yes” this input will be OR-ed with the
INT_ALARMS.
TRIP_IS_ALARM:
This input configures if the TRIP_LATCH_TPS output shall be added to the
ALM_LATCH_TPS inputs. If set to “Yes”, it is included in the inputs, if set to
“No”, it is excluded. The default value is “Yes”.
RPT:
Add the desired amount of RPT fields (max 75). Each added RPT field
includes an INPUT_X and a NAME_X input.
INPUT_X: This input may be blank or requires a Boolean input from one of
the allowed input connections.
NAME_X: This input can be used to define a 24 character name of the input
X. If it is left blank, the default value will be used. The default value is “Alarm
Latch Input X”. X is a number from 1 - 75
RST_FUNC:
This Input may be blank or has to be connected to the output of the
RST_FUNC block.
Outputs
ALM_LATCH:
This Boolean output goes TRUE if one of the INT_ALARMS inputs or one of
the INPUT_X inputs is TRUE.
ALM_INVALID:
This output can´t be connected to any input. The value of this output can be set
manually with NetSim and is for simulation only. If ALM_LATCH is
connected to a Redundancy/Shared Block and the value of this output is set to
TRUE it simulates an invalid ALM_LATCH value for the redundancy/shared
block logic.

AN_IN

Woodward 63
ProTech GAP Manual Manual 26712
BLOCK DESCRIPTION:
This block provides an Analog Output as well as some Boolean
Outputs. The Boolean Outputs depend on the input level
settings. The Analog Input is in a range between 4 mA – 20
mA. The user can change the units and define a new scaling of
the input values appropriate for those units.

FIELD DESCRIPTION:
Inputs
IN_NAME:
User-defined name for the input. Valid values: up to 24 characters.
VAL_LO:
Scaling value for the input, in user-defined units,
corresponding to 4 mA. Valid values: -20000 to 20000.
Default value is 4.
VAL_HI:
Scaling value for the input, in user-defined units,
corresponding to 20 mA. Valid values: -20000 to
20000. Default value is 20.
UNIT:
User-defined units for the input. Valid values: up to 7 characters.
SET_LO:
Lo input level setting, in user-defined units, below
which the Analog Input Lo indication is active. Valid
values: -32500 to 32500. Default value is 0.
SET_LOLO:
LoLo input level setting, in user-defined units, below
which the Analog Input LoLo indication is active. Valid
values: -32500 to 32500. Default value is 0.
SET_HI:
Hi input level setting, in user-defined units, below
which the Analog Input Hi indication is active. Valid
values: -32500 to 32500. Default value is 0.
SET_HIHI:
HiHi input level setting, in user-defined units, below
which the Analog Input HiHi indication is active. Valid
values: -32500 to 32500. Default value is 0.
Outputs
AN_IN:
This is the Analog output.
OUT_LO:
This is a Boolean Output. Is TRUE if AN_IN is lower than the value
of the SET_LO input.
OUT_LOLO:
This is a Boolean Output. Is TRUE if AN_IN is lower than the value
of the SET_LOLO input.
OUT_HI:
This is a Boolean Output. Is TRUE if AN_IN is higher than the value
of the SET_HI input.

64 Woodward
Manual 26712 ProTech GAP Manual
OUT_HIHI:
This is a Boolean Output. Is TRUE if AN_IN is higher than the value
of the SET_HIHI input.
RANGE_ERR:
This is a Boolean Output. Is TRUE if AN_IN is lower than 2 mA or
higher than 22 mA.
AN_IN_INVALID:
This output can´t be connected to any input. The value of this output can
be set manually with NetSim and is for simulation only. If AN_IN is
connected to a Redundancy/Shared Block and the value of this output is
set to TRUE it simulates an invalid AN_IN value for the
redundancy/shared block logic.

AN_OUT
BLOCK DESCRIPTION:
This block defines a min and max Speed value in RPM. The Speed value from the Speed
sensor will be converted into a mA value depending on the defined min/max values.

FIELD DESCRIPTION:
Inputs
RPM_4_mA:
This input defines the min RPM. All RPM values equal to or below this
defined Integer value will be converted to 4 mA. Higher values will be
calculated according to the defined range. Valid values: 0 to 32000 RPM. The
default value is 0 RPM.
RPM_20_mA:
This input defines the max RPM. All RPM values equal to or above this
defined Integer value will be converted to 20 mA. Lower values will be
calculated according to the defined range. Valid values: 0 to 32000 RPM. The
default value is 32000 RPM.

Allowed INPUT connections:

none

AND
BLOCK DESCRIPTION:
This block has between 2 and 5 Boolean inputs. This block's output will be TRUE only if
all of the Boolean Input Fields are TRUE. If any one of the inputs is FALSE then the
output of this block will be FALSE.

Woodward 65
ProTech GAP Manual Manual 26712
FIELD DESCRIPTION:
Inputs
RPT:
Add the desired amount of IN_x inputs. The minimum number of inputs
allowed is 2 and the maximum number of inputs allowed is 5.
NOTE: All IN_X inputs added to the RPT field require an input from the
allowed input connection list, they cannot be left blank. If an input has no
connection, delete the RPT input using the GAP editor.
IN_x:
This input requires a Boolean input from one of the allowed input
connections.
Outputs
AND:
This block's output will be TRUE only if all of the Boolean Input Fields are
TRUE. If any one of the inputs is FALSE then the output of this block will be
FALSE.

ARM

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system.
This block is an Analog Redundancy Manager that performs a voting on two or three
connected analog inputs. The voting logic is described at the ANALOG_OUT output
description below.

FIELD DESCRIPTION:
Inputs
INPUT_1:
This input can be connected with an analog input from one of the allowed input
connections, see below.
INPUT_2:
This input can be connected with an analog input from one of the allowed input
connections, see below.
INPUT_3:
This input can be connected with an analog input from one of the allowed input
connections, see below.
BASE_FUNC:
This input defines the voting logic if three inputs are connected and valid. Default
value is “Median”.
FALLBACK:
This input defines the voting logic if two inputs are connected and valid. Default
value is “HSS”.
DEFAULT_OUT:
This input defines the default output if all inputs are invalid. Default value is 0.

66 Woodward
Manual 26712 ProTech GAP Manual
Outputs
ANALOG_OUT:
If three inputs are connected and valid:
BASE_FUNC set to Median: This output will have the value of the input value
between the other two input values.
BASE_FUNC set to HSS: This output will have the value of the highest input
value.
BASE_FUNC set to LSS: This output will have the value of the lowest input
value.
BASE_FUNC set to Average: This output will have the math average value of all
three input values.

If two/three inputs are connected and only two are valid:

FALLBACK set to HSS: This output will have the value of the highest input
value.
FALLBACK set to LSS: This output will have the value of the lowest input
value.
FALLBACK set to Average: This output will have the math average value of all
the two valid inputs.

If one input is connected and valid or two/three inputs are connected and only one is
valid:
This output will have the same value as the valid input.

If one/two/three inputs are connected and none of them is valid:

This output will have the DEFAULT_OUT value.
IN_1_INVALID:
This block's output will be TRUE if input INPUT_1 is invalid, else this output will
be FALSE.
IN_2_INVALID:
This block's output will be TRUE if input INPUT_2 is invalid, else this output will
be FALSE.
IN_3_INVALID:
This block's output will be TRUE if input INPUT_3 is invalid, else this output will
be FALSE.

BRM

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system.
This block is a Boolean Redundancy Manager that performs a voting on two or three
connected Boolean inputs. The voting logic is described at the BOOL_OUT output description
below.

Woodward 67
ProTech GAP Manual Manual 26712
FIELD DESCRIPTION:
Inputs
INPUT_1:
This input can be connected with a Boolean input from one of the allowed input
connections, see below.
INPUT_2:
This input can be connected with a Boolean input from one of the allowed input
connections, see below.
INPUT_3:
This input can be connected with a Boolean input from one of the allowed input
connections, see below.
NO_VALID_IN:
This input defines the default output if all inputs are invalid. Default value is
FALSE.
TWO_IN_MISM:
This input defines the default output when only two inputs are valid and they do not
match. Default value is FALSE.
Outputs
BOOL_OUT:
If three inputs are connected and valid:
Three inputs match: This output will have the value of the matching input values.
Two inputs match: This output will have the value of the two matching input
values.
If two/three inputs are connected and only two are valid:
Two Inputs match: This output will have the value of the matching input values.
Inputs mismatch: This output will have the value of the TWO_IN_MISM value.
If two/three inputs are connected and only one is valid:
This output will have the value of the remaining value.
If two/three inputs are connected and no input is valid:
This output will have the value of the NO_VALID_IN value.

IN_1_INVALID:
This block's output will be TRUE if input INPUT_1 is invalid, else this output will
be FALSE.
IN_2_INVALID:
This block's output will be TRUE if input INPUT_2 is invalid, else this output will
be FALSE.
IN_3_INVALID:
This block's output will be TRUE if input INPUT_3 is invalid, else this output will
be FALSE.

COMPARE

68 Woodward
Manual 26712 ProTech GAP Manual
BLOCK DESCRIPTION:
This block compares the input value (IN) to the OFF_LEVEL input and
the ON_LEVEL input.

This block’s input is compared to the ON_LEVEL and OFF_LEVEL to

create the output COMPARE value. The values entered have the same
scaling as the connected analog input (speed is in rpm and
acceleration is in rpm/s). The difference between ON-level and OFF-
level can be used to create hysteresis.
If ON_LEVEL is greater than OFF_LEVEL, the output becomes TRUE
when the input is higher than ON_LEVEL and goes FALSE when the
input becomes less than OFF_LEVEL.

If ON_LEVEL is less than OFF_LEVEL, the output becomes TRUE when

the input is less than ON_LEVEL and goes FALSE when the input
becomes higher than OFF_LEVEL.

If ON_LEVEL equals the OFF_LEVEL there is no hysteresis and the

output becomes TRUE when the input is higher than the ON_LEVEL
and goes FALSE when the input becomes less than ON_LEVEL.

FIELD DESCRIPTION:
Inputs
INPUT Analog input value compared to the ON_LEVEL and
OFF_LEVEL to create the output COMPARE value.
OFF_LEVEL Analog Comparator OFF value, in engineering units.
Valid values: -32500 to 32500. Default value is 0.
ON_LEVEL Analog Comparator ON value, in engineering units.
Valid values: -32500 to 32500. Default value is 0.

Outputs
COMPARE:
Boolean block output value.

DELAY

BLOCK DESCRIPTION:
There are 25 Delay functions (timers) available that can be used to
create an output available for trips, alarms, or any logical function.
Each delay function has a pickup delay (delay in switching from FALSE
to TRUE) and a drop-off time (delay in switching from TRUE to FALSE).
The DELAY requires that the input stays TRUE for a configurable
TRUE_DLY time before the output changes state to TRUE, and that the
input be FALSE for a configurable FALSE_DLY time before the output
changes state to FALSE. The input fields for each delay can be any
function result from another gate or from an analog input alarm set
point, or a timer, etc. If the input goes TRUE for a time less than the
value defined in TRUE_DLY then the DELAY output will not change.

Woodward 69
ProTech GAP Manual Manual 26712
FIELD DESCRIPTION:
Inputs
FALSE_DLY:
Time delay that the input must remain FALSE before the output goes FALSE. The
minimum detectable resolution is 4 ms. Valid values: 0-3600 seconds. Default value
is 0.
TRUE_DLY:
Time delay that the input must remain TRUE before the output goes TRUE. The
minimum detectable resolution is 4 ms. Valid values: 0-3600 seconds. Default value
is 0.

Outputs
DELAY:
Results of the block DELAY.

DIFF_DETECT

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system.
This block is a Difference Detection block that compares two inputs and sets the output to
TRUE if the difference between these inputs exceeds a configured threshold for a configured
time.

FIELD DESCRIPTION:
INPUT_1:
This input can be connected with an analog input from allowed input connections,
see below.
INPUT_2:
This input can be connected with an analog input from allowed input connections,
see below.
DIFF_ALM_LIMIT:
This input defines the threshold for a difference alarm. The difference alarm occurs
when two inputs exceed the threshold for the time defined at DIFF_ALM_TIME.
Default value is 2.
DIFF_ALM_TIME:
This input defines the time in “ms” the difference must exceed the
DIFF_ALM_LIMIT before a difference alarm occurs. Default value is 500 ms.
Outputs
DIFF_DETECT:
This output is TRUE if the difference between both inputs exceeds the
DIFF_ALM_LIMIT threshold for the time defined at DIFF_ALM_TIME, else
FALSE.

DISCRETE_IN

70 Woodward
Manual 26712 ProTech GAP Manual
BLOCK DESCRIPTION:
This block provides a Boolean Input.

FIELD DESCRIPTION:
Inputs
NAME:
User-defined name for the input. Valid values: up to 24 characters. Default
value is “Input 1”.
Outputs
DISCRETE_IN:
Boolean Output. Possible values are TRUE or FALSE.
DI_INVALID:
This output can´t be connected to any input. The value of this output can be set
manually with NetSim and is for simulation only. If DISCRETE_IN is connected to
a Redundancy/Shared Block and the value of this output is set to TRUE it simulates
an invalid DISCRETE_IN value for the redundancy/shared block logic.

EVT_LATCH

BLOCK DESCRIPTION:
This block’s output is TRUE if one of the INPUT_X values is TRUE. The output remains
TRUE until all INPUT_X values are FALSE and the RST input is TRUE.
Note: If the block is placed, it requires a connection to the RST input and at least to one
INPUT_X input.

FIELD DESCRIPTION:
Inputs
RST:
This is the reset input. If this input is TRUE and all INPUT_X values are FALSE,
the output will be FALSE.
INPUT_x:
This INPUT_X requires a Boolean value. X is a number from 1 – 25.
NAME_X:
This input is a user-defined name for the input. Valid values: up to 24 characters.
Default value is “Event Latch Input X”. X is a number from 1 – 25.
Outputs
EVT_LATCH:
This output will be TRUE if one of the INPUT_X values is TRUE. If all INPUT_X
are FALSE and RST is TRUE, this output will be FALSE.

Woodward 71
ProTech GAP Manual Manual 26712

INT_ALARMS_TPS

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS system. This block provides all predefined
internal alarms. These Boolean values can be connected to other blocks.

FIELD DESCRIPTION:
Inputs
none
Outputs
All outputs have Boolean values and can be connected to other blocks. Some of them
have to be configured from other blocks, some are available without configuration.
SPD_FAIL:
Configuration block: START_LOGIC.BLOCK
SPD_Loss:
Configuration block: SPEED_TPS.BLOCK
CONF_MISM:
Configuration block: SYS_INFO_TPS.BLOCK
TIME_MON_1:
Configuration block: TRIP_TIMER_1.BLOCK
TIME_MON_2:
Configuration block: TRIP_TIMER_2.BLOCK
INT_FAULT:
No configuration possible.
PWR_FLT_1:
Configuration block: PWR_ALM.BLOCK
PWR_FLT_2:
Configuration block: PWR_ALM.BLOCK
OVRSPD_SP:
Configuration block: TEST_MODE_TPS.BLOCK

72 Woodward
Manual 26712 ProTech GAP Manual
OPN_WIRE:
No configuration possible.
MAN_SPD_TST:
Configuration block: TEST_MODE_TPS.BLOCK
AUTO_SPD_TST:
Configuration block: TEST_MODE_TPS.BLOCK
AUTO_SPD_FAIL:
Configuration block: TEST_MODE_TPS.BLOCK
AUTO_SEQ_TST:
Configuration block: AUTO_TEST.BLOCK
AUTO_SEQ_TO:
Configuration block: AUTO_TEST.BLOCK
USR_TST_1:
Configuration block: USR_TEST.BLOCK_1
Usr_TST_2:
Configuration block: USR_TEST.BLOCK_2
USR_TST_3:
Configuration block: USR_TEST.BLOCK_3
SPD_RM_DIFF:
Configuration block: SPEED_RED_MGR.BLOCK

INT_ALARMS_MSM

BLOCK DESCRIPTION:
This block is only available in the MicroNet SM system. This block provides all predefined
internal alarms. These Boolean values can be connected to other blocks.

Woodward 73
ProTech GAP Manual Manual 26712
FIELD DESCRIPTION:
Inputs
none
Outputs
All outputs have Boolean values and can be connected to other blocks. Some of them
have to be configured from other blocks, some are available without configuration.
SPD_FAIL:
Front Panel Indication: Speed Fail Alarm
Configuration block: START_LOGIC.BLOCK
SPD_LOSS:
Front Panel Indication: Speed Lost Alarm
Configuration block: SPEED_MSM.SPD_LOSS (when set to Alarm)
CONF_MISM:
Front Panel Indication: Configuration Mismatch
Configuration block: SYS_INFO_MSM.CONF_COMP
TIME_MON_1:
Front Panel Indication: Trip Time Mon 1 Alarm
Configuration block: TRIP_TIMER_1.BLOCK
TIME_MON_2:
Front Panel Indication: Trip Time Mon 2 Alarm
Configuration block: TRIP_TIMER_2.BLOCK
INT_FAULT:
Front Panel Indication: Internal Fault Alarm
Configuration block: No configuration possible, always active.
PWR_FLT_1:
Front Panel Indication: Power Supply 1 Fault
Configuration block: PWR_ALM.PS_1_ALM
PWR_FLT_2:
Front Panel Indication: Power Supply 2 Fault
Configuration block: PWR_ALM.PS_2_ALM
OPN_WIRE:
Front Panel Indication: Speed Open Wire Alarm
Configuration blocks: SPEED_MSM.TYPE and SPEED_RED_MGR.BLOCK
(active when speed redundancy is used and speed probe type is passive)
OVRSPD_SP:
Front Panel Indication: Tmp Ovrspd Setpoint On
Configuration block: TEST_MODE_MSM.BLOCK
MAN_SPD_TST:
Front Panel Indication: Manual Sim Speed Test
Configuration block: TEST_MODE_MSM.BLOCK
AUTO_SPD_TST:
Front Panel Indication: Auto Sim Speed Test
Configuration block: TEST_MODE_MSM.BLOCK
AUTO_SPD_FAIL:
Front Panel Indication: Auto Sim Spd Test Fail
Configuration block: TEST_MODE_MSM.BLOCK

74 Woodward
Manual 26712 ProTech GAP Manual
AUTO_SEQ_TST:
Front Panel Indication: Auto Sequence Test
Configuration block: AUTO_TEST.BLOCK
AUTO_SEQ_TO:
Front Panel Indication: Auto Seq Test Timeout
Configuration block: AUTO_TEST.BLOCK
USR_TST_1:
Front Panel Indication: User Defined Test 1
Configuration block: USR_TEST.BLOCK_1.ENABLE
USR_TST_2:
Front Panel Indication: User Defined Test 2
Configuration block: USR_TEST.BLOCK_2.ENABLE
USR_TST_3:
Front Panel Indication: User Defined Test 3
Configuration block: USR_TEST.BLOCK_3.ENABLE
IRIG_LOSS:
Front Panel Indication: IRIG Signal Lost
Configuration block: TIME_SYNC_MSM.MODE
SPD_RM_DIFF:
Front Panel Indication: Speed RM Input Diff. (input difference detected by the
speed redundancy manager)
Configuration block: SPEED_RED_MGR.BLOCK, DIFF_ALM_LIMIT and
DIFF_ALM_TIME

INT_TRIPS_TPS

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS system. This block provides all predefined
internal trips. Boolean values can be connected to other blocks.

FIELD DESCRIPTION:
Inputs
none
Outputs
All outputs have Boolean values and can be connected to other blocks if the output exists
in the allowed list of these blocks. Some of them have to be configured from other
blocks, some are available without configuration.
OVRSPD:
Configuration block: SPEED_TPS.BLOCK

Woodward 75
ProTech GAP Manual Manual 26712
SPD_Loss:
Configuration block: SPEED_TPS.BLOCK
OVRACCEL:
Configuration block: SPEED_TPS.BLOCK
SPD_FAIL:
Configuration block: START_LOGIC.BLOCK
SPD_TO:
Configuration block: START_LOGIC.BLOCK
OPN_WIRE:
No configuration possible.
PWR_UP:
No configuration possible.
INT_FAULT:
No configuration possible.
CONFIG:
No configuration possible.
RESETTABLE:
Configuration block: RESETTABLE_TRIP.BLOCK
PAR_ERR:
No configuration possible.
SPD_RM:
Configuration block: SPEED_RED_MGR.BLOCK

INT_TRIPS_MSM

BLOCK DESCRIPTION:
This block is only available in the MicroNet SM system. This block provides all predefined
internal trips. Boolean values can be connected to other blocks.

FIELD DESCRIPTION:
Inputs
none
Outputs
All outputs have Boolean values and can be connected to other blocks if the output exists
in the allowed list of these blocks. Some of them have to be configured from other
blocks, some are available without configuration.
OVRSPD:
Front Panel Indication: Overspeed Trip
Configuration block: always active, level is based on SPEED_MSM.OVRSPD

76 Woodward
Manual 26712 ProTech GAP Manual
SPD_Loss:
Front Panel Indication: Speed Lost Trip
Configuration block: SPEED_MSM.SPD_LOSS
OVRACCEL:
Front Panel Indication: Overacceleration Trip
Configuration block: SPEED_MSM.ENBL_MAX_ACCEL
SPD_FAIL:
Front Panel Indication: Speed Fail Trip
Configuration block: START_LOGIC.SPD_FAIL_T
SPD_TO:
Front Panel Indication: Speed Fail Timeout
Configuration block: START_LOGIC.SPD_TO_T
OPN_WIRE:
Front Panel Indication: Speed Open Wire Trip
Configuration block: SPEED_MSM.TYPE (active when speed redundancy is
not used and speed probe type is passive)
PWR_UP:
Front Panel Indication: Power Up Trip
Configuration block: TRIP_LATCH_MSM.TRIP_CONF (only active when set
to de-energize-to-trip)
INT_FAULT:
Front Panel Indication: Internal Fault Trip
Configuration block: No configuration possible, always active.
CONFIG:
Front Panel Indication: Configuration Trip
Configuration block: No configuration possible, always active.
RESETTABLE:
Front Panel Indication: Resettable Trip Input
Configuration block: RESETTABLE_TRIP.BLOCK
PAR_ERR:
Front Panel Indication: Parameter Error
Configuration block: No configuration possible, always active.
SPD_RM:
Front Panel Indication: Speed Red Mgr Trip
Configuration block: SPEED_RED_MGR.TWO_IN_FAILED

LAG

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system.
This block´s output performs a lagged value of the connected input according to the
TAU_INDEX value.

Woodward 77
ProTech GAP Manual Manual 26712
FIELD DESCRIPTION:
Inputs
INPUT:
This input requires an analog input from one of the allowed input connections, see
below.
TAU_INDEX:
This input defines the tau value. Possible values are 16 ms, 32 ms, 64 ms, 128 ms,
256 ms, 512 ms, 1024 ms, 2048 ms, 4096 ms. The default value is 512 ms.
Outputs
LAG:
“Output Value” = “Last Output” + ((“Input Value” – “Last Output”) / 2^”Filter
coefficient Exponent”)
“Filter coefficient Exponent” depends on the TAU_INDEX value (16 ms = 2, 32 ms
= 3, . . . , 4096 ms = 10).

LATCH

BLOCK DESCRIPTION:
There are ten latches (set/reset flip-flops) available that can be used to
create the LATCH output available for trips, alarms, or any logical
function. The latch is reset dominant, meaning the output is FALSE if the
RST input is TRUE regardless of the SET input.

FIELD DESCRIPTION:
Inputs
Set:
This input is the selection for the reset-dominant LATCH block SET
input. The SET and RST inputs for each latch can be any function
result from another gate or from an analog input alarm set point,
a timer, etc. Valid values: (see allowed input connections)
RST:
This input is the selection for the reset-dominant LATCH block RST
input. Valid values: (see allowed input connections)

Outputs
LATCH:
Results of the LATCH block function.

NAND

BLOCK DESCRIPTION:
This block has between 2 and 5 Boolean inputs. This block's output will be FALSE only if all
of the Boolean Input Fields are TRUE. If any one of the inputs is FALSE then the output of
this block will be TRUE.

78 Woodward
Manual 26712 ProTech GAP Manual
FIELD DESCRIPTION:
Inputs
RPT:
Add the desired amount of IN_x inputs. The minimum number of inputs allowed is
2 and the maximum number of inputs allowed is 5.
NOTE: All IN_X inputs added to the RPT field require an input from the allowed
input connection list, they cannot be left blank. If an input has no connection, delete
the RPT input using the GAP editor.
IN_x:
This input requires a Boolean input from one of the allowed input connections.
Outputs
NAND:
Results of the NAND block function.

NOR

BLOCK DESCRIPTION:
This block has between 2 and 5 Boolean inputs. This block's output will be TRUE only if all
of the Boolean Input Fields are FALSE. If any one of the inputs is TRUE then the output of
this block will be FALSE.

FIELD DESCRIPTION:
Inputs
RPT:
Add the desired amount of IN_x inputs. The minimum number of inputs allowed is
2 and the maximum number of inputs allowed is 5.
NOTE: All IN_X inputs added to the RPT field require an input from the allowed
input connection list, they cannot be left blank. If an input has no connection, delete
the RPT input using the GAP editor.
IN_x:
This input requires a Boolean input from one of the allowed input connections.
Outputs
NOR:
Results of the NOR block function.

NOT

BLOCK DESCRIPTION:
This block outputs the inverted value of the input. The output will be FALSE if the input is
TRUE and the output will be TRUE if the input if FALSE.

FIELD DESCRIPTION:
Inputs
IN_x:
This input requires a Boolean input from one of the allowed input connections.

Woodward 79
ProTech GAP Manual Manual 26712
Outputs
NOT:
Output results of the block function.

OR

BLOCK DESCRIPTION:
This block has between 2 and 5 Boolean inputs. This block's output will be FALSE only if all
of the Boolean Input Fields are FALSE. If any one of the inputs is TRUE then the output of
this block will be TRUE.

FIELD DESCRIPTION:
Inputs
RPT:
Add the desired amount of IN_x inputs. The minimum number of inputs allowed is
2 and the maximum number of inputs allowed is 5.
NOTE: All IN_X inputs added to the RPT field require an input from the allowed
input connection list, they cannot be left blank. If an input has no connection, delete
the RPT input using the GAP editor.
IN_x:
This input requires a Boolean input from one of the allowed input connections.
Outputs
OR:
Results of the OR block function.

RELAY_OUT

BLOCK DESCRIPTION:
This block drives a Relay with the value of the IN input or with inverted value of the IN input,
depending on the setting of the POLARITY input.

FIELD DESCRIPTION:
Inputs
IN:
This input requires a Boolean value.
POLARITY:
This input inverts the value of IN if it is set to “Inverting”. Default value is “Non
Inverting”.
Outputs
none

RST_FUNC

80 Woodward
Manual 26712 ProTech GAP Manual
BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system. This block is
used to clear module trips and alarms and configure which RST_FUNC blocks shall be
shared between modules. The output of this block can be set from the value of the
IN_RST input on the same block or from RST_FUNC blocks from different modules and
defined at the SHARED_IN_ inputs.

FIELD DESCRIPTION:
Inputs
IN_RST:
This input is the selection for the configurable reset input.
SHARED_IN_1:
This input configures which RST_FUNC of the three modules shall be shared to the
module set in this block. Allowed values are “Module A Reset”, “Module B Reset”,
“Module C Reset” and “Not Used”. Default value is “Not Used”.
SHARED_IN_2:
This input configures which RST_FUNC of the three modules shall be shared to the
module set in this block. Allowed values are “Module A Reset”, “Module B Reset”,
“Module C Reset” and “Not Used”. Default value is “Not Used”.
SHARED_IN_3:
This input configures which RST_FUNC of the three modules shall be shared to the
module set in this block. Allowed values are “Module A Reset”, “Module B Reset”,
“Module C Reset” and “Not Used”. Default value is “Not Used”.
Outputs
RST_FUNC:
This is the Boolean output of the block.

RESETTABLE_TRIP

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system. The
RESETTABLE_TRIP block is used to enable the pre-configured resettable trip feature.

FIELD DESCRIPTION:
Inputs
ENABLE:
Set to “Used” to enable this function. Valid values are “Not Used” or “Used”. The
default value is “Not Used”.
IN_SEL:
Selection for the configurable reset input.
Outputs
None

SPD_OVRR

Woodward 81
ProTech GAP Manual Manual 26712
BLOCK DESCRIPTION:
This is used as part of the Start Logic “Speed Fail Trip” function. When
this function is enabled, closing the Speed-Fail-Override contact
overrides the Speed Fail Trip. This is a level sensitive trigger so the
contact must remain closed to prevent the Speed Fail Trip until speed is
greater than the speed fail setpoint. Refer to the Start Logic section
below for additional details.

FIELD DESCRIPTION:
Inputs
none
Outputs
SPD_OVRR:
This is the Boolean output of the block.

SPEED_RED_MGR

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS or MicroNet SM system.
This block is a Speed Redundancy Manager that performs a voting on two or three connected
remote acceleration inputs. The voting logic is described in the SPEED_OUT output
description below.

FIELD DESCRIPTION:
Inputs
INPUT_1:
This input can be connected with a remote speed input from one of the three
Modules.
INPUT_2:
This input can be connected with a remote speed input from one of the three
Modules.
INPUT_3:
This input can be connected with a remote speed input from one of the three
Modules.
BASE_FUNC:
This input defines the voting logic if three inputs are connected and valid. Default
value is “Median”.
FALLBACK:
This input defines the voting logic if two inputs are connected and valid. Default
value is “HSS”.
DIFF_ALM_LIMIT:
This input defines the threshold for a difference alarm. The difference alarm occurs
when the difference between two valid inputs exceeds the threshold for the time
defined at DIFF_ALM_TIME. Default value is 100 RPM.

82 Woodward
Manual 26712 ProTech GAP Manual
DIFF_ALM_TIME:
This input defines the time for a difference alarm, see DIFF_ALM_LIMIT. Default
value is 500 ms.
TWO_IN_FAILED:
This input defines if a Trip shall occur if two of three inputs are invalid. The default
value is “TRIP”.
Outputs
SPEED_OUT:
If three inputs are connected and valid:
BASE_FUNC set to Median: This output will have the value of the input value
between the other two input values.
BASE_FUNC set to HSS: This output will have the value of the highest input
value.
BASE_FUNC set to LSS: This output will have the value of the lowest input
value.

If two/three inputs are connected and only two are valid:

FALLBACK set to HSS: This output will have the value of the highest input
value.
FALLBACK set to LSS: This output will have the value of the lowest input
value.

If one/two/three inputs are connected and only one is valid: This output will have
the same value as the valid input.

If one/two/three inputs are connected and no input is valid: This output will be set to
0.
IN_1_INVALID:
This block's output will be TRUE if input INPUT_1 is invalid, else this output will
be FALSE.
IN_2_INVALID:
This block's output will be TRUE if input INPUT_2 is invalid, else this output will
be FALSE.
IN_3_INVALID:
This block's output will be TRUE if input INPUT_3 is invalid, else this output will
be FALSE.

SPEED_TPS

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS system. This block configures the Speed and
Acceleration behavior of the ProTechTPS and also provides the Speed and Acceleration
Inputs for Connection.

Woodward 83
ProTech GAP Manual Manual 26712
FIELD DESCRIPTION:
Inputs
Type:
This input defines the Probe Type of the Speed Input. Possible values are “Active”
or ”Passive”. Default value is “Passive”.
gear_teeth:
This input defines the number of Gear Teeth. Possible values are 1 to 320.
Default value is 60.
gear_ratio:
This input defines the Gear Ratio. Possible values are 0.1 to 10.0.
Default value is 1.
ovrspd:
This input defines the Overspeed Trip Threshold. If the Speed value exceeds this
Threshold a Trip occurs. Possible values are 100 to 32000.
Default value is 100.
spd_loss:
This input defines how to handle a sudden speed loss. If “Trip” is selected, a sudden
speed loss will cause a Trip. If “Alarm” is selected, a sudden speed loss will cause
an Alarm.
Default value is “Trip”.
enbl_MAX_acc:
This input defines if the Acceleration Trip is enabled or not. If “Yes” is selected the
Acceleration Trip is enabled. If “No” is selected there is no Acceleration Trip
possible.
Default value is “No”.
min_spd:
This input defines which Speed Threshold has to be exceeded to enable the
Acceleration Trip. Possible values are 0 to 32000.
Default value is 100.
MAX_Accel:
This input defines the Acceleration Threshold. If this value exceeds the acceleration
and MIN_SPD as well as ENABL_ACC are active a Trip occurs. Possible values
are 0 to 25000.
Default value is 0.
Outputs
SPEED_In:
This output is the Speed Input in RPM.
Accel_in:
This output is the Acceleration Input in RPM/s.
SPEED_inVALID:
This output can´t be connected to any input. The value of this output can be set
manually with NetSim and is for simulation only. If SPEED_IN is connected to a
Redundancy/Shared Block and the value of this output is set to TRUE it simulates
an invalid SPEED_IN value for the redundancy/shared block logic.
Accel_inVALID:
This output can´t be connected to any input. The value of this output can be set
manually with NetSim and is for simulation only. If ACCEL_IN is connected to a
Redundancy/Shared Block and the value of this output is set to TRUE it simulates
an invalid ACCEL_IN value for the redundancy/shared block logic.

84 Woodward
Manual 26712 ProTech GAP Manual

START_FUNC

BLOCK DESCRIPTION:
This block is used as part of the START_LOGIC “Speed Fail Timeout
Trip” function. When this function is Enabled, closing the Start contact
will start the Speed Fail Timeout timer. This is an edge triggered signal
and re-selecting Start will re-start this timer. Refer to the Start Logic
section below for additional details.

FIELD DESCRIPTION:
Inputs
none
Outputs
START_FUNC:
This is the Boolean output of the block.

TIME_SYNC_TPS

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS system. This block changes the time of a
ProTechTPS if SYNC_IN becomes TRUE, depending on the MODE configuration. This
allows time synchronization between different devices.

FIELD DESCRIPTION:
Inputs
MODE:
This input selects the time synchronization mode. Possible values are “Not Used”
and “24h Time Sync”. Default value is “Not Used”.
Sync_in:
This input triggers the time synchronization if MODE is configured to “24h Time
Sync”.
TIME_H:
This input defines the hours of the time to be set if MODE is configured to “24h
Time Sync”.
TIME_M:
This input defines the minutes of the time to be set if MODE is configured to “24h
Time Sync”.
TIME_S:
This input defines the seconds of the time to be set if MODE is configured to “24h
Time Sync”.
Outputs
none

Woodward 85
ProTech GAP Manual Manual 26712

TIME_SYNC_MSM

BLOCK DESCRIPTION:
This block is only available in the MicroNet SM system. This block changes the time if
SYNC_IN becomes TRUE or over an IRIG signal, depending on the MODE configuration.
This allows time synchronization between different devices.

FIELD DESCRIPTION:
Inputs
MOde:
This input selects the time synchronization mode. Possible values are “Not Used”,
“24h Time Sync” and “IRIG-B”. Default value is “Not Used”.
Sync_in:
This input triggers the time synchronization if MODE is configured to “24h Time
Sync”.
TIME_H:
This input defines the hours of the time to be set if MODE is configured to “24h
Time Sync”.
TIME_M:
This input defines the minutes of the time to be set if MODE is configured to “24h
Time Sync”.
TIME_S:
This input defines the seconds of the time to be set if MODE is configured to “24h
Time Sync”.
Outputs
none

TIMER

BLOCK DESCRIPTION:
This block starts counting time if the SET input is TRUE and the RST input is FALSE. The
TIMER output shows the elapsed time. If the time value exceeds the value of
SET_HI/SET_HIHI, the value of OUT_HI/OUT_HIHI will be TRUE.
If RST is TRUE, the value of the TIMER output is 0 and the OUT_HI/OUT_HIHI outputs are
FALSE, independent of the SET value.

86 Woodward
Manual 26712 ProTech GAP Manual
FIELD DESCRIPTION:
Inputs
SET:
This input starts counting the time if RST is FALSE.
RST:
This input sets TIMER back to 0 and OUT_HI/OUT/HIHI back to FALSE.
SET_HI:
This analog input allows a value in seconds from 0 to 3600. Default value is 0.001
s.
SET_HIHI:
This analog input allows a value in seconds from 0 to 3600. Default value is 0.001
s.
Outputs
TIMER:
This output displays the counting time. This output can´t be connected to any input.
It is for visualization only.
OUT_HI:
If the TIMER output exceeds the value of the SET_HI input, this output becomes
TRUE.
OUT_HIHI:
If the TIMER output exceeds the value of the SET_HIHI input, this output becomes
TRUE.

TRIP_LATCH_TPS

BLOCK DESCRIPTION:
This block is only available in the ProTechTPS system. The output of this block goes TRUE if
one of the Boolean INT_TRIPS or INPUT_X inputs is TRUE. The output remains TRUE until
the RST_FUNC input goes TRUE and all other inputs are FALSE. The block has predefined
inputs and up to 25 user defined inputs.

FIELD DESCRIPTION:
Inputs
TRIP_CONF:
This Input configures the trip state. Possible values are “de-energize-to-trip” or
“energize-to-trip”. When configured as de-energize-to-trip, the modules power up
in the tripped state. When configured as energize-to-trip, the modules power up
such that they do not enter the tripped state unless a trip condition is present.

Woodward 87
ProTech GAP Manual Manual 26712
OUTPUT_MODE:
This Input configures the trip output mode. Possible values are “Non Latching” or
“Latching”. The default value is “Latching”.
INT_TRIPS:
OVRSPD, SPD_LOSS, OVRACCEL, SPD_FAIL, SPD_TO, OPN_WIRE,
PWR_UP, INT_FAULT, CONFIG, RESETTABLE, PAR_ERR, SPD_RM.
These inputs are predefined. They don’t have to be connected for creating a .wset
file. The values come from the outputs of the INT_TRIPS_TPS block. See link
below.
Internal trip TPS.
RPT:
Add the desired amount of RPT fields. Each added RPT field includes an INPUT_X
and a NAME_X input.
INPUT_X: This input may be blank or requires a Boolean input from one of the
allowed input connections.
NAME_X: This input can be used to define a 24 character name of the input X. If it
is left blank, the default value will be used. The default value is “Trip Latch Input
X”. X is a number from 1 - 25
RST_FUNC:
This Input may be blank or has to be connected to the output of the RST_FUNC
block.
Outputs
Trip_LATCH:
This Boolean output goes TRUE if one of the INT_ALARMS inputs or one of the
INPUT_X inputs is TRUE. When OUTPUT_MODE is configured as “Non
Latching”, this output goes FALSE with a delay of 1 s if all inputs are FALSE and
RST_FUNC is FALSE or doesn´t exist. If RST_FUNC is TRUE and all inputs are
FALSE this output goes FALSE without delay. When configured as “Latching”, the
output goes FALSE when all inputs are FALSE and the RST_FUNC is TRUE.
Trip_INVALID:
This output can´t be connected to any input. The value of this output can be set
manually with NetSim and is for simulation only. If TRIP_LATCH is connected to
a Redundancy/Shared Block and the value of this output is set to TRUE it simulates
an invalid TRIP_LATCH value for the redundancy/shared block logic.

TRIP_LATCH_MSM

BLOCK DESCRIPTION:
This block is only available in the MicroNet SM system. The output of this block goes TRUE
if any one of the Boolean INT_TRIPS or INPUT_X inputs is TRUE. When configured for
‘Latching’ mode (see OUTPUT_CONF), the output remains TRUE until the RST_FUNC
input goes TRUE and all latch inputs are FALSE. When mode is set to ‘Non Latching’, the
output will go FALSE when all inputs are FALSE. The block has predefined inputs and up to
25 user defined inputs.

88 Woodward
Manual 26712 ProTech GAP Manual
FIELD DESCRIPTION:
Inputs
TRIP_CONF:
This Input configures the trip state. Possible values are “de-energize-to-trip” or
“energize-to-trip”. When configured as de-energize-to-trip, the modules power up
in the tripped state. When configured as energize-to-trip, the modules power up
such that they do not enter the tripped state unless a trip condition is present.
OUTPUT_MODE:
This Input configures the trip output mode. Possible values are “Non Latching” or
“Latching”. The default value is “Latching”.
INT_TRIPS:
OVRSPD, SPD_LOSS, OVRACCEL, SPD_FAIL, SPD_TO, OPN_WIRE,
PWR_UP, INT_FAULT, CONFIG, RESETTABLE, PAR_ERR, SPD_RM.
These inputs are predefined and may be blank or connected to the outputs of the
INT_TRIPS_MSM block. If left blank, the default values will be used. The default
values are the INT_TRIPS_MSM block outputs. They don’t have to be connected
for creating a wset file, these connections are provided only for clarification and
NETSIM purposes.
RPT:
Add the desired amount of RPT fields. Each added RPT field include a INPUT_X
and a NAME_X input.
INPUT_X: This input may be blank or requires a Boolean input from one of the
allowed input connections.
NAME_X: This input can be used to define a 24 character name of the input X. If it
is left blank, the default value will be used. The default value is “Trip Latch Input
X”. X is a number from 1 - 25
RST_FUNC:
This Input is predefined and may be blank or connected to the output of the
RST_FUNC block. If it is left blank, the default value will be used. The default
value is the RST_FUNC block output.
Outputs
Trip_LATCH:
This Boolean output goes TRUE if one of the INT_ALARMS inputs or one of the
INPUT_X inputs is TRUE. When OUTPUT_MODE is configured as “Non
Latching”, this output goes FALSE with a delay of 1 s if all inputs are FALSE and
RST_FUNC is FALSE or doesn´t exist. If RST_FUNC is TRUE and all inputs are
FALSE this output goes FALSE without delay. When configured as “Latching”, the
output goes FALSE when all inputs are FALSE and the RST_FUNC is TRUE.
Trip_INVALID:
This output can´t be connected to any input. The value of this output can be set
manually with NetSim and is for simulation only. If TRIP_LATCH is connected to
a Redundancy/Shared Block and the value of this output is set to TRUE it simulates
an invalid TRIP_LATCH value for the redundancy/shared block logic.

TRIP_TIMER

Woodward 89
ProTech GAP Manual Manual 26712
BLOCK DESCRIPTION:
A trip cycle timer is a function that measures the time from a trip
event until the
trip is confirmed by an input (for instance trip and throttle valve limit
switch), or by
any internally created logic function. An Alarm is indicated if the time
is expired
before the feedback confirmation is received. There are two trip cycle
timers.

FIELD DESCRIPTION:
Inputs
INDICATOR:
This input is the selection for the indicator feedback.
MAX_TIME:
The Maximum Cycle Time defines the time allowed between a trip occurrence and
the feedback confirmation. This value is expressed in milliseconds. Valid values: 1-
60000 ms. Default value is 1.
Outputs
none

UNIT_DLY

BLOCK DESCRIPTION:
Ten unit delay blocks are available to break loops in the configurable
logic by forcing a specific execution order. The output of the unit delay
equals the input of the block the last time it was executed. Properly
inserting a unit delay block in the loop will enforce program execution
and satisfy the loop check algorithm.

FIELD DESCRIPTION:
Inputs
IN:
Selection for the block input. The input field for each unit delay can
be any function result from another gate or from an analog input
alarm setpoint, or a timer, etc.

OUTPUTS
UNIT_DLY:
This output has the same value as the IN value.

XNOR

BLOCK DESCRIPTION:
This block has 2 Boolean Inputs. This block’s output is TRUE if both of the Boolean Input
Fields have the same value. If the inputs have different values the output of this block will be
FALSE.

90 Woodward
Manual 26712 ProTech GAP Manual
FIELD DESCRIPTION:
Inputs
IN_X:
This input requires a Boolean input from one of the allowed input
connections.
Outputs
XNOR:
Result of the XNOR block function.

XOR

BLOCK DESCRIPTION:
This block has 2 Boolean Inputs. This block’s output is TRUE if the Boolean Input Fields
have different values. If the inputs have the same value the output of this block will be
FALSE.

FIELD DESCRIPTION:
Inputs
IN_X:
This input requires a Boolean input from one of the allowed input
connections.
Outputs
XOR:
Result of the XOR block function.

Woodward 91
 We appreciate your comments about the content of our publications.
Send comments to: [email protected]

Please reference publication 26712.

PO Box 1519, Fort Collins CO 80522-1519, USA

1000 East Drake Road, Fort Collins CO 80525, USA
Phone +1 (970) 482-5811  Fax +1 (970) 498-3058

Email and Website—www.woodward.com

Woodward has company-owned plants, subsidiaries, and branches,

as well as authorized distributors and other authorized service and sales facilities throughout the world.
Complete address / phone / fax / email information for all locations is available on our website.