Advc2-3001 CLT Manual

Custom Logic Tool
User Guide
Custom Logic Tool (CLT)
for ADVC Controller Range
Additional logic functionality for recloser systems
Make the most of your energy

Scope of This Document
This document describes the user configuration Copyright

and application of the Custom Logic Tool for the © 2011 Schneider Electric. All rights reserved.
ADVC Controller.
No part of the contents of this document may
Limitations be reproduced or transmitted in any form or by
This document is protected by copyright and is any means without the written permission of the
provided solely for the use of the purchaser. It manufacturer.
is not to be copied in any way, nor its contents
divulged to any third party. It is not to be
used as the basis of a tender or specification Document part number
without the express written permission of the ADVC2-3001
manufacturer.
Revision
Disclaimer 1-2
The advisory procedures and information
contained within this document have been
compiled as a guide to the safe and effective
operation of products supplied by Schneider
Electric (Australia) Pty Ltd.
It has been prepared in conjunction with
references from sub-assembly suppliers and the
collective experience of the manufacturer.
In-service conditions for use of the products
may vary between customers and end-users.
Consequently, this document is offered as a
guide only. It should be used in conjunction
with the customer’s own safety procedures,
maintenance program, engineering judgment
and training qualifications.
No responsibility, either direct or consequential,
for injury or equipment failure can be accepted
by the manufacturer resulting from the use of
this document.
2 | Schneider Electric
Contents
1.0 Introduction 5 5.0 Logic Expressions 25

1.1 Compatibility 5 5.1 Logic Expression Builder Interface 25
1.2 Ratings 5 5.1.1 Introduction 25
5.1.2 Operands Toolbox 25
2.0 Quick Start Guide 6
5.1.3 Point Values Toolbox 26
3.0 Create a Custom Logic Map 8 5.1.4 Formatting Toolbox 26
3.1 Open the CLT User Interface 8 5.1.5 Data Points Window 26
3.1.1 Open a New CLT map 8 5.1.6 Filter Data Points 26
3.1.2 Open an Existing CLT map 8 5.2 Operands 26
3.1.3 File Names 8 5.2.1 Logic Operands 27
3.1.4 File Location 9 5.2.2 Analogue Operands 27
3.1.5 Process to Edit the CLT Map 9 5.2.3 Mathematical Operands 28
5.3 Database Points 28
4.0 The Custom Logic Tool 5.3.1 Digital Database Points 28
User Interface 10
5.3.2 Analogue Database Points 29
4.1 CLT User Interface 10
5.3.3 Control Database Points 30
4.2 Custom Logic Tool Menu 11
5.4 Creating Logic Expressions 30
4.3 Design and Edit Logic Characteristics 11
5.4.1 Logic Data Points 30
4.4 Editing the Different Types
of Parameters 12 5.4.2 Analogue Data Points 31
4.4.1 Editing the Basic Parameters 12 5.4.3 Optimising the Logic Expressions 31
4.4.2 Editing the Advanced Parameters 12 5.4.4 Latched and Unlatched
Database Points 31
4.5 Custom Digitals 12
5.4.5 Digital Set and Reset Expressions 33
4.5.1 About Custom Digitals 12
4.5.2 Digitals Configuration Worksheet 12 6.0 Loading CLT Maps to
4.6 Custom Variables 15 the Controller 34
4.6.1 About Custom Variables 15
7.0 Integrating Custom
4.6.2 Variables Configuration Worksheet 16 Logic Points 35
4.7 Custom Counters 18
4.7.1 About Custom Counters 18 8.0 Event Log Entries 36
4.7.2 Counters Configuration Worksheet 18
9.0 Practical Examples 37
4.7.3 Counter Behaviour 20
9.1 Analogue Alarms 37
4.7.4 Counter Maximum Values and Rollover 21
9.2 Two Stage Low battery Alarm 41
4.8 Custom Timers 22
4.8.1 About Custom Timers 22
4.8.2 Timers Configuration Worksheet 23
Custom Logic Tool User Guide (ADVC2-3001) | 3

List of Figures
Figure 1: CLT new configuration 8 Revision history:

Figure 2: Existing configuration 8
Rev 1-0 Initial release 30 Sep 2011
Figure 3: CLT map editing process 9
Rev 1-1 Minor update – 3 Oct 2011
Figure 4: CLT user Interface 10 Chapter 9 “≤”, “≥”
Figure 5: Custom Digitals flow diagram 12 symbols lost in PDF
conversion
Figure 6: Custom Digitals worksheet window 12
Rev 1-2 Counters are 18 Oct 2011
Figure 7: Custom Variables flow diagram 14 included in the
feature
Figure 8: Custom Variables
worksheet window 16
Figure 9: Custom Counters flow diagram 18
Figure 10: Counter configuration
worksheet window 18
Figure 11: Timer comparison 22
Figure 12: Custom Timers flow diagram 23
Figure 13: Timer configuration
worksheet window 23
Figure 14: Logic expression builder window 25
Figure 15: Operands toolbox 25
Figure 16: Point values toolbox 26
Figure 17: Formatting toolbox 26
Figure 18: Data Points window 26
Figure 19: Filter Data Points 26
Figure 20: Analogue operands and a
counter database point 27
Figure 21: Analogue logging option 31
Figure 22: Building logic expressions 32
Figure 23: Analogue reset expression 33
Figure 24: Custom Logic to communicate,
control and indicate 35
1.0 Introduction
The Custom Logic Tool (CLT) provides the user with an opportunity to develop additional logic
functionality for the ADVC Controller Range. By evaluating user-defined collections of digital and
analogue data points from the existing Protocol Database, the CLT is used to alert operators of
specific conditions that may exist on-site. Based on these conditions, it is also possible to perform
basic actions automatically if required.
WSOS5 incorporates the newly developed CLT user interface that is used to create the custom logic
expressions. In addition to CLT, WSOS5 also incorporates other customisation tools that are used
to manage Communication Protocols, Operator Interface and Input/Output devices. Each of these
tools operates independently, provides the user access to the Protocol Database points and offers
a limited level of logic functionality. CLT significantly enhances the logic capabilities of all of these
tools by providing additional Protocol Database points. These new points can be incorporated in the
existing configuration of these tools (see chapter 7).
The CLT incorporates the following functionality:
Custom Digitals Design your own logic functions to provide True/False state indication
and execute actions based on the result of logic expressions.
Custom Variables Preset variable values used in logic expressions. Modify the active
values via protocol to easily adapt the custom logic functionality to
different conditions or applications.
Custom Counters Create counters to monitor the number of transitions in logic
expressions. The counter values are available via protocol and are used
in the custom logic functions (under development).
Custom Timers Create timers to monitor the duration of transitions in a logic expression.
The subsequent chapters describe the CLT operator interface and the functionality of the different
elements. They also contains some practical examples.
1.1 Compatibility
ADVC Controller firmware: A45-03.00+
WSOS 5 version: Version 5.13.01+
Switchgear: N-Series, U-Series, W-Series, RL-Series
Functionality: ACR (Automatic Circuit Recloser), LBS (Automatic Sectionaliser).
1.2 Ratings
These timing results are from tests performed over different controller conditions such as loading
CPU to max, all protection elements pickup, etc. In normal usage, the timing values will be less.
Response time for logic functions 2.3 seconds

Response time for analogue functions 3.2 seconds
Response time for timer functions 2.1 seconds
Expression size limitation 255 elements
WARNING
UNEXPECTED EQUIPMENT OPERATION
• The designer of any logic or control function must consider the potential failure modes and
provide a means to achieve a safe state during and after a failure. Examples of critical control
functions are Work Tag, Hot Line Tag, Trip and Close Operations.
• Separate safety procedures must be provided for critical control functions.
• Consideration must be given to the implications of logic functionality, anticipated response
times and system operating characteristics.
• Each implementation of a Custom Logic Map must be individually and thoroughly tested for
proper operation before being placed into service.
Failure to follow these instructions can result in unexpected operation and
associated attendant hazards.

2.0 Quick Start Guide
Ensure the correct version of WSOS is installed and the correct controller firmware is available.
❏ Install WSOS Version 5.13.01+ or later. – Follow the on-screen instructions.
❏ Download controller firmware A45-03.00+ or higher. The firmware version is needed to create a logic map.
Create a Custom Logic map
Open CLT user interface Select the CLT configuration window

Browse the WSOS menu:
Create new map Configuration
> Customise Select “New” option. Configure product, type
>> Custom Logic Tool and firmware version.
>>> Open.
Open existing map Select from list
Select “Existing” option. Select required map from
a list of *.clt file names.
CLT User Interface
Custom Digitals Custom Variables Custom Counters Custom Timers

Provides True/False state Preset variables used in Counts transitions in logic Provides a logic output
indication and executes logic expressions. Modify expressions and provides when the duration of
actions based on the active values via protocol an analogue output for a transition in a logic
result of logic expressions. to adapt functionality to other logic expressions. expression exceeds a
different applications. preset value.
64 logic points 32 counters
Output: True/False 32 custom variables Output: Active value 32 timers
Output: Default value Output: True/False
User presets: User presets:
❏ Name User presets: ❏ Name User presets:
❏ Set expression ❏ Name ❏ Minimum value ❏ Name
❏ Reset expression ❏ Default value ❏ Maximum value ❏ Type
❏ Set action ❏ Override option ❏ Default value ❏ Resolution
❏ Reset action ❏ Logging option ❏ Reset value ❏ Duration
❏ Comment ❏ Comment ❏ Default expression ❏ Reset expression
❏ Reset expression ❏ Start/Stop expression
Note: WSOS assigns
Left-click to select and ❏ Increment expression ❏ Comment
the scale for variables in
edit each point. Select “fx” ❏ Decrement expression
expressions.
to enter expression. ❏ Comment Left-click to select and
Left-click to select and edit each point. Select “fx”
edit each point. to enter expression.
Left-click to select and
edit each point. Select “fx”
to enter expression.
Expression Builder
❏ Select protocol database point by double
clicking on the data point name.
❏ Add the operand to the expression.
❏ Repeat above until expression is complete.
❏ Press “Apply” button when all the fields are
complete.
Save the CLT map.

> Custom Logic Tool
>> Save (or Save As)
Prepare ADVC Controller
❏ Select the switchgear and ADVC Controller that will be running the custom logic function.
❏ Update the controller firmware to A45-03.00+ or higher.
❏ While offline, select the switchgear device in WSOS. In “Configuration – Feature Selection” make the custom logic tool
available by selecting the “Custom Logic Tool Available” option in the “General” section.
Using the Custom Logic map
Establish relationship between CLT, IOEX, CPMT and OCP

❏ The CLT function controls the status of 64 new custom logic points. These points are available as inputs to the
other tools. Open existing or create new maps in these tools to utilise the new custom logic points.
❏ In addition to the 64 custom logic points, 32 custom variable CLT inputs are available via protocol. The active value
of the variable can be changed via protocol.
Protocol Database
Digital Analogue Accumulator Digital Custom Analogue

data data data controls logic controls
IOEX Tool OCP Tool CPMT Tool

Configures the Input/Output Configures logic expressions for Configures the switchgear
characteristics and logic status indication and set actions information and controls available
functions required for external linked to quick keys on the via the selected protocol used in
devices. flexVUE operator interface. a communication link.
❏ Link IOEX inputs to digital ❏ Use digital data and logic ❏ Select the required information
controls to achieve the desired expressions for status from the protocol database for
action (effect). indication. communication via protocol.
❏ Create logic expression to ❏ Link digital controls and quick ❏ Operation is described in a
drive specific IOEX outputs. keys to provide operator separate manual.
❏ Operation is described in a control of specific functions
Inputs:
separate manual.
Inputs: ❏ The entire protocol database
Inputs: ❏ Digital switchgear data including custom logic
❏ Digital switchgear data ❏ Custom logic digital data digital data.
❏ Custom logic digital data
Outputs: Outputs:
Outputs: ❏ Digital control of switchgear ❏ Digital control of switchgear
❏ Digital control of switchgear ❏ Assert IOEX outputs
❏ Override custom variables in
the CLT tool
Save the Save the Save the

IOEX map OCP map CPMT map
Attach the required Go online with the Write the maps to the
maps to the switchgear switchgear switchgear
Test the customised behaviour

Go online with the switchgear. Open the Custom Logic Tool window and monitor the digital data status, while stimulating
the necessary inputs.

3.0 Create a Custom Logic Map
WSOS version 5.13.01+ or later contains the Custom Logic Tool. It is
possible to create CLT maps without having the controller connected to
the PC. This chapter describes how to create a new or open an existing
CLT map.
3.1 Open the CLT User Interface

To open an existing or create a new CLT map, browse to the “Customise”
menu in the WSOS menu toolbar, select “Open” from the “Custom Logic
Tool” option in the “Customise” WSOS menu toolbar. An “Open Custom
Logic Tool Configuration” window will be displayed.
> Customise
>> Custom Logic Tool
>>> Open.
3.1.1 Open a New CLT Map

Create a new CLT map by selecting the “New” option. Define the
configuration of the map. The configuration allows the user to set up a
map for a specific type of switchgear by selecting one of the following
product options:
❏ U-Series 3-phase up to 27kV recloser
❏ W-Series 1-phase SWER recloser
❏ N-Series 3-phase up to 38kV recloser
❏ RL-Series 3-phase up to 38kV sectionaliser.
Alternatively, if a map will be used across different types of switchgear
(example N-Series and U-Series) select the following option:
Figure 1: CLT new configuration
❏ All Switchgear (all types of switchgear).
The Switchgear Type (ACR or LBS) defines the function of the switchgear.
It is also necessary to configure the firmware version used on the
controllers. The software version controls the availability of database
points.
Note: If an incorrect software version is specified, the CLT tool may
include database points that are not supported by the controller. This
could result in errors when the controller executes the CLT map.
Click the “Open” button when complete.
3.1.2 Open an Existing CLT Map

It is possible to open/edit an existing CLT map by selecting the “Existing”
option in the window. Select the file from the list in the “Configuration”
frame and click the “Open” button. This action displays the Custom Logic
Tool (CLT) user interface (see chapter 4).
3.1.3 File Names

When a new CLT file is created, WSOS automatically names the file
“Custom Logic Tool Configuration.clt”. The files are identified by a “*.CLT”
extension. If the file already exists a number suffix is automatically added
to the file name – for example “Custom Logic Tool Configuration1.clt”. To
change the file name, use the “Save As” option in the Custom Logic Tool
Figure 2: Existing configuration menu (see paragraph 4.2).
3.1.4 File Location
The *.CLT file location is set in the Directories tab of the System Properties window. Access the
System Properties window via the Customise > Properties menu. The default location is in the
following directory:
“C:\Documents and Settings\All Users\Application Data\WSOS Switchgear Data\
Custom Logic Tool”.
3.1.5 Process to Edit the CLT Map

The flow diagram in Figure 3 shows the basic process to edit a CLT map. Chapters 4 and 5 describe
each part of the process in detail.
CLT User Interface (see page 8).

Select Configuration View configuration in a View live status when
Worksheet to display compact format online with controller
Select the point to edit by

clicking in the row (offline)
Custom Logic Tool Worksheet Interface

(see page 9).
View all the relevant parameters Select parameter Type in or select new
available in the worksheet to edit parameters
fx Edit logic expressions in

expression builder
Logic Expression Builder

(see page 23).
Create the logic Find Select

expression data point data point
Add
operand
Figure 3: CLT map editing process

4.0 The Custom Logic Tool User Interface
The CLT user interface offers a dashboard from where users can select the components to edit, view
the CLT map configuration and display the online status during commissioning or testing.
Chapter 4.3 describes how to edit the CLT map.
Digitals Variables Counters Timers Firmware version CONFIGURATION MODE

Switchgear type
Selection buttons Configuration information Mode

The CLT Worksheet Area displays the status and configuration
Custom or Custom or Custom or Custom Timers
Digitals Variables Counters
Rows Columns – online Columns – user configuration fields.

status indication.
Figure 4: CLT user interface
4.1 CLT User Interface

The CLT user interface contains the following components: selection buttons, configuration
information, configuration worksheet area and a Custom Logic Tool menu.
Selection Buttons – The four buttons, located on the top left of the CLT user interface, are used to
display the different configuration worksheets in the worksheet area. Left-clicking on the button will
display the corresponding worksheet.
Configuration Information – Also located on the top, the two fields displaying the firmware
version and the switchgear type chosen for the map.
Mode – The mode field displays CONFIGURATION MODE when offline and editing the map. When
online the CLT map name is displayed.
Configuration Worksheet Area – This area displays the online status and configuration of each
available parameter for the custom digital, variable, counter and timer functions. Each function offers
the user a collection of database points. The result of the database points are determined by the
function of the point, user-defined logic expressions and preset values.
The configuration worksheet is arranged with the database points as rows and the user-defined
parameters as columns. Please see chapter 4.3 for more detail on the worksheet.
Users can swap between the worksheets by using the buttons or the CLT menu.
4.2 Custom Logic Tool Menu
A “Custom Logic Tool” menu is displayed when the CLT user interface
is open. This menu provides normal file managing type options such as
“Open”, “Save” and “Save As”. It also provides options to view the four
main CLT configuration worksheets:
❏ Custom Digitals
❏ Custom Variables
❏ Custom Counters
❏ Custom Timers.
Browse the WSOS menu – From the CLT menu it also possible to print a copy of the configuration file
>Custom Logic Tool menu for record keeping or review.
>> Open This menu also provides the option “Version Upgrade” to modify the
>> Custom Digitals firmware version selected for a CLT map. It is possible to upgrade the
>> Custom Variables firmware version to a newer or the latest version. However, it is not
>> Custom Counters possible to change to an earlier version of firmware. Please follow the
>> Custom Timers onscreen instructions to update the firmware version. Updating makes
>> Print Configuration File available the latest set of database points for inclusion in the CLT map.
>> Save However it does not upgrade the controller firmware. To update the
>> Save As controller firmware it is necessary to use the “ADVC Loader Tool” that can
>> Version Upgrade be accessed via the “Customise” menu.
4.3 Design and Edit Logic Characteristics

This chapter firstly describes how to edit the different types of parameters and then the different
configuration worksheets available in the CLT user interface. Separate worksheets are provided to
configure the parameters required for the logic, values, counters and timers within the CLT map.
Paragraphs 4.1 and 4.2 describe how to switch between the different worksheets. There are four
configuration worksheets, these are:
❏ Custom Digitals. See paragraph 4.5 for a description of all parameters.
❏ Custom Variables. See paragraph 4.6 for a description of all parameters.
❏ Custom Counters. See paragraph 4.7 for a description of all parameters.
❏ Custom Timers. See paragraph 4.8 for a description of all parameters.
Each Configuration Worksheet has an associated editing tool. The tool displays and allows editing
of the function’s parameters. There are six different types of parameters, each requiring a slightly
different editing technique. The table below summarises the different types of parameters.
Configuration worksheets
Parameter type Digitals Variables Counters Timers
Text Name, Name, Name, Name,
Comment Comment Comment Comment
Basic parameters
Values Default Minimum, Duration

Maximum,
(See 4.4.1)
Default,
Reset
Tick box Override
value
Selection list Type,
Resolution
Logic expressions Set, Default, Reset,
parameters
(See 4.4.2)
Reset Reset, Start/Stop

Advanced
fx Increment,
Decrement
Actions Set,
fx Reset
Display contents of point n-1, where “n” is the current point. Does
UP arrow
not apply any changes to the current point.
Common
controls
Display contents of point n+1, where “n” is the current point. Does
Down arrow
not apply any changes to the current point.
Apply button Apply Applies the changes in the current point to the map.

4.4 Editing the Different Types of Parameters
To edit the parameters, select the correct configuration worksheet, identify the row to edit and left
click on any of the fields in the row. That will open the digital editing window. Edit the parameters.
The parameters can be grouped in two:
❏ Basic parameters – these parameters are keyed in directly or selected using a mouse click.
❏ Advanced parameters – an expression builder window is used to create these parameters.
4.4.1 Editing the Basic Parameters

Editing the basic parameters are extremely easy. Please see the basic instructions provided below.
Text Select and delete the existing text. Type the new text.
Values Select and delete the existing value. Type the new value.
Tick box Click in the square box provided to select/deselect the option.
Selection list Click on the field to display the list of possible options and select the correct one.
4.4.2 Editing the Advanced Parameters

A Logic Expression Builder is used to create the logic functions and actions. Use the “fx “symbol
to open the Logic Expression Builder window. The builder is used to insert database points and
operands in the expression field.
Chapter 5 describes in detail how to use the Logic Expression Builder.
4.5 Custom Digitals

4.5.1 About Custom Digitals
With Custom Digitals you create your own logic functionality. The logic functionality is used to
provide the local or remote operator with unique true/false state indication. It is also possible
to associate commands with the logic functions, therefore executing actions based on the logic
expressions.
Database
Optional
Custom automation
Digitals Digitals actions
Figure 5: Custom Digitals flow diagram
Based on information contained in the protocol database, Custom Digitals provide two main
functions:
❏ Create additional status data in the database, making the results available to other database-
related tools
❏ Perform basic automation through actions linked to custom digital points.
4.5.2 Digitals Configuration Worksheet

This paragraph describes the different user parameters available in the Custom Digitals
configuration worksheet.
Figure 6: Custom Digitals worksheet window
The tables below describe the fields in the Custom Digitals configuration worksheet.
Custom Logic Tool – Custom Digitals configuration worksheet Rows

Digital points Field name and description 01 - 64
Point 01 to 64.
Custom Digital 01 – 64
Custom Logic Tool – Custom Digitals configuration worksheet Columns

Online indication Field name and description 1st
True/False (digital point status)
This field indicates the logic state (true or false) of the custom logic point. The status is visible
when a valid CLT map is running in the controller and the user is online with the switchgear.
Range: True/False
Default: blank.

User configuration Field name and description 2nd - 7th
Name (customer specified name for the digital point) 2nd
Instead of the generic “Custom Digital xx” name, users may specify a
unique alias that can easily identify the purpose of the relevant logic point.
The alias is visible in the user interface and is reported in the event log when
the point changes status.
Range: Up to 50 ASCII characters.
Default: Custom Digital 01 to Custom Digital 64.
Set Expression (expression to assert the digital point). 3rd
The expression is a logic function comprising a collection of database
points and operands to determine the relationship between the points.
When a Set Expression evaluates True, the digital point is asserted. The
point remains true until one of the following conditions occur:
❏ in the absence of a Reset Expression, the Set Expression evaluates to
false, or
❏ the Reset Expression evaluates to True.
The Set Expression may also be used to trigger a predetermined action that
is configured in the set action field.
Range: True/False.
Default: Blank.
Reset Expression (expression to reset the digital point). 4th
The Reset Expression is optional. It is a logic function comprising a
collection of database points and operands to determine the relationship
between the points. When a Reset Expression evaluates True, the Digital
point is reset to False. The point remains False until the Set Expression
evaluates True.
The Reset Expression may also be used to trigger a predetermined action
that is configured in the Reset Action field.
Range: True/False.
Default: blank.
Note: The Reset Expression is optional.

User Configuration Field name and description 2nd - 7th
Set Action (takes action when the Set Expression is True). 5th
When the Set Expression evaluates true, it can be used to toggle a control
point or to turn a control point on or off. By changing the control point state,
it is possible to trigger a predetermined action.
Range: digital controls, protocol IOEX controls, analogue controls.
Default: blank.
Note: only one action can be assigned per set expression.
Reset Action (takes action when the Reset Expression is True) 6th
When the Reset Expression evaluates true, it can be used to “Toggle” a
control point or to turn the control point “On” or “Off”. By changing the
control point state, it is possible to trigger a predetermined action.
Range: digital controls, protocol IOEX controls, analogue controls.
Default: blank.
Note: only one action can be assigned per reset expression.
Comment (comment text field). 7th
A text field is provided to describe the function of the digital point for
maintenance or editing. The information is only visible in the CLT user
interface.
Range: Up to 127 unicode characters.
Default: blank.
Example 1. Switchgear Status

This example illustrates the use of digital database points and operands such as AND, OR and NOT.
Use Digital 01 to create a logic point to assist an operator during a site visit in verifying that the
switchgear is in the correct status before leaving the installation. For this example the correct
switchgear status is when:
❏ the switchgear is closed
❏ protection group A is active
❏ the Work Tag is removed
❏ the auxiliary supply fail
❏ the battery supply fail.
The protocol database includes status points that can be used to achieve this functionality.
These are:
Database point True when False when

Switchgear Closed Switchgear closed Switchgear not closed
Protection Group A Active Protection Group A is active Protection Group A is not active
Work/Hot Line Tag Work (Hot Line) Tag applied Work (Hot Line) Tag removed
Auxiliary Supply Fail Auxiliary supply fail Auxiliary supply normal
Battery Supply Fail Battery supply is not normal Battery supply is normal
Maintenance Required Maintenance needed Maintenance not required
The green cells highlight the states that will provide the necessary indication. Using Boolean
algebra to satisfy the requirement, the configuration for Custom Digital Point 01 in the Digitals
Worksheet will be:
Name Change Custom Digital 01 to Confirm Switch Status.

Set Expression Switchgear Closed AND Protection Group A Active AND (NOT(Work/Hot Line Tag OR
Auxiliary Supply Fail OR Battery Supply Fail)
Reset Expression The Reset Expression is optional. Confirm Switch Status will become False when the Set
Expression evaluates to False. Alternatively, it is possible to create a reset expression containing
the same or different database points. As an example, it can include an additional check for
possible maintenance required.
NOT (Switchgear Closed AND Protection Group A Active) OR Work/Hot Line Tag OR
Auxiliary Supply Fail OR Battery Supply Fail OR Maintenance Required
Example 2. Low Battery Trip

This example illustrates the use of analogue database points with operands such as ≥ and ≤, and the
use of set/reset actions.
Use Digital 02 to create a battery monitoring function that will trip the switchgear when the battery
voltage falls below a predetermined level of 21.6V. When the battery voltage recovers to above
22.6V, normal operation should be possible.
The protocol database includes an analogue Battery Voltage point that will be used to achieve this
functionality. It also requires an action to trip the switchgear.
Analogue database point Description

Battery voltage Analogue database point
Minimum value is 0, maximum value is 32V,
Resolution is 0.01 and Deadband is 1.
Database control point Description
Trip switchgear and block When this point is asserted, the switchgear will trip. Simultaneously close operations from
any source are blocked. The block is removed by turning the point off.
Note how the above expressions use different voltage levels to create a deadband. It is also
important to note that the reset expression is used to remove the close block. However, it does not
close the switchgear. An operator has to close the switchgear manually.
4.6 Custom Variables

4.6.1 About Custom Variables
Custom Variables is a collection of preset values. The preset values are used as active values in logic
expressions containing analogue database points. It is possible to override the active values via
protocol. This flexibility allows a standard map to be created and loaded to a collection of switchgear
devices. Each device can be calibrated to the different conditions or applications via protocol
without altering the standard map.
Database
Custom
Digitals Digitals
Active Values Custom

Variables Optional
Automation
Actions
Protocol
Tool
Figure 7: Custom Variables flow diagram

The purpose of the Custom Variables is to:
❏ provide a selection of preset values that are available to all logic expressions containing analogue
database points
❏ provide remote access to the variable values in order to adapt the functionality of the custom logic
map to different conditions.
4.6.2 Variables Configuration Worksheet

This paragraph describes the parameters available in the Custom Variables configuration worksheet.
Figure 8: Custom Variables worksheet window
The tables below describe the fields in the Custom Variables worksheet.
Custom Logic Tool – Custom Variables configuration worksheet Rows

Custom Variables Field name and description 01 - 32
Point 01 to 32.
Custom Variable 01 – 32.
Custom Logic Tool – Custom Variables configuration worksheet Columns

Active Value (existing value of the variable)
This field indicates the active value of the variable. The value is visible when a valid CLT map is
running in the controller and the user is online with the switchgear.
Default: 0.
Custom Logic Tool – Custom Variables configuration worksheet Columns
Name (Customer specified name for the custom variable). 2nd
Instead of the generic “Custom Variable xx” point name, users may specify
a unique alias that can easily identify the purpose of the relevant variable.
The alias is visible in the user interface and is reported in the event log with
maximum/minimum value events.
Range: up to 50 ASCII characters.
Default: “Custom Variable 01” to “Custom Variable 32”.
Default Value (specified map value for the point). 3rd
The default value will be the active value used in all logic expressions
referencing the variable, unless the active value is overridden with a new
value.
Default: 0.
Override Value (tick box). 4th
Selecting the tick box allows modification of the variable’s active value via
SCADA. When the option is not selected the default value will always be
used in logic expressions.
Range: selected/not selected.
Default: not selected.
Comment (comment text field). 5th
interface.
Range: up to 127 unicode characters.
Default: blank.
Scale (practical scale value). 6th
The scale is determined by WSOS when the Custom Variable is used in
conjunction with an analogue database point. WSOS RPN engine is an
integer only, thus will round up the decimal results of expressions.
Default: 1.
Example 3. Load Current Monitor Using Custom Variables

This example illustrates the use of custom variables in logic expressions containing analogue
data points.
For the purposes of this example we will set up Custom Digital point 03 to monitor the phase
currents. If the phase currents exceed 400A an overload alarm must be activated. The alarm must
stay active until the phase current reduces to less than 390A.
Analogue Database point Description

A-Phase Current Line current flowing through each phase.
B-Phase Current Minimum value is 0, maximum value is 16,000 Amps,
C-Phase Current Resolution is 0.1 and Deadband is 10.
Custom Data point Description
Custom Variable 01 Custom Variable from the Custom Data collection of analogue values. This point is
configured as over load current with a value of 400A.
Custom Variable 02 Custom Variable from the Custom Data collection of analogue values. This point is
configured as normal load current with a value of 390A.
In the “Digitals” worksheet configure point 03 to the following.
Name Change “Custom Logic 03” to “Overload”.

Set Expression ( A-Phase Current > Custom Variable 01 ) OR ( B-Phase Current > Custom Variable
01 ) OR ( C-Phase Current > Custom Variable 01 )
Reset Expression ( A-Phase Current < Custom Variable 02 ) AND ( B-Phase Current < Custom
Variable 02 ) AND ( C-Phase Current < Custom Variable 02 )

4.7 Custom Counters
4.7.1 About Custom Counters
Custom Counters determine the number of times a particular logic status has occurred. The counter
values can change in either direction (count up or down), under the control of separate increment/
decrement logic expressions. The active values of the counters are available via the protocol
database for remote display. Active values can also be incorporated in logic expressions to drive
logic functions, indication and even automation actions.
Database
Optional
Custom Automation
Custom
Active values Variables
Custom
Counters Counters
Figure 9: Custom Counters flow diagram
The custom counters provide two main functions:

❏ Count (up or down) logic transitions with the counter value available via protocol for remote
indication
❏ Counter values are used as analogue database points in logic expressions.
4.7.2 Counters Configuration Worksheet

This paragraph describes the user parameters available in the Custom Counters
configuration worksheet.
Figure 10: Counter configuration worksheet window
The tables below describe the fields in the Custom Counters worksheet.
Custom Logic Tool – Custom Counters configuration worksheet Rows

Custom Counters Field name and description 01 - 32
Point 01 to 32.
Custom Counters 01 – 32.
Custom Logic Tool – Custom Counters configuration worksheet Columns

Active Value (existing value of the counter)
This field indicates the active value of the counter. The value is visible when a valid CLT map is
Default: 0.
Name (customer specified name for the custom counter) 2nd
Instead of the generic “Custom Counter xx” point name, users may specify
a unique alias that can easily identify the purpose of the relevant counter.
The alias is visible in the user interface and is reported in the event log with
Default: “Custom Counter 01” to “Custom Counter 32”.
Minimum Value (specified minimum value for the counter) 3rd
The minimum value specifies the lowest possible value of the counter.
When the counter reaches the minimum value the count will not decrease
further, even if the decrement expression evaluates True. Unless, the global
“Counter Rollover On” setting in the switchgear Feature Selection window
is selected. Then the value will go from the Minimum Value to the Maximum
Value when the Decrement Expression evaluates True.
Range: 0 to 2,000,000,000.
Default: 0.
Maximum Value (specified maximum value for the counter) 4th
The maximum value specifies the highest possible value of the counter.
When the counter reaches the maximum value, the count will not increase
further even if the increment expression evaluates True. Unless, the global
“Counter Rollover On” setting in the switchgear Feature Selection window
is selected. Then the value will go from the maximum value to the minimum
value when the Increment Expression evaluates True.
Range: 0 to 2,000,000,000.
Default: 0.
Default Value (specified default value for the counter) 5th
At initialisation of the map, the active value of the counter will be the default
value. The active value of the counter also changes to the Default Value
when the default expression evaluates True.
Range: 0 to 2,000,000,000.
Default: 0.
Reset Value (specified reset value for the counter) 6th
The active value of the counter changes to the Reset Value when the Reset
Expression evaluates True.
Range: 0 to 2,000,000,000.
Default: 0.
Default Expression (changes the counter value to default) 7th
When a Default Expression evaluates True, the counter value is set to the
Default Value. The value remains unchanged until the Default Expression
becomes False.
Range: True/False.
Default: blank.
Reset Expression (changes the counter value to reset) 8th
When a Reset Expression evaluates True, the counter value is set to the
Reset Value. The value remains unchanged until the Reset Expression
becomes False.
Range: True/False.
Default: blank.

Increment Expression (increases the counter value by one) 9th
When the Increment Expression evaluates True, the counter value is
increased by one.
Range: True/False.
Default: blank.
Decrement Expression (decreases the counter value by one) 10th
When the Decrement Expression evaluates True, the counter value is
decreased by one.
Range: True/False.
Default: blank.
Comment (comment text field) 11th
interface.
Default: blank.
4.7.3 Counter Behaviour

Using a timing diagram, this paragraph illustrates the behaviour of counters.
Increment 1
Parameters
0
Default Value = 3
Decrement 1
0 Reset Value = 0
Active Value shown in Blue.
Counter value 7
6 Expressions shown in Red:
5
4 ❏ Increment expression
3
2 ❏ Decrement expression
1
0 ❏ Default expression
❏ Reset expression
Default 1
0
Reset 1
0
Step-by-step description of the counter behaviour: Value

1. Initially the counter starts at the Default Value. 3
2. The counter value increases by one when the Increment Expression evaluates True. 4–5
3. The counter value decreases by one when the Decrement Expression evaluates True. 4
4. As per step 2. 5
5. As per step 3. 4
6. The Default Expression evaluates True and sets the counter value to the Default Value. 3
7. The Reset Expression evaluates True and sets the counter value to the Reset Value, even though the Default 0
Expression is still true. Reset has a higher priority.
8. The Reset Expression evaluate False, but the Default Expression is still True. Therefore the value of the counter 3
is set to the Default Value.
4.7.4 Counter Maximum Values and Rollover
Using a timing diagram, this paragraph illustrates the behaviour of counters when a maximum value
is specified. It also shows the difference in behaviour when Counter Rollover is turned on/off. This
illustration uses the same Increment/Decrement Expressions as 4.7.3. However there are no Reset
and Default Expressions.
From the below illustration, the importance of the maximum, minimum values and rollover settings
become clear.
Increment
1
Parameters
0
Decrement Maximum Value = 4
1
0 Default Value = 3
Reset Value = 0
Counter value 7
– without 6 Active Value shown in Blue.
5
Maximum value 4 Expressions shown in Red:
specified 3
2 ❏ Increment expression
1
0 ❏ Decrement expression
Counter value 7
– with
6
5
Maximum value 4
specified, and 3
rollover OFF. 2
1
0
Counter value 7
– with
6
5
Maximum value 4
specified, and 3
rollover ON. 2
1
0
Counter without a maximum value: Value
2. The counter value increases by one when the Increment Expression evaluates True. 4–5
4. As per step 2. 5
5. As per step 3. 4–3
6. As per step 2. 4
Counter with a maximum value, Rollover OFF: Value
8. The counter value increases by one when the Increment Expression evaluates True. This is the maximum 4
value. The value remains 4 even when the Increment Expression evaluates True.
10. As per step 8. 4
11. As per step 3. 3–2
12. The counter value increases by one when the Increment Expression evaluates True. 3
Counter with a maximum value, Rollover ON: Value
15. The counter value rolls over to the minimum value when the Increment Expression evaluates True. 0
16. The counter value rolls over to the maximum value when the Decrement Expression evaluates True 4

4.8 Custom Timers
4.8.1 About Custom Timers
Custom Timers are available to filter or delay transitions in logic expressions. Each timer has a preset
duration, and starts running when the Start/Stop Expression evaluates true. When the timer expires
a logic output is asserted. The output remains asserted until the Reset Expression evaluates True.
There are three different types of timers to choose from. Each responds differently to the start/stop
logic expression. Their behaviour can be summarised as follows:
Type Characteristics
De-bounce Timer If the Start/Stop Expression evaluates True, the timer starts running. However, if the Start/Stop
Expression becomes False before the timer expires, the timer resets to the preset value. Therefore,
the timer output is only asserted if the Start/Stop Expression remains in a True state for a period
greater than the preset value. The output is asserted when the timer expires.
Cumulative Timer If the Start/Stop Expression evaluates True, the timer starts running. The timer is paused if the
Start/Stop Expression becomes False before the timer has expired and continues when the
expression becomes True again. Therefore, the timer output is asserted when the combined
duration of True state equals the preset value.
Latching Timer If the Start/Stop Expression becomes True, regardless of the duration, the timer output is asserted
a time equalling the preset value after the initial transition to the True state.
The timing diagram below compares the different types of timers using the same Start/Stop
expression and time scale.
Start/Stop 1
0
De-bounce Timer
Output 1
0
Remaining time 100%
reset 0%
Cumulative Timer
1
Output 0
100%
Remaining time pause 0%
Latching Timer
1
Output 0
100%
Remaining time 0%
1
Reset
0
Figure 11: Timer comparison
The custom timers provide three main functions:

❏ Filter transitions in logic expressions to act only on those exceeding a preset duration.
❏ Measure the cumulative duration of a logic state.
❏ Delay the transition in a logic expression by a preset time.
Custom timers are used in conjunction with the other CLT functions.
Database
Optional
Custom Automation
Custom
Active values Variables
Custom
Counters Counters
Custom
Timers Timers
Figure 12: Custom timers flow diagram
4.8.2 Timers Configuration Worksheet

This paragraph describes the user parameters available in the Custom Timers configuration worksheet.
Figure 13: Timer configuration worksheet window
The tables below describe the fields in the Custom Timers Worksheet.
Custom Logic Tool – Custom Timers configuration worksheet Rows

Custom Timers Field name and description 01 - 32
Point 01 to 32.
Custom Timers 01 – 32
Custom Logic Tool – Custom Timers configuration worksheet Columns

Online indication Field name and description 1st - 2nd
Timer Output (logic output) 1st
This field indicates the logic state of the timer – True when the timer has
expired and False otherwise. The value is visible when a valid CLT map is
Range: True/False.
Default: blank.
Elapsed Value (existing value of the timer) 2nd
This field indicates the elapsed value of the timer. The value is visible when
a valid CLT map is running in the controller and the user is online with the
switchgear.
Default: 0.

User configuration Field name and description 3rd - 9th
Name (customer specified name for the custom timer) 3rd
Instead of the generic “Custom Timer xx” point name, users may specify a
unique alias that can easily identify the purpose of the relevant timer. The
alias is visible in the user interface and is reported in the event log with
Default: “Custom Timer 01” to “Custom Timer 32”.

User configuration Field name and description 3rd - 9th
Name (customer specified name for the custom timer) 4th
Instead of the generic “Custom Timer xx” point name, users may specify a
unique alias that can easily identify the purpose of the relevant timer. The
alias is visible in the user interface and is reported in the event log with
Default: Custom Timer 01 to Custom Timer 32.
Timer Resolution (select the resolution for the timer) 5th
Choose an appropriate resolution from the list provided.
Range: 1 second, 1 minute, 1 hour, 1 day.
Default: 1 second.
Timer Duration (specified duration for the timer) 6th
The duration of the timer determines the timing period before the output is
asserted. (See 4.8.1).
Range: 2,000,000,000.
Default: 0.
Reset Expression (resets the timer value and logic output) 7th
When a Reset Expression evaluates True, the timer value is reset and the
logic output is set to False.
Range: True/False.
Default: blank.
Start/Stop Expression (expression monitored by the timer) 8th
Range: True/False.
Default: blank.
Comment (comment text field) 9th
interface.
Default: blank
Example 4. Duration of Overload

This example illustrates the use of timers in logic expressions.
In this example we will create an alarm that will alert operators when the feeder has been overloaded
for a period exceeding 4 hours. We will use the overload feature created in Example 3 and add a
timer to it.
Custom Data point Description

Custom Digital 03 This is a custom logic point created in a previous example. It is asserted when the load current
in any phase exceeds the level set in Custom Variable 01 (400A). The point resets when the load
current on all phases are less than Custom Variable 02 (390A). These values can be changed via
protocol.
In the “Timers” worksheet, configure point 01 to the following.
Name Change “Custom Timer 01” to “Overload Duration”.

Type De-bounce timer
Resolution 1 hour
Duration 4
Start/Stop Expression Custom Digital 03
Custom Timer will be asserted when the overload current exceeds 4 hours.
5.0 Logic Expressions
5.1 Logic Expression
Builder Interface
5.1.1 Introduction
?
The Logic Expression Builder is used to add points and operands to the
expression field in the Custom Logic Tool worksheet interface. It is used to
create two different types of logic expressions:
Point Value
controls ❏ Logic expressions.
Operand ❏ Action expressions.
selection
Formatting The builder is accessed from the Custom Logic Tool worksheets by
controls selecting the “fx“ symbol. Figure 14 shows the typical expression
builder window comprising five main components. These components
are discussed in subsequent paragraphs. Availability of the first three
components located on top depends on the type of logic expression being
created. The table below summarises the availability:
Data Points
Logic expression Action expression
Find (search)
Browse for points 1. Operand selection All 17 operands are None are available
Select points available
View point 2. Point value controls None are available ON, OFF, and
information TOGGLE are available
3. Formatting controls Indent, New line, and Delete all text is
Delete all text are available
available
Filter Data Points 4. The fourth component, Data Points, allows the user to search or browse
to Data Points, select the Data Points for inclusion in the expression and
view a description of the Data Point.
5. The fifth component, Filter Data Points, limits the availability of Data
Figure 14: Logic expression builder window Points to only those supported by specific firmware versions.
5.1.2 Operands Toolbox

The following operands are available to describe the relationship
of database points. This toolbox is only visible when creating logic
expressions. The use and behaviour of the different operands are
described in paragraph 5.2.
To avoid ambiguity, parentheses are used to group

( ) expressions together. These expressions are
resolved first.
AND Logic – AND OR Logic – OR
NOT Logic – NOT + Mathematical – PLUS
Mathematical – MINUS x Mathematical –

—
MULTIPLY
. Mathematical – DIVIDE Analogue – EQUAL TO
Figure 15: Operands toolbox —
. =
Analogue – NOT Logic – Exclusive OR

≠ XOR
EQUAL TO
Analogue – LESS THAN Analogue – LESS THAN
< ≤
or EQUAL TO
Analogue – GREATER Analogue – GREATER
> ≥
THAN THAN or EQUAL TO
Analogue – STORE NUMBER is used to
Store Number add numerical values to the logic
expressions.

5.1.3 Point Values Toolbox
Point Values are used to control the action of digital control points. This
toolbox is only visible when creating action expressions.
ON Turns the control point ON.

OFF Turns the control point OFF.
Figure 16: Point values toolbox
TOGGLE Toggles the state of the control point. If it was in the
ON state the point is turned off and vice versa.
5.1.4 Formatting Toolbox

The formatting tools are used to alter the appearance of the expressions in
the expression window.
INDENT – indents the current line in the expression window. This

tool is not available when actions are being created.
Figure 17: Formatting toolbox NEW LINE – inserts a new line in the expression window. This
tool is not available when actions are being created.
DELETE ALL TEXT – deletes the contents of the expression
window.
5.1.5 Data Points Window

The data points available in the specified firmware version are displayed
in the Data Points window. It is important to know that there are two main
groups of data points available:
❏ Status Data Points (used as inputs in logic expressions).
❏ Control Data Points (used to cause specific actions).
There are two different types of status data points:
❏ Logic (True/False).
❏ Analogue.
All the control data points are Logic (On/Off).
Logic points have a “ ” symbol to identify the digital nature. A group of
logic points are identified by the “ ” symbol.
Analogue points have a “ ” symbol to identify the analogue nature. A
group of analogue points are identified by the “ ” symbol.
The Find feature is used to search the text names of the database points
Figure 18: Data Points window and it will only display those points containing the text typed into the Find
field.
All database points are contained in a three-tier structure. The “+” symbol
is used to browse to the different tiers. Simply click on the “+” to display
the contents of the group.
5.1.6 Filter Data Points

The Version Filter reduces the set of database points to only those
available in the specified range of firmware.
5.2 Operands
Seventeen operands are provided to describe the relationship between
database points in logic expressions. This paragraph describes the
Figure 19: Filter Data Points
function of the different operands and illustrates its use with logic and
analogue data points. There are three groups of operand:
❏ Logic Operands – used with logic database points.
❏ Analogue Operands – used with analogue database points.
❏ Mathematical Operands – used to perform calculations on set values.
5.2.1 Logic Operands
Logic Operands are used with logic database points. AND, OR, NOT and XOR are logic operands
used to implement Boolean functions. It performs a logic operation on one or more logic inputs and
produces a single logic output. The table below summarises the function of the logic operands by
showing the output of the different operands for the same inputs. “A” and “B” are digital
database points.
Database points Result of expression

A B NOT A NOT B A AND B A OR B A XOR B
0 0 1 1 0 0 0
0 1 1 0 0 1 1
1 0 0 1 0 1 1
1 1 0 0 1 1 0
Operand Description
NOT When the database point is True, the result is False.
AND If all the database points are True, the result is True.
OR If one or more of the database points are True, the result is True.
XOR The result is True if the database points are not equal.
It is possible to simultaneously use different combinations of logic operands in one expression.

Example:
❏ A AND B AND C
❏ A OR B OR C
❏ (A AND B) OR C
❏ NOT (A AND B AND C)
❏ (A XOR B) OR C
5.2.2 Analogue Operands

The analogue operands (=, ≠, <, ≤, ≥, > and Store Number) are used
16 with analogue database points. To illustrate the function and difference
15 between the operands, Figure 20 shows the behaviour of the different
14
13 operands when applied to the same counter database point. The counter
12 counts up over a period of time and, when used with each of the operands
11
Set Value 10 and a specific set value, will deliver the results as shown.
9
8 Store Number is used to add a fixed set value in the expression.
7
6 For example:
5
4 To create an expression where a counter point such as Operations
3
2 Counter is greater than 1000, the following steps are required:
1
0 1. Find the Operations counter database point in the expression builder.
2. Add the point by double clicking on the point name.
3. Select high alarm as the analogue logging option.
Figure 20: Analogue operands and a counter database point 4. Select the operand “>” to add it to the expression.
5. Select the operand Store Number and enter the number 1000 when
prompted.
The expression will look something like this:
Operations Counter > 1000

5.2.3 Mathematical Operands
The mathematical operands (+, x, −, ÷) are used to perform calculations on analogue setting values.
For example it is possible to change the Reset Expression used in Example 3. Instead of having the
reset value as (Custom Variable 02) it is possible to calculate the Reset Value from the Set Value
(Custom Variable 01):
Example 3 with a fixed reference for the Reset Value: Calculate the Reset Value as 10A less than the Set Value
(400A – 10A = 390A):
A-Phase Current < Custom Variable 02 AND A-Phase Current < (Custom Variable 01 - 10) AND
B-Phase Current < Custom Variable 02 AND B-Phase Current < (Custom Variable 01 - 10) AND
C-Phase Current < Custom Variable 02 C-Phase Current < (Custom Variable 01 - 10)
Or it is possible to calculate the Reset Value as a percentage
of the Set Value (400A x 0.9 = 360A):
A-Phase Current < (Custom Variable 01 x 0.9) AND
B-Phase Current < (Custom Variable 01 x 0.9) AND
C-Phase Current < (Custom Variable 01 x 0.9)
5.3 Database Points

The protocol database is used to convey information such as status indication (ON/OFF) and
analogue information to remote or local users. It is also used to control elements by allowing
remote operators to turn elements on or off. These three types of database points are made
available to end users to customise the behaviour of their switchgear products. The Logic
Expression Builder Interface is used to access the database points. Paragraph 5.1.5 introduces
the Data Points window. There are too many database points to list them all, and the list changes
frequently when new functionality is developed. Therefore this paragraph rather provides an
overview of the different types of database points.
5.3.1 Digital Database Points

Logic points are used as is in logic expressions. For example, an expression containing Protection
ON/OFF AND Auto Reclose will be True when both protection and auto reclose are on.
The digital data points can be broken up in four groups with sub-groups:
Digital Data
Switchgear and Controller State Flags
( Includes points for Trip/Close status, maintenance items, Live/Dead indication, alarms)
Operator/Protection Flags for ACR
( Includes points for protection functions on/off indication, protection group active)
Protection trip flags ACR
( Includes points of fault elements during reclose trip sequence)
Distributed Automation Flags
( Status indication of Loop Automation and Auto-Changeover)
Pickup Flags
( Fault pickup information)
IOEX Inputs
( Input status of the IOEX (Input Output Expander accessory device))
Unit Protection
( Unit Protection status)
Protocol IOEX Control Status
( Virtual RTU points)
LBS Data
Operator/Detection Flags for LBS
( Includes points for detection functions ON/OFF indication, detection group active)
Detection Flags LBS
( Includes points of fault detection during fault conditions)
Protocol-Specific Data
Protocol-Specific Digital status points.
( Protocol alarms)
Custom Data
Custom Digitals
( Custom Digital database points)
5.3.2 Analogue Database Points

Before these analogue points can be used in logic expressions it is necessary to convert the points
to a logic entity. This is done by means of the analogue operands. For example, it is not possible
to use a phase current analogue value as is in a logic expression. But when the phase current is
greater than a specific value can be used. By adding an analogue operand and a preset value to an
analogue point, the phase current is a logic entity (True or False).
Analogue Data
Line Currents
( A, B, C phase currents, fault levels, demand information)
Voltage Measurement
( A, B, C phase to phase, phase to earth)
System Power
( Total, A, B, C real, apparent, reactive power)
SF6 Gas Pressure
( Status and pressure in different units)
Protection State
( Cold load, NPS, Loss of phase status)
Protection Sequence and Trip Data
( A, B, C, Earth, NPS for each trip)
Switchgear Details
( Serial number, contact live remaining, operations counter)
Controller Data
( Battery, Auxiliary voltage, serial numbers, cover versions)
Distributed Automation
( Loop Automation, Auto-Changeover status)
Daily Data
( Average current, demand, power factor)
Frequency Measurement
( Frequency)
Unit Protection-Read
( Unit phase current, trip number)
Unit Protection-Derived
( Maximum phase and earth currents per trip)
Sequence Components
( ZPS, PPS, NPS Currents and voltages)
LBS Analogue Data
Detection State
( Cold Load, Group, NPS)
Fault Detection Data
( Active group, counters, fault leves)
Protocol-Specific Data
Protocol-Specific Analog status points.
( Address data)
Custom Data
Custom Variables
( Custom Variables 01 - 32)
Custom Timers
( Custom Timers 01 - 32)

5.3.3 Control Database Points
Control Database Points are logic points used in action expressions. For example, an expression
containing an action is ON Switch Control Remote. This will put the controller in a Remote Mode.
To return the controller to Local Mode the action is OFF Switch Control Remote.
Digital Controls – there are no sub-groups

( Operator ON/OFF control points such as Work Tag, Reset Flags, Protection, Local/Remote,
Active protection group.
( Protection function ON/OFF points such as Earth, SEF, Auto Reclose, High Current Lockout,
Loss of Phase, Sequence
Control, Live Load Blocking, APGS, Frequency Protection, Dead Lockout.
( Automation ON/OFF control points such as Loop Automation and Auto-Changeover.
( I/O control points Protocol IOEX Control 1 – 16
Protocol IOEX Controls – there are no sub-groups
( Protocol IOEX Control 1 - 16
5.3 Creating Logic Expressions

Preceding chapters and paragraphs describe the tools and components of logic expressions in
great detail.
Figure 22: Building logic expressions, shows the different elements that are used to create logic and
action expressions.
5.4.1 Logic Data Points

With the following step-by-step instructions it is possible to create expressions containing logic data
points:
1. Find the required database point by searching or browsing the database tree.
2. Click once on the database point’s name and hover over the name. This will open a description
text box. Peruse the detail and determine if the point is suitable and if the True/False states are
correct for the purpose of the expression.
3. If the True/False state needs to be inverted to suit the purpose of the expression, click on the NOT
operand. This inserts a NOT in the expression field.
4. Now insert the database point by double clicking on the database point’s name. The database
point is added to the expression – NOT Database point name.
5. Add the next operand such as AND, OR, XOR by clicking on the required operand in the
Expression Builder window.
6. Find the next database point and add by double clicking.
It may be necessary to use parentheses to prioritise some operations in the expression.
5.4.2 Analogue Data Points
Using analogue data points in expressions are very similar to logic points.
The only difference is that in addition to the point name, it is necessary to
select a logging option and specify an analogue operand and numerical
value.
1. Find and add the analogue database point.
2. Select the logging option. This is only available for set expressions. The
options are: No Logging, High or Low Alarm options.
3. Specify the analogue operand ( =, ≠, <, ≤, ≥, >).
Figure 21: Analogue logging option
4. Add the numerical value either using Store Number or by using a
custom variable value.
5. If required add mathematical operand and value using Store Number.
6. Add the logic operand.
7. Continue with the next analogue or digital database points.
It will be necessary to use parentheses to prioritise some operations in
the expression.
5.4.3 Optimising the Logic Expressions

The complexity of the CLT map may affect the response time of the different expressions. It is,
therefore, necessary to optimise the logic functions as much as possible during development of a
feature. There are several methods, such as Karnaugh maps (K-maps) that can be helpful during
development.
In addition, keep in mind that the priority of the CLT map execution is much lower than the protection
functionality in the controllers. Therefore, the response time of the logic expressions may vary
depending on the other activities performed at that point in time.
5.4.4 Latched and Unlatched Database Points

The protocol database contains a mixture of latched and unlatched points. With latched database
points the point will remain asserted even when the condition is no longer True. For example,
Protection Pickup is not latched, but Phase A Pickup Latched is latched. It is possible to identify
latched points through the name or description. While creating logic expressions it is important
to consider which points are latched as this may affect the reset expression or could lead to an
undetermined state, when both the set and reset expressions are true at the same time.

Building expressions: Building actions:
Find the data point by browsing or Add the point value control (ON, OFF,
using “Find”. A window appears TOGGLE) to the action field. Find the
with information about the selected digital control point by browsing or
data point. Double-click to add the using “Find”. A window appears with
point to the expression field. Select more information about the control
the operand by clicking the button. point. Double-click to add the control
Repeat until the Set and Reset point to the action field. Only one action
expressions are complete. is allowed per expression. Complete for
the Set and Reset actions.
Name:
Enter the point alias.
Comment:
Use the comment field to
capture a description or
support information that
may be helpful during map
development or maintenance.
Custom logic tool operator interface – Custom Digitals

This diagram illustrates step-for-step the process required to define all the parameters describing a
Custom Digital point.
Step Field name Description

A Name Provide an alias describing the function of the digital point,
B+C Set/Reset Expressions Click the “fx” symbol to activate the Expression builder. Data points are shown in Blue and
operands in Black.
D+E Set/Reset Actions Click the “fx” symbol to activate the Expression builder. The Data point is shown in Blue and
point value control in Black.
F Comment Provide a sensible comment,
G APPLY Click the “Apply” button to apply the changes to the CLT map.
Figure 22: Building logic expressions
5.4.5 Digital Set and Reset Expressions
A variety of logic expressions are available in the CLT:
❏ Digitals Worksheet – Set and Reset Expressions.
❏ Counters Worksheet – Default, Reset, Increment, Decrement Expressions
❏ Timers Worksheet – Reset, Start/Stop Expressions.
In the Counters and Timers worksheets the expressions perform specific functions associated
with the counter/timer. When the conditions in these expressions evaluate True the functions are
performed and when the conditions are not met the expression evaluates False, ready for the next
time when the conditions are met.
In the Digitals worksheet, however, the expressions are associated with database points instead of
performing a specific function. In the absence of a reset expression operation is straightforward –
when the conditions of the Set Expression are met the database point is True, when the conditions
are not met the database point is False. However to provide additional flexibility it is possible to
specify a different Reset Expression. When a Reset Expression is included, the point will be asserted
when the conditions in the Set Expression are met, but the database point will remain True (even if
the conditions are no longer met) until the conditions in the reset expression are met.
For example: Digital point xx : Set expression = A AND B AND C
In the absence of a reset expression the value of Digital Point 01 is:
Digital point xx = True when A and B and C are True.
Digital point xx = False when A or B or C are False.
In the presence of a Reset Expression = D OR E OR F the value of Digital Point xx is:
Digital point xx = True when A and B and C are True. And it will remain True until the reset
expression evaluates True.
Digital point xx = False when D or E or F are True.
Note: When both the set and reset expression evaluate True at the same time, the state will remain
unchanged and an event
will be recorded accordingly for example Custom Digital 01 state undetermined.
It is also possible to use analogue points in logic expressions. Without a Reset Expression the
analogue point will behave as expected, but without a deadband. A deadband is a margin around
the set value that is used to avoid nuisance indication caused by noise or analogue values remaining
close to the set value. A separate reset expression is used to create the deadband. The following
example illustrates the use of a deadband.
Digital point yy : Set expression = A Phase Current > 400
The True/False state of Digital point yy is shown in red (when there is no reset expression).
If the Reset Expression is defined = A Phase Current < 380, the True/False state of Digital point yy
is shown in black.
Amp
420 A
400 A
380 A
OFF
OFF
ON
time
ton tmax toff
Digital point yy without reset expression
Digital point yy with reset expression
Figure 23: Analogue reset expression

6.0 Loading CLT Maps to the
Controller
Make the Custom Logic Tool available in the switchgear file. The Custom
Logic Tool Available field is found under the General section of the Feature
Selection window in WSOS.
When CLT is available in the switchgear a new option is added to the

switchgear explorer to access the Custom Logic Tool.
Selecting the Custom Logic Tool option opens the window below.
Click on the CLT Description field to select the map for the switchgear.
The adjacent window allows the user to select the Custom Logic Tool Map
from a list of “*.clt” files that exists on the personal computer. Select the
file and click OK.
This attaches the CLT map to the switchgear file. Save the switchgear
file and go online with the switchgear. In the Options Menu select “Write
Switchgear Settings to Switchgear”, select the CLT Mapping option and
follow the on-screen instructions to load the map to the controller.
The operator interface includes a field to display the name of the map in
use. For the setVUE operator interface a “Custom Logic” page displays
the map name being used. In the flexVUE operator interface – Engineering
menu > Configuration menu > Custom Logic menu the Custom Logic Map
displays map name of the file being used.
Both these pages are not visible when CLT feature is disabled from WSOS.
7.0 Integrating Custom Logic Points
CLT provides a variety of Operands to describe the relationship between the selected database
points in a Logic Expression. The results of the Logic Expressions are available via the Protocol
Database to the CPMT, OCP and IOEX tools, significantly enhancing the status reporting via
communications protocol, operator interface and input/output devices.
Figure 24 below demonstrates the relationship between the different customisation tools. Note how
all the maps are created separately based on the data contained in the protocol database. Each tool
has its own operator guide. This guide focuses on the Custom Logic Tool (CLT).
Note: This document often refers to a map for the different tools. For example CPMT map, OCP
map, IOEX map, CLT map. In this context “map” refers to the file containing the Logic
Expressions, input and output characteristics and relations.
CPMT Tool CPMT

(Protocol management) Map
Protocol OCP Tool (flexVUE

database OCP
Operator interface) Map
(331 points)
& IOEX Tool IOEX

(Input/Output) Map
Custom
Logic points
CLT Tool Logic
(Custom logic) Map
Computer with WSOS
Logic
Reference material: IOEX IOEX
331 points Device
The following manuals are available to assist in the
Expressions &
operation of the other configuration tools available in
Actions
WSOS. Copies are located in: OCP flexVUE
331 points Interface
“C:\Program Files\WSOS\”
CPMT manual WSOS01-DOC-102 CPMT Protocol
331 points Client
IOEX manual N00-685
Protocol database ADVC-PTCL-331.html
Figure 24: Custom Logic to communicate, control and indicate ADVC Controller

8.0 Event Log Entries
The custom digital points are logged in the event log when the state of the point changes. The
source for these events is “CLT” for Custom Logic Tool. The event log entry is of the format:
Timestamp Logic point name ON/OFF
Example: Timestamp Custom logic 01 ON
When the user enables logging of the maximum/minimum values in Logic Expressions containing
analogue database points the event log entries are:
Example: Timestamp1 High Power Alarm ON
Timestamp2 High Power Alarm Max Value
Timestamp2 At time Max time
Timestamp2 High Power Alarm OFF
In the above example “High Power Alarm” is the alias set by the user and ON when the point is
asserted. Timestamp1 is when the alarm was turned ON. Timestamp2 is the time when the alarm
was turned off. At this timestamp three events are recorded. The first reports the maximum value,
the second the time at which this maximum was recorded and the third reports that the logic point
was turned off. Max Value is the maximum value.
When an action is linked to a virtual point, the event log will show the virtual point entry as described
above plus those events associated with the action. For example if the “High Power Alarm” virtual
point above had associated with it the action to change the active protection to Protection Group C,
the event log entries in WSOS would look something like this:
“Timestamp CLT High Power Alarm ON”
“Timestamp CLT Protection Group (C) Requested”
“Timestamp Protection Group C Active”
The source is shown in the event log when it is viewed on the flexVUE or setVUE operator interfaces.
The event log can be filtered to only display CLT related events.
9.0 Practical Examples
9.1 Analogue Alarms
The analogue alarms feature monitors a selection of analogue database points and alerts the remote
user when any of the parameters are outside the predetermined range. This map is designed for a
controller using an unsigned power setting. If signed power is used the reset expressions for power
alarms will have to be modified to allow for the negative values.
Parameter Value
Filename C:\Documents and Settings\All Users\Application Data\WSOS Switchgear Data\ Custom Logic Tool\
Analog Alarms.clt
Product All Switchgear
Version Version A44-42.0
Custom Logic Tool Digital
Row 1
Name High Phase Current Alarm
Set Expression ((A-Phase Current ≥ Custom Variable 01) OR
(B-Phase Current ≥ Custom Variable 01) OR
(C-Phase Current ≥ Custom Variable 01))
Reset ((A-Phase Current ≤ (Custom Variable 02 + (Custom Variable 01 - Custom Variable 02) × 0.9)) AND
Expression (B-Phase Current ≤ (Custom Variable 02 + (Custom Variable 01 - Custom Variable 02) × 0.9)) AND
(C-Phase Current ≤ (Custom Variable 02 + (Custom Variable 01 - Custom Variable 02) × 0.9)))
Comment High Phase Current Alarm
Custom Logic A-Phase Current High Alarm 0.1 amp
Tool Variable B-Phase Current High Alarm 0.1 amp
Logging C-Phase Current High Alarm 0.1 amp
Row 2
Name Low Phase Current Alarm
Set Expression ((A-Phase Current ≤ Custom Variable 02) OR
(B-Phase Current ≤ Custom Variable 02) OR
(C-Phase Current ≤ Custom Variable 02))
Reset ((A-Phase Current ≥ (Custom Variable 02 + (Custom Variable 01 - Custom Variable 02) × 0.1)) AND
Expression (B-Phase Current ≥ (Custom Variable 02 + (Custom Variable 01 - Custom Variable 02) × 0.1)) AND
(C-Phase Current ≥ (Custom Variable 02 + (Custom Variable 01 - Custom Variable 02) × 0.1)))
Comment Low Phase Current Alarm
Custom Logic A-Phase Current Low Alarm 0.1 amp
Tool Variable B-Phase Current Low Alarm 0.1 amp
Logging C-Phase Current Low Alarm 0.1 amp
Row 3
Name High Phase to Phase Voltage Alarm
Set Expression ((ABi Phase to Phase ≥ Custom Variable 03) OR
(BCi Phase to Phase ≥ Custom Variable 03) OR
(CAi Phase to Phase ≥ Custom Variable 03) OR
(ABx Phase to Phase ≥ Custom Variable 03) OR
(BCx Phase to Phase ≥ Custom Variable 03) OR
(CAx Phase to Phase ≥ Custom Variable 03))
Reset ((ABi Phase to Phase ≤ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.9)) AND
Expression (BCi Phase to Phase ≤ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.9)) AND
(CAi Phase to Phase ≤ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.9)) AND
(ABx Phase to Phase ≤ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.9)) AND
(BCx Phase to Phase ≤ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.9)) AND
(CAx Phase to Phase ≤ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.9)))
Comment
Custom Logic ABi Phase to Phase High Alarm 1 volt
Tool Variable BCi Phase to Phase High Alarm 1 volt
Logging CAi Phase to Phase High Alarm 1 volt
ABx Phase to Phase High Alarm 1 volt
BCx Phase to Phase High Alarm 1 volt
CAx Phase to Phase High Alarm 1 volt

Parameter Value
Row 4
Name Low Phase to Phase Voltage Alarm
Set ((ABi Phase to Phase ≤ Custom Variable 04) OR
Expression (BCi Phase to Phase ≤ Custom Variable 04) OR
(CAi Phase to Phase ≤ Custom Variable 04) OR
(ABx Phase to Phase ≤ Custom Variable 04) OR
(BCx Phase to Phase ≤ Custom Variable 04) OR
(CAx Phase to Phase ≤ Custom Variable 04))
Reset ((ABi Phase to Phase ≥ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.1)) AND
Expression (BCi Phase to Phase ≥ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.1)) AND
(CAi Phase to Phase ≥ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.1)) AND
(ABx Phase to Phase ≥ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.1)) AND
(BCx Phase to Phase ≥ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.1)) AND
(CAx Phase to Phase ≥ (Custom Variable 04 + (Custom Variable 03 - Custom Variable 04) × 0.1)))
Comment
Custom ABi Phase to Phase Low Alarm 1 volt
Logic Tool BCi Phase to Phase Low Alarm 1 volt
Variable CAi Phase to Phase Low Alarm 1 volt
Logging ABx Phase to Phase Low Alarm 1 volt
BCx Phase to Phase Low Alarm 1 volt
CAx Phase to Phase Low Alarm 1 volt
Row 5
Name High Phase to EarthGround Voltage Alarm
Set ((Ai Phase to Earth/Ground Volts ≥ Custom Variable 05) OR
Expression (Bi Phase to Earth/Ground Volts ≥ Custom Variable 05) OR
(Ci Phase to Earth/Ground Volts ≥ Custom Variable 05) OR
(Ax Phase to Earth/Ground Volts ≥ Custom Variable 05) OR
(Bx Phase to Earth/Ground Volts ≥ Custom Variable 05) OR
(Cx Phase to Earth/Ground Volts ≥ Custom Variable 05))
Reset ((Ai Phase to Earth/Ground Volts ≤ (Custom Variable 06+(Custom Variable 05 - Custom Variable 06) × 0.9)) AND
Expression (Bi Phase to Earth/Ground Volts ≤ (Custom Variable 06+(Custom Variable 05 - Custom Variable 06) × 0.9)) AND
(Ci Phase to Earth/Ground Volts ≤ (Custom Variable 06+(Custom Variable 05 - Custom Variable 06) × 0.9)) AND
(Ax Phase to Earth/Ground Volts ≤ (Custom Variable 06+(Custom Variable 05 - Custom Variable 06) × 0.9)) AND
(Bx Phase to Earth/Ground Volts ≤ (Custom Variable 06+(Custom Variable 05 - Custom Variable 06) × 0.9)) AND
(Cx Phase to Earth/Ground Volts ≤ (Custom Variable 06+(Custom Variable 05 - Custom Variable 06) × 0.9)))
Comment
Custom Ai Phase to Earth/Ground Volts High Alarm 1 volt
Logic Tool Bi Phase to Earth/Ground Volts High Alarm 1 volt
Variable Ci Phase to Earth/Ground Volts High Alarm 1 volt
Logging Ax Phase to Earth/Ground Volts High Alarm 1 volt
Bx Phase to Earth/Ground Volts High Alarm 1 volt
Cx Phase to Earth/Ground Volts High Alarm 1 volt
Row 6
Name Low Phase to EarthGround Voltage Alarm
Set ((Ai Phase to Earth/Ground Volts ≤ Custom Variable 06) OR
Expression (Bi Phase to Earth/Ground Volts ≤ Custom Variable 06) OR
(Ci Phase to Earth/Ground Volts ≤ Custom Variable 06) OR
(Ax Phase to Earth/Ground Volts ≤ Custom Variable 06) OR
(Bx Phase to Earth/Ground Volts ≤ Custom Variable 06) OR
(Cx Phase to Earth/Ground Volts ≤ Custom Variable 06))
Reset ((Ai Phase to Earth/Ground Volts ≥ (Custom Variable 06+(Custom Variable 05 - Custom Variable 06) × 0.1)) AND
Expression (Bi Phase to Earth/Ground Volts ≥ (Custom Variable 06+(Custom Variable 05 - Custom Variable 06) × 0.1)) AND
(Ci Phase to Earth/Ground Volts ≥ (Custom Variable 06+(Custom Variable 05 - Custom Variable 06) × 0.1)) AND
(Ax Phase to Earth/Ground Volts ≥ (Custom Variable 06+(Custom Variable 05 - Custom Variable 06) × 0.1)) AND
(Bx Phase to Earth/Ground Volts ≥ (Custom Variable 06+(Custom Variable 05 - Custom Variable 06) × 0.1)) AND
(Cx Phase to Earth/Ground Volts ≥ (Custom Variable 06 + (Custom Variable 05 - Custom Variable 06) × 0.1)))
Comment
Custom Ai Phase to Earth/Ground Volts Low Alarm 1 Volts
Logic Tool Bi Phase to Earth/Ground Volts Low Alarm 1 Volts
Variable Ci Phase to Earth/Ground Volts Low Alarm 1 Volts
Logging Ax Phase to Earth/Ground Volts Low Alarm 1 Volts
Bx Phase to Earth/Ground Volts Low Alarm 1 Volts
Cx Phase to Earth/Ground Volts Low Alarm 1 Volts
Parameter Value
Row 7
Name High Earth/Ground Current Alarm
Set Expression (Earth/Ground Current ≥ Custom Variable 07)
Reset Expression (Earth/Ground Current ≤ (Custom Variable 08 + (Custom Variable 07 - Custom Variable 08) × 0.9))
Comment
Custom Logic Tool Earth/Ground Current High Alarm 0.1 Amps
Variable Logging
Row 8
Name Low Earth/Ground Current Alarm
Set Expression (Earth/Ground Current ≤ Custom Variable 08)
Reset Expression (Earth/Ground Current ≥ (Custom Variable 08 + (Custom Variable 07 - Custom Variable 08) × 0.1))
Comment
Custom Logic Tool Earth/Ground Current Low Alarm 0.1 amp
Variable Logging
Row 9
Name High System Power Alarm
Set Expression ((Apparent Power-S ≥ Custom Variable 09) OR
(Reactive Power-Q ≥ Custom Variable 09) OR
(Real Power-P ≥ Custom Variable 09))
Reset Expression ((Apparent Power-S ≤ (Custom Variable 10 + (Custom Variable 09 - Custom Variable 10) × 0.9)) AND
(Reactive Power-Q ≤ (Custom Variable 10 + (Custom Variable 09 - Custom Variable 10) × 0.9)) AND
(Real Power-P ≤ (Custom Variable 10 + (Custom Variable 09 - Custom Variable 10) × 0.9)))
Comment
Custom Logic Tool Apparent Power-S High Alarm 1kVA
Variable Logging Reactive Power-Q High Alarm 1kVAR
Real Power-P High Alarm 1kW
Row 10
Name Low System Power Alarm
Set Expression ((Apparent Power-S ≤ Custom Variable 10)
OR (Reactive Power-Q ≤ Custom Variable 10)
OR (Real Power-P ≤ Custom Variable 10))
Reset Expression ((Apparent Power-S ≥ (Custom Variable 10 + (Custom Variable 09 - Custom Variable 10) × 0.1)) AND
(Reactive Power-Q ≥ (Custom Variable 10 + (Custom Variable 09 - Custom Variable 10) × 0.1)) AND
(Real Power-P ≥ (Custom Variable 10 + (Custom Variable 09 - Custom Variable 10) × 0.1)))
Comment
Custom Logic Tool Apparent Power-S Low Alarm 1kVA
Variable Logging Reactive Power-Q Low Alarm 1kVAR
Real Power-P Low Alarm 1kW
Row 11
Name High NPS Current Alarm
Set Expression (NPS Current ≥ Custom Variable 11)
Reset Expression (NPS Current ≤ (Custom Variable 12 + (Custom Variable 11 - Custom Variable 12) × 0.9))
Comment
Custom Logic Tool NPS Current High Alarm 0.1 amp
Variable Logging
Row 12
Name Low NPS Current Alarm
Set Expression (NPS Current ≤ Custom Variable 12)
Reset Expression (NPS Current ≥ (Custom Variable 12 + (Custom Variable 11 - Custom Variable 12) × 0.1))
Comment
Custom Logic Tool NPS Current Low Alarm 0.1 amp
Variable Logging

Parameter Value
Custom Logic Tool Variable
Row 1
Name High Phase Current Threshold
Set Value 200.1
Override Value On
Comment
Row 2
Name Low Phase Current Threshold
Set Value 20.2
Override Value On
Comment
Row 3
Name High Phase to Phase Voltage Threshold
Set Value 10000
Override Value On
Comment
Row 4
Name Low Phase to Phase Voltage Threshold
Set Value 4000
Override Value On
Comment
Row 5
Name High Phase to Earth/Ground Voltage Threshold
Set Value 6500
Override Value On
Comment
Row 6
Name Low Phase to Earth/Ground Voltage Threshold
Set Value 2000
Override Value On
Comment
Row 7
Name High Earth/Ground Current Threshold
Set Value 200.0
Override Value On
Comment
Row 8
Name Low Earth/Ground Current Threshold
Set Value 1.8
Override Value On
Comment
Row 9
Name High System Power Threshold
Set Value 5400
Override Value On
Comment
Row 10
Name Low System Power Threshold
Set Value 500
Override Value On
Comment
Row 11
Name High NPS Current Threshold
Set Value 100.0
Override Value On
Comment
Row 12
Name Low NPS Current Threshold
Set Value 1.0
Override Value On
Comment
9.2 Two Stage Low Battery Alarm
The two stage low battery alarm is used to detect when the battery capacity is depleted. And when the determined low voltage
level is detected, the controller trips the attached switchgear. After the trip action the controller shuts down due to the low
power condition. If preferred the map can be modified to raise an alarm via protocol rather than trip the switchgear.
Parameter Value
Filename C:\Documents and Settings\All Users\Application Data\WSOS Switchgear Data\Custom Logic Tool\Low
Battery Voltage Alarm.clt
Product All Switchgear
Version Version A45-2.0
Custom Logic Tool Digital
Row 1
Name Low Battery Voltage Alarm
Set Expression (Battery Voltage ≤ Custom Variable 01) AND Auxiliary Supply Fail
Reset (Battery Voltage ≥ Custom Variable 02)
Expression
Set Action OFF ACR/LBS Control
Comment Low Battery Voltage Alarm
Custom Logic Battery Voltage High And Low Alarm 0.01 volt
Tool Variable
Logging
Custom Logic Tool Variable
Row 1
Name Low Battery Threshold
Set Value 21.60
Override Value On
Comment Low Battery Alarm Threshold
Row 2
Name Low Battery Alarm Reset
Set Value 22.60
Override Value On
Comment Low Battery Alarm Reset Threshold
CLIPCOM23725

Make the most of your energy SM
Schneider Electric (Australia) Pty Limited

Head Office
Postal Address:
Locked Bag 2211
North Ryde B C 1670
www.schneider-electric.com.au/CAPP
©2011 Schneider Electric, All Rights Reserved.

Schneider Electric and Make the most of your energy are
owned by Schneider Electric, or its affiliated companies
in the United States and other countries.

Advc2-3001 CLT Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Advc2-3001 CLT Manual

Uploaded by

Copyright:

Available Formats

Custom Logic Tool

Make the most of your energy

This document describes the user configuration Copyright

1.0 Introduction 5 5.0 Logic Expressions 25

Custom Logic Tool User Guide (ADVC2-3001) | 3

Figure 1: CLT new configuration 8 Revision history:

Response time for logic functions 2.3 seconds

Custom Logic Tool User Guide (ADVC2-3001) | 5

Create a Custom Logic map

Open CLT user interface Select the CLT configuration window

CLT User Interface

Custom Digitals Custom Variables Custom Counters Custom Timers

Save the CLT map.

Using the Custom Logic map

Establish relationship between CLT, IOEX, CPMT and OCP

Digital Analogue Accumulator Digital Custom Analogue

IOEX Tool OCP Tool CPMT Tool

Save the Save the Save the

Test the customised behaviour

Custom Logic Tool User Guide (ADVC2-3001) | 7

3.1 Open the CLT User Interface

3.1.1 Open a New CLT Map

3.1.2 Open an Existing CLT Map

3.1.3 File Names

3.1.5 Process to Edit the CLT Map

CLT User Interface (see page 8).

Select the point to edit by

Custom Logic Tool Worksheet Interface

fx Edit logic expressions in

Logic Expression Builder

Create the logic Find Select

Figure 3: CLT map editing process

Custom Logic Tool User Guide (ADVC2-3001) | 9

Digitals Variables Counters Timers Firmware version CONFIGURATION MODE

Selection buttons Configuration information Mode

Rows Columns – online Columns – user configuration fields.

Figure 4: CLT user interface

4.1 CLT User Interface

4.3 Design and Edit Logic Characteristics

Values Default Minimum, Duration

Reset Reset, Start/Stop

Custom Logic Tool User Guide (ADVC2-3001) | 11

4.4.1 Editing the Basic Parameters

4.4.2 Editing the Advanced Parameters

4.5 Custom Digitals

Figure 5: Custom Digitals flow diagram

4.5.2 Digitals Configuration Worksheet

Figure 6: Custom Digitals worksheet window

Custom Logic Tool – Custom Digitals configuration worksheet Rows

Custom Logic Tool – Custom Digitals configuration worksheet Columns

Custom Logic Tool – Custom Digitals configuration worksheet Columns

Custom Logic Tool User Guide (ADVC2-3001) | 13

Example 1. Switchgear Status

Database point True when False when

Name Change Custom Digital 01 to Confirm Switch Status.

Example 2. Low Battery Trip

Analogue database point Description

4.6 Custom Variables

Active Values Custom

Figure 7: Custom Variables flow diagram

Custom Logic Tool User Guide (ADVC2-3001) | 15

4.6.2 Variables Configuration Worksheet

Figure 8: Custom Variables worksheet window