Woodward DTSC-200 Configuration

37483C
DTSC-200
ATS Controller
Configuration
Software Version 2.0xxx
Manual 37483C
Manual 37483C DTSC-200 - ATS Controller
WARNING
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. Failure to follow instructions can cause personal injury and/or property damage.
The engine, turbine, or other type of prime mover should be equipped with an overspeed
(overtemperature, or overpressure, where applicable) shutdown device(s), that operates totally
independently of the prime mover control device(s) to protect against runaway or damage to the
engine, turbine, or other type of prime mover with possible personal injury or loss of life should the
mechanical-hydraulic governor(s) or electric control(s), the actuator(s), fuel control(s), the driving
mechanism(s), the linkage(s), or the controlled device(s) fail.
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 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.
CAUTION
To prevent damage to a control system that uses an alternator or battery-charging device, make sure
the charging device is turned off before disconnecting the battery from the system.
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 contact while handling the control).
• 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.
OUT-OF-DATE PUBLICATION
This publication may have been revised or updated since this copy was produced. To verify that you
have the latest revision, be sure to check the Woodward website. The revision level is shown at the
bottom of the front cover after the publication number. The latest version of most publications is
available at:
http://www.woodward.com/publications
If your publication is not there, please contact your customer service representative to get the latest
copy.
Important definitions
WARNING
Indicates a potentially hazardous situation that, if not avoided, could result in death or serious injury.
CAUTION
Indicates a potentially hazardous situation that, if not avoided, could result in damage to equipment.
NOTE
Provides other helpful information that does not fall under the warning or caution categories.
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, Woodward assumes no responsibility unless otherwise expressly undertaken.
© Woodward
All Rights Reserved.
Page 2/158 © Woodward

Revision History
Rev. Date Editor Changes

C 2014-01-22 GG Describes Software Version V 2.0012.
Changes to previous software version

New parameter 3463 ’Limit Switch Failure Delay Time’.
• For functional description go to page 67.
• The List of Parameters (Appendix B) is updated. For details see page 143 ff.
New parameter 12891 ’Reset limit switch failure’.
• For functional description go to page 67.
• The List of Parameters (Appendix B) is updated. For details see page 143 ff.
Manual
Description became more detailed, especially what settings are taken into account for
monitoring and control:
• Chapter Breaker, see page 52 ff.
• Parameter 3430 ‘Limit Switch Monitoring’, see page 66.
B 2013-09-18 GG New parameters 8820 and 8821 added for a special application of In-Phase monitoring (Synch
Check). In application mode Util-Util it is possible to define a phase angle range for transfer
condition. See chapter “Monitoring: Load transfer between two utility sources with special
(phase angle) conditions” on page 78 for more details.
New LogicsManager 19.21 and 19.22 S1/S2 failed status and 20.22 Synch. Check active.
See chapter Logical Command Variables: [19.00] - ATS Status Flags and Logical Command
Variables: [20.00] - ATS Status Flags on page 132 for more details.
Manual
Correction: Default setting of parameter 4570 In-phase monitor is “OFF” (see page 145).
Setting range of parameter 4577 explains now special value 0.10 (see page 81).
List of parameters updated.
Minor changes and layout optimization.
A 12-07-11 GG Command Variables 00.16 and 04.01 removed: no auto mode selection.
New unit display language available on parameter 1700: Russian.
Setting range of parameters 10411 … 10415 changed to “1 … 9999”.
NEW 11-11-17 TE Release Software Version 2.0xxx - Based on 37386A
Content
CHAPTER 1. GENERAL INFORMATION ....................................................................................... 8

CHAPTER 2. CONFIGURATION .................................................................................................. 9
Configuration Via The Front Panel ........................................................................................................... 9
Configuration Via PC .............................................................................................................................. 10
Install ToolKit Configuration and Visualization Software ............................................................. 10
Install ToolKit Software ................................................................................................................ 10
Install ToolKit Configuration Files ................................................................................................ 11
Starting ToolKit Software ............................................................................................................. 12
Configure ToolKit Software .......................................................................................................... 13
Connect ToolKit and the DTSC-200 Unit ..................................................................................... 14
View DTSC-200 Data with ToolKit ............................................................................................... 16
Configure the DTSC-200 with ToolKit.......................................................................................... 17
General Information ............................................................................................................................... 18
Important Designations ................................................................................................................ 18
Signal and Command Abbreviations ........................................................................................... 18
Monitoring Functions.................................................................................................................... 19
Function Of The Inputs And Outputs ..................................................................................................... 20
© Woodward Page 3/158

CHAPTER 3. PARAMETERS ..................................................................................................... 22

Language ............................................................................................................................................... 23
Password ............................................................................................................................................... 23
Event History ......................................................................................................................................... 24
Measuring .............................................................................................................................................. 25
Measuring: Rated Values ............................................................................................................ 25
Measuring: Transformers ............................................................................................................ 29
Application ............................................................................................................................................. 31
Application: Application Mode ..................................................................................................... 31
Application: Transfer Timers ....................................................................................................... 32
Application: Transfer Logics (LogicsManager) ............................................................................ 38
Application: Elevator Pre-Signal .................................................................................................. 42
Application: Motor Load Disconnect ............................................................................................ 44
Application: Source Priority Selection ......................................................................................... 45
Breaker .................................................................................................................................................. 52
Breaker: Transfer Switch Type .................................................................................................... 52
Test Modes ............................................................................................................................................ 61
Timer Exerciser ........................................................................................................................... 62
Monitoring .............................................................................................................................................. 66
Monitoring: Alarm Acknowledgement .......................................................................................... 66
Monitoring: Limit Switch Monitoring............................................................................................. 66
Monitoring: Source 1 Monitoring ................................................................................................. 67
Monitoring: Source 2 Monitoring ................................................................................................. 72
Monitoring: In-Phase Monitoring (Synch Check)......................................................................... 77
Monitoring: Overcurrent ............................................................................................................... 86
Monitoring: Overload ................................................................................................................... 88
Monitoring: Engine, Start Failure Source 1 ................................................................................. 90
Monitoring: Engine, Start Failure Source 2 ................................................................................. 90
Monitoring: Battery, Overvoltage ................................................................................................. 91
Monitoring: Battery, Undervoltage ............................................................................................... 93
Monitoring: CANopen Interface ................................................................................................... 95
Discrete Inputs ....................................................................................................................................... 96
Discrete Outputs (LogicsManager) ........................................................................................................ 98
Counters .............................................................................................................................................. 100
Configure Counters: Operation Hours, kWh, and kvarh............................................................ 100
LogicsManager .................................................................................................................................... 102
LogicsManager: Internal Flags .................................................................................................. 102
LogicsManager: Timer ............................................................................................................... 103
Interfaces ............................................................................................................................................. 105
Interfaces: CAN Bus (FlexCAN) ................................................................................................ 105
Interfaces: Serial Interface 1 (RS-232) ...................................................................................... 113
Interfaces: Serial Interface 2 (RS-485) ...................................................................................... 113
System ................................................................................................................................................. 114
System: Configure Display Backlight ........................................................................................ 114
System: Configure Daylight Saving Time .................................................................................. 115
System: Password System ........................................................................................................ 117
System: Real-Time Clock Set ................................................................................................... 119
System: Versions....................................................................................................................... 120
Logical Symbols ................................................................................................................................... 123
Logical Outputs .................................................................................................................................... 124
Logical Outputs: Internal Flags .................................................................................................. 124
Logical Outputs: Internal functions ............................................................................................ 124
Logical Outputs: Relay Outputs ................................................................................................. 125
Logical Command Variables ................................................................................................................ 126
Logical Command Variables: [00.00] - Internal Flags ............................................................... 126
Logical Command Variables: [01.00] - Alarm Classes .............................................................. 127
Logical Command Variables: [03.00] - Engine Control ............................................................. 127
Logical Command Variables: [04.00] - Operating Status .......................................................... 128
Logical Command Variables: [06.00] - Load Alarms ................................................................. 128
Logical Command Variables: [08.00] - System Alarms ............................................................. 129
Logical Command Variables: [09.00] - Discrete Inputs ............................................................. 129

Logical Command Variables: [11.00] - Time Functions ............................................................. 130
Logical Command Variables: [12.00] - External Discrete Inputs (Expansion Board) ................ 130
Logical Command Variables: [13.00] - Internal Relay Output Status ........................................ 131
Logical Command Variables: [14.00] - External Relay Outputs Status ..................................... 131
Logical Command Variables: [19.00] - ATS Status Flags ......................................................... 132
Logical Command Variables: [20.00] - ATS Status Flags ......................................................... 132
Logical Command Variables: [21.00] - ATS Alarms .................................................................. 133
Logical Command Variables: [98.00] - LogicsManager Outputs ............................................... 133
Factory Setting ..................................................................................................................................... 134
Factory Setting: Functions ......................................................................................................... 134
Factory Setting: Relay Outputs .................................................................................................. 139
Factory Setting: Internal Flags ................................................................................................... 141
Discrete Inputs ........................................................................................................................... 142
Product Service Options ...................................................................................................................... 153
Returning Equipment For Repair ......................................................................................................... 153
Packing A Control ...................................................................................................................... 154
Return Authorization Number RAN ............................................................................................ 154
Replacement Parts ............................................................................................................................... 154
How To Contact Woodward ................................................................................................................. 155
Engineering Services ........................................................................................................................... 156
Technical Assistance ........................................................................................................................... 157

Illustrations And Tables
Illustrations
Figure 2-1: ToolKit - visualization screen ................................................................................................................................ 16
Figure 2-2: ToolKit - analog value trending screen .................................................................................................................. 16
Figure 2-3: ToolKit - configuration screen ............................................................................................................................... 17
Figure 3-1: Event history- display............................................................................................................................................. 24
Figure 3-2: Source stable and outage timers ............................................................................................................................. 37
Figure 3-3: External timer bypass - push button ....................................................................................................................... 40
Figure 3-4: Elevator pre-signal - example 1 .............................................................................................................................. 43
Figure 3-7: Source priority selection - S1 preferred .................................................................................................................. 46
Figure 3-8: Source priority selection - S2 preferred .................................................................................................................. 46
Figure 3-9: Load shed relay wiring - standard transition switch ............................................................................................... 50
Figure 3-10: Load shed relay wiring - delayed or closed transition switch ............................................................................... 50
Figure 3-11: Open transition switch - connected to source 1 .................................................................................................... 52
Figure 3-12: Open transition switch - connected to source 2 .................................................................................................... 52
Figure 3-13: Delayed transition switch - connected to source 1 ............................................................................................... 53
Figure 3-14: Delayed transition switch - neutral position ......................................................................................................... 53
Figure 3-15: Delayed transition switch - connected to source 2 ............................................................................................... 53
Figure 3-16: Closed transition switch - connected to source 1 .................................................................................................. 54
Figure 3-17: Closed transition switch - neutral position ........................................................................................................... 54
Figure 3-18: Closed transition switch - connected to source 1 and 2 (overlap position) ........................................................... 54
Figure 3-19: Closed transition switch - connected to source 2 .................................................................................................. 54
Figure 3-20: Breaker - transition pulse ..................................................................................................................................... 58
Figure 3-21: Test modes - load test configured for timer exerciser........................................................................................... 62
Figure 3-22: Test modes - no-load test configured for timer exerciser ..................................................................................... 62
Figure 3-23: Test modes - parameter IDs of the timer exercisers ............................................................................................. 63
Figure 3-24: Test modes - configuring exerciser 1 for a daily exercise .................................................................................... 64
Figure 3-25: Test modes - configuring exerciser 2 for a weekly exercise ................................................................................. 64
Figure 3-26: Test modes - configuring exerciser 3 for a 14-day exercise ................................................................................. 64
Figure 3-27: Test modes - configuring exerciser 4 for a one event exercise ............................................................................. 65
Figure 3-28: Test modes - display screen with pending exercise event .................................................................................... 65
Figure 3-29: Test modes - display screen with running load test .............................................................................................. 65
Figure 3-30: Inphase monitoring............................................................................................................................................... 77
Figure 3-31: Switch reaction time ............................................................................................................................................. 82
Figure 3-32: Monitoring - load time-overcurrent ...................................................................................................................... 86
Figure 3-33: Monitoring - overload .......................................................................................................................................... 88
Figure 3-34: Monitoring - battery overvoltage.......................................................................................................................... 91
Figure 3-35: Monitoring - battery undervoltage........................................................................................................................ 93
Figure 3-36: Discrete inputs - control inputs - operation logic ................................................................................................. 96
Figure 3-37: Interfaces - Principle of PDO mapping .............................................................................................................. 108
Figure 3-38: LogicsManager - function overview .................................................................................................................. 122
Figure 3-39: LogicsManager - display in ToolKit .................................................................................................................. 123
Figure 3-40: LogicsManager - display in LCD ....................................................................................................................... 123

Tables
Table 1-1: Manual - overview ..................................................................................................................................................... 8
Table 3-1: Application - load shed with standard transition switch .......................................................................................... 49
Table 3-2: Application - load shed with delayed or closed transition switch ............................................................................ 50
Table 3-3: Monitoring - standard values - load time-overcurrent.............................................................................................. 86
Table 3-4: Monitoring - standard values - overload .................................................................................................................. 88
Table 3-5: Monitoring - standard values - battery overvoltage ................................................................................................. 91
Table 3-6: Monitoring - standard values - battery undervoltage ............................................................................................... 93
Table 3-7: Discrete inputs - assignment .................................................................................................................................... 96
Table 3-8: Discrete inputs - parameter IDs ............................................................................................................................... 97
Table 3-9: External discrete inputs - parameter IDs .................................................................................................................. 97
Table 3-10: Relay outputs - Assignment ................................................................................................................................... 98
Table 3-11: Discrete outputs - parameter IDs ........................................................................................................................... 99
Table 3-12: External discrete outputs - parameter IDs .............................................................................................................. 99
Table 3-13: Internal flags - parameter IDs .............................................................................................................................. 102
Table 3-14: Daylight saving time - configuration example ..................................................................................................... 115
Table 3-15: Daylight saving time - examplary dates ............................................................................................................... 115
Table 3-16: LogicsManager - command overview ................................................................................................................. 122
Table 3-17: LogicsManager - logical symbols ........................................................................................................................ 123

Chapter 1.
General Information
Type English German
DTSC-200
DTSC-200 - Installation 37482 -
DTSC-200 - Configuration this manual  37483 -
DTSC-200 - Operation 37484 -
DTSC-200 - Application 37485 -
DTSC-200 - Interfaces 37486 -
Table 1-1: Manual - overview
Intended Use The unit must only be operated for the uses described in this manual. The prerequisite for a proper
and safe operation of the product is correct transportation, storage, and installation as well as careful operation
and maintenance.
NOTE
This manual has been developed for a unit fitted with all available options. Inputs/outputs, functions,
configuration screens and other details described, which do not exist on your unit, may be ignored.
The present manual has been prepared to enable the installation and commissioning of the unit. On
account of the large variety of parameter settings, it is not possible to cover every possible
combination. The manual is therefore only a guide. In case of incorrect entries or a total loss of
functions, the default settings can be taken from the enclosed list of parameters at the rear of this
manual.

Chapter 2.
Configuration
Configuration Via The Front Panel

≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Operation of the unit via the front panel is explained in the operation manual 37484. This manual will familiarize
you with the unit, the meanings/functions of the buttons, and the display.

Configuration Via PC
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Install ToolKit Configuration and Visualization Software
NOTE
Woodward’s ToolKit software is required to configure the unit via PC.
Install ToolKit Software

1. Please insert the enclosed Product CD in the CD-ROM drive of your computer
2. The CD is going to start automatically (autostart function needs to be activated)
3. Please go to the section “Software” and follow the instructions described there
Alternatively ToolKit can be downloaded from our Website. Please proceed as follows:
1. Go to http://www.woodward.com/software
2. Select ToolKit in the list and click the “Go” button
3. Click “More Info” to get further information about ToolKit
4. Choose the preferred software version and click “Download”
5. Now you need to login with your e-mail address or register first
6. The download will start immediately
Minimum system requirements for ToolKit:
• Microsoft Windows® 7, Vista SP1 or later, XP (32- & 64-bit);

support for XP will end on 2014-April-8
• Microsoft .NET Framework
• 1 GHz Pentium® CPU
• 512 MB of RAM
• Minimum 800 by 600 pixel screen with 256 colors
• Serial Port
• Serial Extension Cable (null modem cable)
NOTE
Microsoft .NET Framework 4.0 must be installed on your computer to be able to install ToolKit. If not
already installed, Microsoft .NET Framework will be installed automatically. You must be connected to
the internet for this. Alternatively you can use the .NET Framework installer which can be found on the
Product CD.

Install ToolKit Configuration Files

1. Please insert the enclosed Product CD in the CD-ROM drive of your computer
2. The CD is going to start automatically (autostart function needs to be activated)
3. Please go to the section “Configuration Files” and follow the instructions described there
Alternatively ToolKit configuration files can be downloaded from our Website. Please proceed as follows:
1. Go to http://www.woodward.com/software/configfiles/
2. Please insert the part number (P/N) and revision of your device into the corresponding fields
3. Select ToolKit in the application type list
4. Click “Search”
NOTE
ToolKit is using the following files:
*.WTOOL
1 2
File name composition: [P/N1]* -[Revision]_[Language ID]_[P/N2]* -[Revision]_[# of visualized
gens].WTOOL
Example file name: 8440-1234-NEW_US_5418-1234-NEW.WTOOL
Content of the file: Display screens and pages for online configuration, which are associated with
the respective *.SID file
*.SID
2
File name composition: [P/N2]* -[Revision].SID
Example file name: 5418-1234-NEW.SID
Content of the file: All display and configuration parameters available in ToolKit
*.WSET
File name composition: [user defined].WSET
Example file name: DTSC-200_settings.WSET
Content of the file: Default settings of the ToolKit configuration parameters provided by the SID
file or user-defined settings read out of the unit.
1
* P/N1 = Part number of the unit
2
* P/N2 = Part number of the software in the unit

Starting ToolKit Software

1. Start ToolKit via Windows Start menu -> Programs ->Woodward -> ToolKit
2. Please press the button “Open Tool”
3. Go to the “Application” folder and open then the folder equal to the part number (P/N) of your device
(e.g. 8440-1234). Select the wtool file (e.g. 8440-1234-NEW_US_5418-1234-NEW.wtool) and click
“Open” to start the configuration file
4. Now the home page of the ToolKit configuration screen appears

Configure ToolKit Software

1. Start the configuration by using the toolbar. Please go to Tools -> Options
2. The options window will be displayed
a. Adjust the default locations of the configuration files

b. The displayed language can be selected here
3. The changes become effective after clicking “OK”
NOTE
Please use the ToolKit online help for further information.

Connect ToolKit and the DTSC-200 Unit

For configuration of the unit via ToolKit please proceed as follows:
1. Plug the DPC cable into the service port. Use a USB cable/null modem cable to connect the USB/RS-
232 serial port of the DPC to a serial USB/COM port of the PC with.
NOTE
The USB/RS-232 serial interface is only provided via the optional Woodward DPC (direct configuration
cable), which must be connected to the service port. For additional information refer to Chapter
“Service Port” in the installation manual (37482).
2. Open ToolKit via Windows Start menu -> Programs -> Woodward -> ToolKit
3. From the main ToolKit window, click File then select “Open Tool”..., or click the Open Tool icon
on the tool bar.
4. Locate and select the desired tool file (*.WTOOL) in the ToolKit data file directory and click Open.
5. From the main ToolKit window, click Device then click “Connect”, or select the Connect icon on
the toolbar.
6. The connect dialog window will open if the option is enabled.
a. Select the COM port that is connected to the communication cable.

b. Click the “Connect” button.
7. The identifier of the device that ToolKit is connected to, will display in the status bar.
8. If the Communications window opens, select “ToolConfigurator” under Tool Device and close the
Communications window.
9. If the device is security enabled, the Login dialog will appear.

10. Now you are able to edit the DTSC-200 parameters in the main window. Any changes made are written
to the control memory automatically.

SID Files for Using ToolKit on the CAN Bus With Other CANopen Devices
If a PC with ToolKit is connected to the DTSC-200 via a CAN bus with other external CANopen devices (like a
Phoenix Contact I/O expansion board, for example), it may happen that ToolKit cannot establish a connection
with the DTSC-200 because it looks for a SID file for such an external device, which does not exist.
A special *.sid file can be created in this case. Contact Woodward for support or create a *.sid file with the
following content:
<?xml version="1.0" encoding="utf-8"?>

<ServiceInterfaceDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Identifier="[add the
required device application name here]" Specification="EmptyFile">
</ServiceInterfaceDefinition>
The file name must be the same as the Identifier plus the extension *.sid. The file must be stored to the
configured SID file directory.
NOTE
Depending on the computer used and the installed operation system, problems with the
communication via an infrared connection may occur.
NOTE
If your computer is equipped with a Bluetooth interface please deactivate it temporarily in the Windows
system control menu in the case that ToolKit is freezing building up a connection.
NOTE
It is also possible to connect to the unit via CAN bus. If a suitable CAN adapter is used, this may be
selected in the Connect window. We recommend using the IXXAT USB-to-CAN converter using the VCI
V3 driver.
Be sure to configure the correct baud rate and timeout in the Properties dialog of the Connect window.
The Password for CAN Interface 1 (parameter 10402 on page 117) must be entered before being able to
edit the parameters.

View DTSC-200 Data with ToolKit

The following figure shows an example visualization screen of ToolKit:
Figure 2-1: ToolKit - visualization screen
Navigation through the various visualization and configuration screens is performed by clicking on
the and icons, by selecting a navigation button (e.g. ), or by selecting a screen from the drop-down
list to the right of the arrow icons.
It is possible to view a trend chart of up to eight values with the trending tool utility of ToolKit. The following
figure shows a trending screen of the measured battery voltage value:
Figure 2-2: ToolKit - analog value trending screen
Each visualization screen provides for trending of monitored values by right-clicking on a value and selecting the
"Add to trend" function. Trending is initiated by clicking on the Start button. Clicking the Export… button will
save the trend data to a Comma Separated Values (CSV) file for viewing, editing or printing with office software,
like Microsoft Excel, etc. The Properties… button is used to define high and low limits of the scale, sample rate,
displayed time span and color of the graph. The trend functionality is not available if ToolKit is used utilizing a
CAN bus connection to the unit.

Configure the DTSC-200 with ToolKit

The following figure shows an example configuration screen of ToolKit:
Figure 2-3: ToolKit - configuration screen
Entering a new value or selecting a value from a defined list will change the value in a field. The new value is
written to the controller memory by changing to a new field or pressing the Enter key.
Navigation through the various configuration and visualization screens is performed by clicking on the
and icons, by selecting a navigation button (e.g. ), or by selecting a screen from the drop-down list to
the right of the arrow icons.

General Information
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The DTSC-200 has been developed to control ATS (Automatic Transfer Switch) units.
The main purpose of the ATS controller is to control and monitor the transfer switch as well as issuing an engine
start signal to a connected genset control. The controller is continuously monitoring the presence of a source. If
the preferred source fails, it attempts to transfer to a second source (emergency power supply, etc.).
It is NOT the task of an ATS controller to monitor a start/stop sequence. Start and stop failures will be displayed,
but have no effect on the functionality of the controller. Only switch failures or problems with connected position
limit switches, which signal the actual position of the ATS (connected with utility or connected with emergency
power supply, etc.) to the controller, block the ATS controller for further automatic functions.
Important Designations
• Source 1 Usually the preferred power source, e.g. utility supply (depends on application)
• Source 2 Usually the emergency power source, e.g. genset (depends on application)
• Transfer Change from one source to the other
• Blocked Transfer Switch Failure or inhibit command blocks transfer
Signal and Command Abbreviations

• S1 Signal: breaker in source 1 position
• S2 Signal: breaker in source 2 position
• S1O Signal: breaker in source 1 OPEN position
• S2O Signal: breaker in source 2 OPEN position
• C1 Command: close to source 1
• C2 Command: close to source 2
• C1O Command: open from source 1
• C2O Command: open from source 2

Monitoring Functions
Source Monitoring
• Overvoltage / undervoltage
• Overfrequency / underfrequency
• Voltage imbalance
• Rotation field monitoring
NOTE
If one of these monitoring functions is triggered, the ATS controller attempts to change to the non-
preferred source.
Load Monitoring
• Overload
• Overcurrent
Switch Monitoring
• Monitoring for plausible position feedback
• Monitoring for transfer switch failure
NOTE
If one of these monitoring functions is triggered, then all automatic transfers are blocked.
Generator Monitoring
• Unintended stop
• Start failure
Battery Monitoring
• Overvoltage / undervoltage
Interface Monitoring
• Monitoring of the CANopen communication

Function Of The Inputs And Outputs

≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Discrete Inputs
The discrete inputs are grouped into two categories:
• programmable
The programmable discrete input has been programmed with a factory default function using the
LogicsManager. The following text describes how these functions may be changed using the LogicsManager.
• fixed
The discrete input has a specific function that cannot be changed. The discrete input cannot be used in the
LogicsManager.
NOTE
Depending on the configured transfer switch type (parameter 3424); the discrete inputs can be
"programmable" or "fixed". Please refer to Table 3-7 on page 96.
Reply from ATS limit switch: Breaker in source 1 position fixed to discrete input [DI 1], terminal 51/50
 Note: Normally closed (break) contact!
This discrete input indicates to the control that the breaker is closed to source 1 position if it is de-
energized (logic "0").
Reply from ATS limit switch: Breaker in source 2 position fixed to discrete input [DI 2], terminal 52/50
This discrete input indicates to the control that the breaker is closed to source 2 position if it is de-
energized (logic "0").
Reply from ATS limit switch: Breaker in source 1 open position fixed to discrete input [DI 3], terminal 53/50
This discrete input indicates to the control that the breaker is in source 1 open position if it is de-
energized (logic "0"). This discrete input is programmable when transfer switch type is configured as
standard.
Reply from ATS limit switch: Breaker in source 2 open position fixed to discrete input [DI 4], terminal 54/50
This discrete input indicates to the control that the breaker is in source 2 open position if it is de-
energized (logic "0"). This discrete input is programmable when transfer switch type is configured as
standard.
Disconnect switch: Inhibit ATS programmable to discrete input [DI 5], terminal 55/50
This discrete input indicates to the control that the disconnect switch is actuated. If this discrete input is
de-energized (logic "0"), the "Inhibit ATS" function is enabled.
Control Inputs programmable to discrete inputs [DI 6] through [DI 12], terminals 56 through 62 / 50
These discrete inputs may be used as control signals for functions, including priority selection, remote
peak shave, inhibit transfer, etc. The control inputs can be configured freely. Please refer to Discrete
Inputs on page 86.

Relay Outputs
The discrete outputs are grouped into two categories:
• programmable
The relay output is freely programmable using the LogicsManager (which is described in the following text).
• pre-defined
The relay output has been pre-defined (programmed) with this function using the LogicsManager (which is
described in the following text). The function may be changed by using the LogicsManager.
NOTE
The relay outputs can be "programmable" or "pre-defined" for a specific function required for the
configured transfer switch type (parameter 3424). Please refer to Table 3-10 on page 98.
LogicsManager Relay {all} programmable to relay [R1] through [R3], terminals 32 through 34 / 31
 Note: Normally open (make) contact!
All relays not assigned a defined function, may be configured via the LogicsManager.
LogicsManager Relay {all} programmable to relay [R4], terminals 35/36/37

 Note: Change-over contact!
All relays not assigned a defined function, may be configured via the LogicsManager.
Start engine {all} pre-defined to relay [R5], terminals 39/40/41

 Note: Change-over contact!
By energizing (or de-energizing, depending on the utilized contact) this relay an engine start signal will
be issued to the genset control.
Command: close to source 1 position {all} pre-defined to relay [R6], terminals 42/43
By energizing this relay, a "close to source 1 position" command will be issued to the ATS.
Command: close to source 2 position {all} pre-defined to relay [R7], terminals 44/45
By energizing this relay, a "close to source 2 position" command will be issued to the ATS.
Command: open from source 1 position to neutral position{all} pre-defined to relay [R8], terminals 46/47
By energizing this relay, an "open from source 1 position to neutral position" command will be issued
to the ATS.
Command: open from source 2 position to neutral position{all} pre-defined to relay [R9], terminals 48/49
By energizing this relay, an "open from source 2 position to neutral position" command will be issued
to the ATS.

Chapter 3.
Parameters
The description of the parameters is confined to the illustration via the PC-program. The parameters are described
as follows.

Language
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The following parameter is used to set the unit display language.
Language Set language English / Deutsch / Español / Polski / Russian

EN
Language
DE
CL0 {0} {1} {2} The desired language for the unit display text is configured here.
1700   
Password
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The DTSC-200 utilizes a password protected multi-level configuration access hierarchy. This permits varying
degrees of access to the parameters being granted by assigning unique passwords to designated personnel. A
distinction is made between the access levels as follows:
Code level CL0 (User Level) Standard password = none

This code level permits for monitoring of the system and limited access to the parameters. Configuration of the
control is not permitted. Only the parameters for setting the language, the date, the time, and the horn reset time
are accessible. The unit powers up in this code level.
Code level CL1 (Basic Level) Standard password = "0 0 0 1"

This code level entitles the user to change selected non-critical parameters, such as setting the parameters
accessible in CL0 plus Bar/PSI, °C/°F. The user may also change the password for level CL1. Access granted by
this password expires two hours after the password has been entered and the user is returned to the CL0 level.
Code level CL2 (Temporary Commissioning Level) No standard password available

This code level grants temporary access to most of the parameters. The password is calculated from the random
number generated when the password is initially accessed. It is designed to grant a user one-time access to a
parameter without having to give him a reusable password. The user may also change the password for
level CL1. Access granted by this password expires two hours after the password has been entered and the user is
returned to the CL0 level. The password for the temp. commissioning level may be obtained from the vendor.
Code level CL3 (Commissioning Level) Standard password = "0 0 0 3"

This code level grants complete and total access to most of the parameters. In addition, the user may also change
the passwords for levels CL1, CL2 and CL3. Access granted by this password expires two hours after the
password has been entered and the user is returned to the CL0 level.
NOTE
Once the code level is entered, access to the configuration menus will be permitted for two hours or
until another password is entered into the control. If a user needs to exit a code level then code level
CL0 should be entered. This will block unauthorized configuration of the control. A user may return to
CL0 by allowing the entered password to expire after two hours or by changing any one digit on the
random number generated on the password screen and entering it into the unit.
It is possible to disable expiration of the password by entering "0000" after the CL1 or CL3 password
has been entered. Access to the entered code level will remain enabled until another password is
entered. Otherwise, the code level would expire when loading the standard values (default 0000) via
ToolKit.
Password Password: Entry via front panel 0000 to 9999

EN
Passwort
DE
CL {0} {1} {2} The password for configuring the control via the front panel must be entered here.
0   
10416

Event History
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The event history is a FIFO (First In/First Out) memory for logging alarm events and operation states of the unit.
The capacity of the event history is 300 entries. As new event messages are entered into the history, the oldest
messages are deleted once 300 events have occurred.
The individual alarm messages, which are stored in the event history, are described in detail in ‘Appendix A:
Alarm Messages’ operation manual 37484. The operation states, which are stored in the event history, are listed
in the table below.
The event history display is password-protected.
Figure 3-1: Event history- display
NOTE
The button deletes the highlighted entry!
A date/time stamp is added to each entry. Additional characters (+ and -) indicate the state of the alarm. The
"+" character indicates an alarm condition that is still active. If the alarm conditions are no longer present
anymore, the "+" character will be changed to "-".
Event history display Event history: Display event history Info

EN
Ereignisspeicher anzeigen
DE
CL2 {0} {1} {2} Individual entries can be selected with the or keys and deleted from the event
   history with the key.
NOTE
Refer to ‘Appendix A: Alarm Messages’ operation manual 37484 for a complete list of all entries, which
may appear in the event history.
Clear event log Event history: Clear event history YES / NO

EN
Ereignisspeicher löschen
DE
CL2 {0} {1} {2} YES ..............The complete event history will be deleted. After the event history
1706    has been deleted, this parameter changes back to "NO" automatically.
NO ................The event history will not be deleted.

Measuring
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
NOTE
This controller is available in two different hardware version with either 1A [../1] or 5A [../5] current
transformer inputs. Both versions are discussed in this manual. The set points for specific parameters
will differ depending upon the hardware version.
NOTE
It is absolutely necessary for correct rated voltage values to be entered, as many measurement and
monitoring functions refer to these values.
Measuring: Rated Values
Rated system frequency Rated system frequency 50/60 Hz

EN
Nennfrequenz im System
DE
CL2 {0} {1} {2} The rated frequency of the system is used as a reference figure for all frequency
  
1750
related functions, which use a percentage value, like frequency monitoring or
breaker operation windows.
Rated voltage S1 Rated voltage source 1 50 to 650,000 V

EN
Nennspannung S1
DE
CL2 {0} {1} {2}  This value refers to the rated voltage of source 1 and is the voltage
1774    measured on the potential transformer primary.
The source 1 potential transformer primary voltage is entered in this parameter. The
source 1 rated voltage is used as a reference figure for all source 1 voltage related
functions, which use a percentage value, like utility voltage monitoring or breaker
operation windows.
Rated voltage S2 Rated voltage source 2 50 to 650,000 V

EN
Nennspannung S2
DE
CL2 {0} {1} {2}  This value refers to the rated voltage of source 2 and is the voltage
1772    measured on the potential transformer primary.
The source 2 potential transformer primary voltage is entered in this parameter. The
source 2 rated voltage is used as a reference figure for all source 2 voltage related
functions, which use a percentage value, like utility voltage monitoring or breaker
operation windows.

EN
S1 voltage measuring Measurement principle: Source 1 3Ph 4W / 3Ph 3W / 1Ph 2W / 1Ph 3W
S1 Spannungsmessung
DE
CL2 {0} {1} {2}  Please refer to the comments on measuring principles in the installation
1862    manual (37482).
3Ph 4W ........Measurement is performed Line-Neutral (WYE connected system).

Phase voltages and the neutral must be connected for proper
calculation. The measurement, display and protection are adjusted
according to the rules for WYE connected systems. Monitoring refers
to the following voltages:
• VL12, VL23, and VL31, or
• VL1N, VL2N and VL3N.
3Ph 3W ........Measurement is performed Line-Line (Delta connected system).
Phase voltages must be connected for proper calculation. The
measurement, display and protection are adjusted according to the
rules for Delta connected systems. Monitoring refers to the following
voltages:
• VL12, VL23, VL31.
1Ph 2W ........Measurement is performed for single-phase systems. The
rules for single-phase systems. Monitoring refers to the following
voltages:
• VL1N, VL12
The measurement, display, and protection are adjusted according to
the rules for single-phase systems. Monitoring refers to the following
voltages:
• VL1N, VL3N.

S2 voltage measuring Measurement principle: Source 2 3Ph 4W / 3Ph 3W / 1Ph 2W / 1Ph 3W
EN
S2 Spannungsmessung
DE
1861    manual (37482).

Phase voltages and the neutral must be connected for proper
calculation. The measurement, display and protection are adjusted
according to the rules for WYE connected systems. Monitoring
refers to the following voltages:
• VL12, VL23, and VL31, or
• VL1N, VL2N and VL3N.
3Ph 3W ........Measurement is performed Line-Line (Delta connected system).
Phase voltages must be connected for proper calculation. The
rules for Delta connected systems. Monitoring refers to the
following voltages:
• VL12, VL23, VL31.
1Ph 2W ........Measurement is performed for single-phase systems. The
rules for single-phase systems. Monitoring refers to the following
voltages:
• VL1N, VL12
The measurement, display, and protection are adjusted according to
the rules for single-phase systems. Monitoring refers to the
following voltages:
• VL1N, VL3N.
1Ph2W voltage measuring Measurement principle: 1Ph 2voltage measuring Ph – Ph / Phase - N

EN
Art der 1Ph2W Messung

DE
1858    manual (37482).
This parameter is only visible, if parameter 1862 and/or parameter 1861 is

configured as "1Ph 2W".
Ph – Ph .........The phase-phase voltages are monitored for 1Ph 2W measuring.

Phase - N ......The phase-neutral voltages are monitored for 1Ph 2W measuring.
1Ph2W phase rotation Measurement principle: 1Ph 2W phase rotation CW / CCW

EN
Art der 1Ph2W Drehrichtung

DE
1859    manual (37482).
This parameter is only visible, if parameter 1862 and/or parameter 1861 is

CW ...............A clockwise rotation field is considered for 1Ph 2W measuring.

CCW ............A counter-clockwise rotation field is considered for 1Ph 2W
measuring.

EN
S1 Load current measuring Measurement principle: S1 Load current L1 L2 L3 / Phase L1 / Phase L2 / Phase L3
S1 Last Strommessung
DE
1863    manual (37482).
L1 L2 L3 ......All three phases are monitored. The measurement, display and

protection are adjusted according to the rules for 3-phase
measurement. Monitoring refers to the following currents:
• IL1, IL2, IL3.
Phase L{1/2/3} Only one phase is monitored. The measurement, display and
protection are adjusted according to the rules for single-phase
measurement. Monitoring refers to the selected phase.
Current and power from source 1 to the load are only measured, if the transfer
switch is closed to source 1 position (S1).
Parameters 1860 and 1863 must be configured identical because they share one
common CT set at the load connection.
S2 Load current measuring Measurement principle: S2 Load current L1 L2 L3 / Phase L1 / Phase L2 / Phase L3
EN
S2 Last Strommessung
DE
1860    manual (37482).
L1 L2 L3 ......All three phases are monitored. The measurement, display and

protection are adjusted according to the rules for 3-phase
measurement. Monitoring refers to the following currents:
• IL1, IL2, IL3.
Phase L{1/2/3} Only one phase is monitored. The measurement, display and
protection are adjusted according to the rules for single-phase
measurement. Monitoring refers to the selected phase.
Current and power from source 2 to the load are only measured, if the transfer
switch is closed to source 2 position (S2).
The parameters 1860 and 1863 must be configured identical because they share one
common CT set at the load connection.
NOTE
It is absolutely necessary for correct rated power and current values to be entered, as many
measurement and monitoring functions refer to these values.
Rated active power [kW] Rated active power 0.5 to 99,999.9 kW

EN
Nennwirkleistung [kW]
DE
CL2 {0} {1} {2} This value specifies the rated power.
1752   
Rated current Rated current 5 to 32,000 A

EN
Nennstrom
DE
CL2 {0} {1} {2} This value specifies the rated current.
1754   

Measuring: Transformers
Voltage Transformer
EN
S1 voltage transf. primary Voltage transformer, source 1, primary 50 to 650,000 V
S1 Spannungswandler primär
DE
CL2 {0} {1} {2} Some applications may require the use of potential transformers to facilitate
  
1819
measuring the source voltages. The rating of the primary side of the potential
transformer on source 1 must be entered into this parameter.
If the application does not require potential transformers (i.e. the generated voltage
is 480 V or less), then the source volt. will be entered into this parameter.
S1 voltage transf. secondary Voltage transformer, source 1, secondary 50 to 480 V

EN
S1 Spannungswandler sekund.
DE
CL2 {0} {1} {2}  The control is equipped with dual voltage measuring inputs. The voltage
1818    range of these measurement inputs is dependent upon which input
terminals are used (see below). This value refers to the secondary voltages
of the potential transformers, which are directly connected to the control.
Some applications may require the use of potential transformers to facilitate

measuring the source voltages. The rating of the secondary side of the potential
• Rated voltage: 120 Vac (this parameter configured between 50 and 130 V)
- Source 1 voltage: Terminals 15/17/19/21
S2 volt. transf. primary Voltage transformer, source 2, primary 50 to 650,000 V

EN
S2 Spannungswandler primär
DE
CL2 {0} {1} {2} Some applications may require the use of potential transformers to facilitate
1816    measuring the source voltages. The rating of the primary side of the potential
S2 volt. transf. secondary Voltage transformer, source 2, secondary 50 to 480 V

EN
S2 Spannungswandler sekund.
DE
CL2 {0} {1} {2}  The control is equipped with dual voltage measuring inputs. The voltage
1815    range of these measurement inputs is dependent upon which input
terminals are used (see below). This value refers to the secondary voltages
of the potential transformers, which are directly connected to the control.
Some applications may require the use of potential transformers to facilitate

measuring the source voltages. The rating of the secondary side of the potential

Current Transformer
NOTE
This controller is available in two different hardware version with either 1A [../1] or 5A [../5] current
transformer inputs. Both versions are discussed in this manual. The set points for specific parameters
will differ depending upon the hardware version, indicated on the data plate.
• [1] DTSC-200-1 = Current transformer with ../1 A rated current
• [5] DTSC-200-5 = Current transformer with ../5 A rated current
Load Current transformer Current transformer, load 1 to 32,000/5 A

EN
Last Stromwandler
DE
CL2 {0} {1} {2} This screen only applies to controls equipped with 5 A CT inputs. This
  
1821
will not be displayed in the controller screen of a unit equipped with 1 A
CT inputs.
The input of the current transformer ratio is necessary for the indication and
control of the actual monitored value. The current transformers ratio should be
selected so that at least 60% of the secondary current rating can be measured
when the monitored system is at 100% of operating capacity (i.e. at 100% of
system capacity a 5 A CT should output 3 A). If the current transformers are sized
so that the percentage of the output is lower, the loss of resolution may cause
inaccuracies in the monitoring and control functions and affect the functionality
of the control.
Load Current transformer Current transformer, load 1 to 32,000/1 A

EN
Last Stromwandler
DE
CL2 {0} {1} {2} This screen only applies to controls equipped with 1 A CT inputs. This
1822    will not be displayed in the controller screen of a unit equipped with 5 A
CT inputs.
The input of the current transformer ratio is necessary for the indication and
control of the actual monitored value. The current transformers ratio should be
selected so that at least 60% of the secondary current rating can be measured
when the monitored system is at 100% of operating capacity (i.e. at 100% of
system capacity a 5 A CT should output 3 A). If the current transformers are sized
so that the percentage of the output is lower, the loss of resolution may cause
inaccuracies in the monitoring and control functions and affect the functionality
of the control.

Application
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Application: Application Mode
Application mode Application mode Util-Gen / Gen-Gen / Util-Util

EN
Betriebsmodus
DE
CL2 {0} {1} {2} This parameter selects the basic function of the unit. If the unit is used to transfer
4148    the load between two utility sources (setting "Util-Util"), no engine start signals are
issued.
Util-Util ....... Application "utility-utility" {0}

No engine start signals will be issued.
Source 1 Source 2
Util-Gen ....... Standard application "utility-generator" {1}
Engine start signals will be issued for source 2 only.
G
Source 1 Source 2
Gen-Gen ...... Application "generator-generator" {2}
Engine start signals will be issued for source 1 and source 2.
G G
Source 1 Source 2
NOTE
In Util-Gen application, source S2 is considered as the generator.
NOTE
Refer to the application chapter of the Application manual 37485 for details.

Application: Transfer Timers

Examples transfer delay:
NOTE
Please refer to “Transfer delay timer S1->S2” (parameter 4496) and “Transfer delay timer S2->S1”
(parameter 4497) for details.
Scenario 1 ..... Transfer delay timer is configured to a value > 0 seconds

Elevator pre-transfer signal is “Disabled”
Motor load disconnect signal is “Disabled”

Elevator pre-transfer signal is “Enabled”

Elevator pre-transfer signal is “Enabled”
Motor load disconnect signal is “Enabled”

Transfer commit Transfer commit YES / NO
EN
Transfer zustimmen
DE
CL2 {0} {1} {2} This function is only effective if a transfer from the preferred source to the non-
4146 ---  --- preferred source is requested.
YES .............. A transfer to the non-preferred source is committed as soon as the

non-preferred source stable timer has started to count. The transfer
will be performed after the stable timer has expired, even if the
preferred source restores. A transfer is committed even if priority
source returns while the non-preferred source start timer is counting.
NO................ A transfer to the non-preferred source is only committed, if the non-
preferred source stable timer has expired completely.
If the preferred source restores while the non-preferred source stable
timer is still counting, the whole process will be aborted and the
transfer switch remains on the preferred source. Even after stable
timer expires, if transfer timer starts, and S1 is restored, S2 goes into
cool down.
Transfer delay timer S1->S2 Transfer delay timer S1->S2 0 to 6500 s

EN
Transfer Verzögerung S1->S2

DE
CL2 {0} {1} {2} Usually a transfer to S2 is performed as soon as the “S2 source stable time”
4496 --- ---  (parameter 3332) has expired. The “Transfer delay timer S1S2” can be used to
add an additional delay to the transfer, after the “S2 source stable time” has expired.
If the “Transfer delay timer S1S2” is configured to “0 Seconds”, it will

automatically be de-activated and no longer be taken into account during transfers.
If the “Transfer delay timer S1S2” is configured to a value > 0 Seconds, it will
always be triggered after the S2 stable delay timer has expired. A bypass of the
timer is possible via the “Bypass “Softkey on the display screen or via
LogicsManager “Ext. bypass” (parameter 12820). Once this timer is configured to a
value >0 it will always be active during each transfer. It will never be automatically
bypassed.
Trigger conditions for “Transfer delay timer S1S2”:
1. A transfer to S2 has been initiated

2. The S2 stable timer has expired
3. “Transfer delay timer S1S2” is configured to a
value larger than “0 Seconds”.

Transfer delay timer S2->S1 Transfer delay timer S2->S1 0 to 6500 s

EN
Transfer Verzögerung S2->S1

DE
CL2 {0} {1} {2} Usually a transfer to S1 is performed as soon as the “S1 source stable time”
4497 --- ---  (parameter 3333) has expired. The “Transfer delay timer S2S1” can be used to
add an additional delay to the transfer, even if the “S1 source stable time” has
already expired.
If the “Transfer delay timer S2S1” is configured to “0 Seconds”, it will

automatically be de-activated and no longer be taken in account during transfers.
If the “Transfer delay timer S2S1” is configured to a value > 0 Seconds, it will
always be triggered after the S1 stable delay timer has expired. A bypass of the
timer is possible via the “Bypass “Softkey on the display screen or via
LogicsManager “Ext. bypass” (parameter 12820). Once this timer is configured to a
value >0 it will always be active during each transfer. It will never be automatically
bypassed.
Trigger conditions for “Transfer delay timer S2S1”:
1. A transfer to S1 has been initiated

2. The S1 stable timer has expired
3. “Transfer delay timer S2S1” is configured to a
value larger than “0 Seconds”.
S1 start delay time Source 1 start delay time 0 to 300 s

EN
S1 Startverzögerung
DE
CL2 {0} {1} {2} This parameter delays the energizing/de-energizing of the start relay ( engine start)
4149 --- ---  if source 2 is considered as "not OK" or a start, "Load Test", " No Load Test",
remote peak shave or interruptible power rates request is performed.
The counter starts as soon as source 2 is considered as "not OK" or the start request
is initiated.
If source 2 returns before this counter has expired, the timer will be terminated and
the controller returns to standby mode (since it is not intended that the engine starts
with every short temporary line fault).
If the timer has expired and source 2 has not been considered as "OK", the engine
start relay will be energize/de-energize, the engine will be started, and flag 20.05
"S1 Start Signal" will be enabled.
If this timer is running, the "S1 start delay" message and the Bypass softkey are
displayed.
S2 start delay time Source 2 start delay time 0 to 300 s

EN
S2 Startverzögerung
DE
CL2 {0} {1} {2} This parameter delays the energizing/de-energizing of the start relay (engine start)
3330 ---   if source 1 is considered as "not OK" or a start, "Load Test", " No Load Test",
remote peak shave or interruptible power rates request is performed.
The counter starts as soon as source 1 is considered as "not OK" or the start request
is initiated.
If source 1 returns before this counter has expired, the timer will be terminated and
the controller returns to standby mode (since it is not intended that the engine starts
with every short temporary line fault).
If the timer has expired and source 1 has not been considered as "OK", the engine
start relay will energize/de-energize, the engine will be started, and flag 20.06 "S2
Start Signal" will be enabled.
If this timer is running, the "S2 start delay" message and the Bypass softkey are
displayed.

S1 Source Stable time Source 1 source stable time 1 to 6500 s
EN
S1 Stabilisierzeit
DE
CL2 {0} {1} {2} This parameter configures the delay before source 1 is considered as OK. This
3333    timer starts after the last monitored value has returned within the restore limits
following a source 1 outage. Source 1 will be considered as OK again after this
timer has expired. If the voltage and/or frequency exceeds the restore limits again
before the timer expires, the timer will be reset (refer to Figure 3-2).
The source 1 stable timer is automatically bypassed if source 1 is the preferred
source and the outage delay of source 2 (non-preferred) has expired.
If source 1 fails unexpectedly before this timer has expired, it will be terminated
and the load will still be supplied by source 2.
This timer is intended to delay the transfer to ensure that source 1 voltage and
frequency are definitely stable before the ATS switch is operated to perform a
transfer to source 1.
If this timer is running, the "S1 stable timer" message and the Bypass softkey are
displayed.
The S1 source stable timer is automatically bypassed, when the transfer switch is in
neutral position and only S1 is available (only valid if the parameter “Transfer
switch type” (parameter 3424) is configured to “Delayed” or “Closed”. This
ensures the fastest possible transfer to S1 if the DTSC-200 is powered up while the
system is in neutral position.
NOTE
In case a "load test" is being performed (i.e. the load is supplied by source 2, but source 1 is present as
well and OK) and source 2 fails, the "S1 source stable timer" will be bypassed completely to be able to
change back (OK) to source 1 immediately. This is intended to ensure that the load is not de-energized
if a genset failure takes place during a load test.
S2 Source Stable time Source 2 source stable time 1 to 6500 s

EN
S2 Stabilisierzeit
DE
CL2 {0} {1} {2} This parameter configures the delay before source 2 is considered as OK. This
3332    timer starts after the last monitored value has returned within the restore limits
following a source 2 outage. Source 2 will be considered as OK again after this
timer has expired. If the voltage and/or frequency exceeds the restore limits again
before the timer expires, the timer will be reset (refer to Figure 3-2).
The source 2 stable timer is automatically bypassed if source 2 is the preferred
source and the outage delay of source 1 (non-preferred) has expired.
If source 2 fails unexpectedly before this timer has expired, it will be terminated
and the load will still be supplied by source 1.
This timer is intended to delay the transfer to ensure that source 2 voltage and
frequency are definitely stable before the ATS switch is operated to perform a
transfer to source 2.
If this timer is running, the "S2 stable timer" message and the Bypass softkey are
displayed.
The S2 source stable timer is automatically bypassed, when the transfer switch is in
neutral position and only S2 is available (only valid if the parameter “Transfer
switch type” (parameter 3424) is configured to “Delayed” or “Closed”. This
ensures the fastest possible transfer to S2 if the DTSC-200 is powered up while the
system is in neutral position.

EN
S1 outage delay Source 1 outage delay 0.1 to 10.0 s
S1 Ausfallverzögerung
DE
CL2 {0} {1} {2} This timer defines the maximum time before source 1 (voltage, frequency and
2804 --- ---  phase rotation) is considered as "not OK" to initiate a transfer to source 2. This
timer starts if any of the monitored source 1 values exceeds the fail limits. Source 1
will be considered as "not OK", after this timer has expired. If the voltage and/or
frequency returns within the fail limits before the timer expires, the timer will be
reset (refer to Figure 3-2).
This timer is intended to prevent an immediate transfer to source 2 in case of a
temporary voltage or frequency drop during a load test due to a short temporary
failure of source 1 (i.e. ignition miss of a genset, etc.).
If this timer has expired, the alarm "Unint. stop S1" is issued.
Note: If source 2 is the "preferred source" and the "S1 outage delay" timer has
expired (i.e. source 1 is considered as "not OK"), the "S2 source stable timer" will
be bypassed.
S2 outage delay Source 2 outage delay 0.1 to 10.0 s

EN
S2 Ausfallverzögerung
DE
CL2 {0} {1} {2} This timer defines the maximum time before source 2 (voltage, frequency and
2803 ---   phase rotation) is considered as "not OK" to initiate a transfer to source 1. This
timer starts if any of the monitored source 2 values exceeds the fail limits. Source 2
will be considered as "not OK", after this timer has expired. If the voltage and/or
frequency returns within the fail limits before the timer expires, the timer will be
reset (refer to Figure 3-2).
This timer is intended to prevent an immediate transfer to source 1 in case of a
temporary voltage or frequency drop during a load test due to a short temporary
failure of source 2 (i.e. ignition miss of a genset, etc.).
If this timer has expired, the alarm "Unint. stop S2" is issued.
Note: If source 1 is the "preferred source" and the "S2 outage delay" timer has
expired (i.e. source 2 is considered as "not OK"), the "S1 source stable timer" will
be bypassed.

[V], [f]
rated
value source stable timer source stable timer
restore
value
source source OK
not OK
outage outage
delay delay
timer timer
fail
value
source is stable [t]

stable timer start outage timer start source has failed
stable timer start outage timer start
Figure 3-2: Source stable and outage timers
NOTE
Figure 3-2 describes the principle of stable and outage timers for an example where a threshold needs
to be exceeded to consider the source as "OK" (like underfrequency or undervoltage).
In cases which a value needs to drop below the threshold for that source to be considered as OK
(overfrequency, voltage imbalance or overvoltage), the restore value is lower than the fail value.
S1 cooldown time Engine 1 cooldown time 1 to 6500 s

EN
S1 Nachlaufzeit
DE
CL2 {0} {1} {2} This parameter configures the duration of the cool down phase of engine 1 after the
3343 --- ---  load has been disconnected.
If this timer is running, the "S1 cooldown" message and the Bypass softkey are
displayed.
S2 cooldown time Engine 2 cooldown time 1 to 6500 s

EN
S2 Nachlaufzeit
DE
CL2 {0} {1} {2} This parameter configures the duration of the cool down phase of engine 2 after the
3344 ---   load has been disconnected.
If this timer is running, the "S2 cooldown" message and the Bypass softkey are
displayed.

Application: Transfer Logics (LogicsManager)
NOTE
All functions which are described in the following text may be assigned by the LogicsManager to any
relay which is available via the LogicsManager and not assigned to another function. The assignment
of the defined relays to defined functions occurs by selection of the application mode. The same way
some relays are designated to specific functions, others may be assigned to different functions. These
are listed as "programmed" relays. If a relay is "programmable" the function may be assigned to other
relays by configuring the LogicsManager.
Inhibit ATS
If this logical output becomes TRUE, the ATS controller is blocked against automatic transfers and the "ATS
Inhibit" message is displayed. Usually, a selected relay output is configured to this LogicsManager function,
which may be used to block the ATS controller when a disconnect switch is connected to this "Inhibit ATS" relay
output.
All automatic transfers will be blocked. Only the "Engine start" signal will still be issued.
Inhibit ATS Inhibit ATS LogicsManager

EN
Blockiere ATS
DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 121 in Appendix
  
12600
A: "LogicsManager".
NOTE
The disconnect switch must be located in the ATS cabinet. During a manual transfer, the disconnect
switch is operated to the “Inhibit ATS” position, which will block the controller from performing an
automatic transfer.
WARNING
If the “Inhibit ATS” function is not active during a manual transfer, serious injury may occur!
Always inhibit automatic ATS transfers before performing a manual transfer!

Inhibit Transfer to Source 1

If this logical output becomes TRUE, the transfer back to source 1 will be blocked temporarily and the "Inhib.
XFR to S1" message is displayed.
Application example:
A hospital has a source 1 (preferred source) power failure. Source 2 would then be started, and a transfer to S2
will occur, with the load being supplied by that source. When source 1 returns, a transfer back to S1 may be
prevented by making Inhibit Transfer to Source 1 LogicsManager function TRUE (i.e. energizing a DI). In this
case, a transfer back to source 1 may have some risk involved if a difficult surgery is in progress. A potential
mechanical failure resulting from transfer can be avoided by using this function.
Inhib. XFR to S1 Inhibit transfer to source 1 LogicsManager

EN
Trans S1 sperren
DE
12610    A: "LogicsManager".
Inhibit Transfer to Source 2

If this logical output becomes TRUE, the transfer to source 2 will be blocked temporarily and the "Inhib. XFR to
S2" message is displayed.
This function has the same behavior as the "Inhibit XFR to source 1" function, except that a transfer to source 2
will be prevented.
Inhib. XFR to S2 Inhibit transfer to source 2 LogicsManager

EN
Trans S2 sperren
DE
Remote Peak Shave

If this logical output becomes TRUE, the non-preferred source will be started, a transfer to the non-preferred
source will be performed, and the "Rem.peak shave" message is displayed as soon as the transfer is completed.
The load will then be supplied by the non-preferred source. If the logical output becomes FALSE again, a regular
transfer sequence back to the preferred source will be performed including the expiry of all timers belonging to
this sequence.
If the non-preferred source fails during a remote peak shave request and the preferred source is available, an
immediate transfer back to the preferred source will be performed.
Remote peak shave Remote peak shave LogicsManager

EN
Spitzenlast Modus
DE

Interruptible Power Rate Provisions

If this logical output becomes TRUE, the non-preferred source will be started, a transfer to the non-preferred
source will be performed, and the "Pwr.rate.prov." message is displayed as soon as the transfer is completed. The
load will then be supplied by the non-preferred source. If the logical output becomes FALSE again, a regular
transfer sequence back to the preferred source will be performed including the expiry of all timers belonging to
this sequence.
If the non-preferred source fails during an interruptible power rate provisions request and the preferred source is
available, an immediate transfer back to the preferred source will be performed.
This function may be used in some countries where the provider offers contracts, which contain provisions for the
customer to disconnect from the utility during peak load times and change to a different power supply (e.g.
genset), like the United States. In case the alternative (genset) supply fails during a "Interruptible power rate
provisions" request, a transfer to the preferred source will be performed with the effect that the customer must
pay a reimbursement to the provider.
Int. pow. rates Interruptible power rate provisions LogicsManager

EN
Anforder. Netzbetr.
DE
External Timer Bypass

If this logical output becomes TRUE (by energizing a DI for example), all timers, which are in progress at the
moment and can be bypassed, are bypassed. This has the same effect as pressing the "Bypass" softkey.
Ext. bypass External timer bypass LogicsManager

EN
Ext. Zeit Bypass

DE
  
12820
A: "LogicsManager".
NOTE
If another timer becomes active immediately after the previous timer has been bypassed, the discrete
input must be de-energized before it may be energized again to bypass the next timer. We recommend
using a momentary push-to-make button for this function.
Push button
Discrete input
Figure 3-3: External timer bypass - push button

Gen-Gen Enable
This function is only enabled if the application mode (parameter 4148) is configured to "Gen-Gen". If this logical
output becomes TRUE (by energizing a DI for example), the gen-gen mode will be enabled.
The behavior of the function depends on the source priority:
• Only the LogicsManager function "Source priority S1" (parameter 12680) is TRUE:
The source 1 genset will be started. If source 1 doesn't start or fails, source 2 genset will be started
automatically.
• Only the LogicsManager function "Source priority S2" (parameter 12810) is TRUE:
The source 2 genset will be started. If source 2 doesn't start or fails, source 1 genset will be started
automatically.
• Both source priority LogicsManager functions (parameters 12680 and 12810) are TRUE or both are FALSE:
Source 1 has priority, i.e. the source 1 genset will be started. If source 1 doesn't start, source 2 genset will be
started automatically.
If the gen-gen mode will be disabled again, all start requests are terminated and the genset, which is currently in
operation, will be shut down with a cool down.
Gen-Gen enable Generator-Generator mode enable LogicsManager

EN
Gen-Gen Aktivieren
DE
12830 --- ---  A: "LogicsManager".

Application: Elevator Pre-Signal
The elevator pre-signal flag (20.01) may be assigned to any output relay using the LogicsManager.
The elevator pre-signal is important for buildings which are equipped with elevators. This signal will be enabled
before any transfer in order to signal a transfer to an elevator control. If this signal is received by an elevator
control, the elevator stops at the next floor and opens the doors. This signal is enabled until the transfer is
completed. Then, the signal will be disabled and the elevator is able to operate regularly again.
This function may be used if there is a load test performed during regular hospital operation. A load test means
that two sources are available. This signal will not be set in case of a utility failure. In this case, the elevator
might get stuck between two floors and it makes no sense to enable the elevator pre-signal. Possibly stuck
elevators are accepted and the main target is to attempt to supply the load. As soon as the supply returns, the
elevators are ready to operate again.
NOTE
The elevator pre signal (EPS) may be enabled in parallel with a motor load disconnect signal (MLD) if a
MLD signal is configured. EPS and MLD are two functions, which operate completely independent and
don't affect each other.
If the EPS timer will be bypassed, the MLD signal will be processed consequently (if configured).
Otherwise, the transfer sequence will be continued. If the transfer has been performed, the EPS signal
will be reset. This is also valid, if the EPS signal has been bypassed prior to the transfer and a MLD
timer was configured additionally.
This timer is automatically bypassed, if not both sources are available (and stable) for transfer.
If, for example, a load test has been requested and cancelled again while the EPS signal is active, the
EPS relay will be reset automatically and the complete process will be terminated.
Elevator Pre Signal Elevator pre-signal ON / OFF

EN
Aufzugswarnsignal
DE
CL2 {0} {1} {2} OFF ..............No elevator pre-signal is issued, no elevator pre-signal timer starts
4490    and the LogicsManager flag 20.01 is not enabled.
ON ................The elevator pre-signal will be issued before any transfer and the
LogicsManager flag 20.01 will be enabled. The remaining elevator
pre-signal time is displayed.
Elevator pre-signal duration Elevator pre-signal duration 1 to 6500 s

EN
Warnsignal Dauer
DE
CL2 {0} {1} {2} The time configured here determines how long the elevator pre-signal is enabled
4491    before the transfer process will be continued. The signal will be disabled again if
the transfer process has been completed.
If this timer is running, the "Pre signal timer" message is displayed.

The following examples show the behavior of the elevator pre-signal for different applications.
Example 1 (elevator pre-signal disabled):
Figure 3-4: Elevator pre-signal - example 1
Example 2 (elevator pre-signal enabled):
Example 3 (elevator pre-signal and motor load disconnect enabled):
NOTE
If the transfer delay timers are configured to “0” seconds, they will automatically be bypassed and no
longer taken in account during a transfer.

Application: Motor Load Disconnect
The motor load disconnect flag (20.02) may be assigned to any output relay using the LogicsManager.
The motor load disconnect function is intended for sequential load shedding before a transfer and sequential load
addition after a transfer. This shall prevent the addition of the complete load at once.
The loads will be disconnected one after the other before a transfer. Then, the loads will be connected again in the
same order following the transfer.
In contrast to the elevator pre-signal, this signal will also be enabled in case of a preferred source failure. No
automatic or manual bypass of this signal will be performed.
Motor Load Disconnect Motor load disconnect ON / OFF

EN
Lastabwurf
DE
CL2 {0} {1} {2} OFF ............. No motor load disconnect signal is issued, no motor load disconnect
4550    signal timer starts and the LogicsManager flag 20.02 is not enabled.
It will be proceeded with the operation of the transfer switch.
ON ............... The motor load disconnect signal will be issued before any transfer
and the LogicsManager flag 20.02 will be enabled. The remaining
motor load disconnect signal time is displayed with the "Motor Load
Disc." message. After the motor load disconnect timer expires, the
transfer switch will be operated. The signal will be disabled again if
the transfer process has been completed.
Active direction Active direction S1->S2 / S1<-S2 / Both

EN
Aktive Richtung für Lastabwurf

DE
CL2 {0} {1} {2} This parameter configures the transfer direction into which the motor load
4553    disconnect signal is enabled.
S1->S2 ..........The motor load disconnect signal is only enabled in this transfer
direction. The LogicsManager flag 20.02 will not be enabled when
transferring from source 2 to source 1.
S1<-S2 ..........The motor load disconnect signal is only enabled in this transfer
direction. The LogicsManager flag 20.02 will not be enabled when
transferring from source 1 to source 2.
Both ..............The motor load disconnect signal is always enabled in both transfer
directions.
Disconnect time S1->S2 Disconnect time S1 -> S2 1 to 6500 s

EN
Lastabwurfszeit S1
DE
CL2 {0} {1} {2} This parameter configures the maximum duration of the motor disconnect signal
4551    in source 1 to source 2 transfer direction. After the timer has expired, the transfer
to source 2 will be performed
Disconnect time S2->S1 Disconnect time S2 -> S1 1 to 6500 s

EN
Lastabwurfszeit S2
DE
CL2 {0} {1} {2} This parameter configures the maximum duration of the motor disconnect signal
4552    in source 2 to source 1 transfer direction. After the timer has expired, the transfer
to source 1 will be performed

Application: Source Priority Selection
The two LogicsManager functions "Source Priority S1" and "Source Priority S2" are used to determine which
source is to be considered as preferred. The LogicsManager enables to use a discrete input (for example) to select
the preferred source externally using a source priority selector switch, which is usually on the operation panel.
In general, the preferred source is the one, which is permanently available. The NON-preferred source serves as
second source, which will be enabled if the preferred source fails or if a remote start signal is present.
Application examples:
• One utility supply, one generator (Util-Gen application)

If the utility (source 1) is defined as preferred source, the genset (source 2) will be started if the utility fails.
If the genset is defined as preferred source, the engine start signal is permanently enabled until the source
priority changes to the other source.
NOTE
Changing the priority while a load test (parameter 12640), remote peak shave (parameter 12630) or
interruptible power rates (parameter 12660) operation is enabled, results in a transfer to the selected
non-preferred source.
• Two utility supply networks (Util-Util application)

In this case, the customer might select one utility supply as preferred source. In case of a failure of the
preferred source, the load will be transferred to the other source.
• Two generators (Gen-Gen application)

In this case, the customer might select one generator as preferred source. In case of a failure of the preferred
source, the other genset will be started and the load will be transferred to the other source.
If the LogicsManager function "Source Priority S1" becomes TRUE, source 1 will be considered as preferred.
S1 Priority Source Priority S1 LogicsManager

EN
S1 Priorität
DE
If the LogicsManager function "Source Priority S2" becomes TRUE, source 2 will be considered as preferred.
S2 Priority Source Priority S2 LogicsManager

EN
S2 Priorität
DE
NOTE
If no source is preferred (both LogicsManager functions are FALSE or both LogicsManager functions
are TRUE), source 1 will be the preferred source.

Application example 1 (source priority = S1):
Transfer direction
upon loss of S1
S1 S2
preferred source non-preferred source
(emergency source)
Load
Figure 3-7: Source priority selection - S1 preferred
Application example 2 (source priority = S2):
Transfer direction
upon loss of S2
S1 S2
non-preferred source preferred source
(emergency source)
Load
Figure 3-8: Source priority selection - S2 preferred
If the preferred source is available, the load will automatically be connected to the preferred source (except when
a transfer to the non-preferred source is forced by a load test or remote peak shave, etc.).
It is also possible to change the source priority while the load is connected to the preferred or non-preferred
source.
If the load is connected to the non-preferred source and this non-preferred source is chosen as the preferred
source, the load remains connected to this source.
If the load is connected to the preferred source and this preferred source is chosen as the non-preferred source, the
load will be transferred to the "new" preferred source.

Extended Parallel Time
NOTE
This function is only effective if the transfer switch type (parameter 3424) is configured to "Closed" and
in-phase monitoring (parameter 4570) is enabled.
If a closed transition is performed, the overlap time of the make-before-break process, in which both sources are
parallel, is as configured in parameter 4577 (Max. overlap time). If this time is to be extended, a LogicsManager
function is available to keep the transition switch in overlap position. This may be achieved by a digital signal of
an external synchronization device for example.
If transfer switch type (parameter 3424) is configured as “Standard”, external sync. permission (ext. permit for
closed transition (parameter 4584) and closed transfer enable (parameter 4584)) does not apply.
If the LogicsManager function "Ext. para. time" becomes TRUE, the transfer switch will remain in overlap
position. If it becomes FALSE again, the source, from which the transfer has been initiated, will be disconnected
and the load will be supplied by the new source.
Ext. para. time Extended parallel time LogicsManager

EN
Erweiterte para. Zeit

DE
  
12860
A: "LogicsManager".
NOTE
As long as this function is TRUE, parameter 4577 (Max. overlap time) is not effective.
NOTE
If one source fails as long as this function is TRUE, the failed source will automatically be
disconnected.
WARNING
Both sources remain in overlap position as long as this function is TRUE.
Both sources are not decoupled if
• a load test (parameter 12640 on page 61) is disabled
• a remote peak shave request (parameter 12630 on page 39) is disabled
• an interruptible power rate request (parameter 12660 on page 40) is disabled
• the priority is changed
An overlap situation is only decoupled if
• the "Extended parallel time" function becomes FALSE again
• the phase angle during overlap position is > 2.0° or < -2.0°

The following example shows a typical transfer sequence from source 1 to source 2 with extended parallel time:
Initial situation:
S1 S2 Load is supplied by source 1
A transfer is initiated (e.g. by a load test):

S1 S2 As soon as source 2 is detected as stable and synchronicity is
achieved, the transfer switch is closed to source 2.
2
Extended parallel time is active:

S1 S2 As long as the LogicsManager function is TRUE, the transfer
switch remains in overlap position and load is supplied by both
3 sources.
Extended parallel time expires:

S1 S2 As soon as the LogicsManager function becomes FALSE, the
transfer switch opens from source 1.
4
Final situation:
S1 S2 Load is supplied by source 2

Load Shed
NOTE
Load shed is inactive as long as an "Extended parallel time" (parameter 12860) is enabled.
The load shed function bypasses the in-phase monitoring function. This can cause an asynchronous
transfer in case a standard transition switch is used.
The load shed function is intended to shed the load from the non-preferred source if a load shed signal is received
from a master controller (e.g. SCADA system) via a discrete input.
If a load shed signal is received from a master control, the DTSC disconnects the load from the non-preferred
source immediately. The following rules are valid for the load shed function:
• The load must be supplied by the non-preferred source. The load shed function can only trigger to disconnect
the load from the non-preferred source. If the load is supplied by the preferred source while a load shed
signal is triggered, the load will not be disconnected.
• Possible timers for pre-transfer signals like motor load disconnect or elevator pre-signal, which are enabled
prior to the transfer, will be ignored in case of a load shed request.
• If in-phase monitoring is enabled, this will be ignored in case of a load shed request.
• If the LogicsManager function "Inhibit XFR to S1" or "Inhibit XFR to S2" is TRUE and would prevent a
transfer to the preferred source, this function will be ignored on case of a standard transition switch. If a
delayed or closed transition switch is used, the switch will open to neutral position.
• If transfer switches are used, which may only be operated in case a measuring voltage is present, a transfer to
the preferred source may only be possible, when it is present. If only the non-preferred source is present, the
LogicsManager flag "Load shed" (20.11) will be enabled. This flag enables to close a load shed relay, which
connects the voltage of the non-preferred source to the preferred source side of the transfer switch to operate
it. If the neutral position (delayed / closed switch) or the preferred source position (standard switch) is
detected by the DTSC, the load shed signal will be reset again. Refer to Figure 3-9 and Figure 3-10 for more
detailed information.
If the LogicsManager function "Load shed" becomes TRUE, a load shed from the non-preferred source will be
performed.
Load shed Load shedding enabled LogicsManager

EN
Nicht prio. LS auf

DE
Table 3-1 defines the behavior in case of a load shed request when utilizing a standard transition switch
depending on the system conditions.
Load is connected to Pre-transfer In-phase Preferred source Behavior on load shed request
signals monitoring available
Non-preferred source Bypassed Bypassed Yes Immediate transfer to preferred source
Non-preferred source Bypassed Bypassed No LogicsManager flag "Load shed" (20.11) is set to transfer to the
preferred source
Preferred source N/A N/A Yes No action performed - load remains connected to preferred source
Table 3-1: Application - load shed with standard transition switch

Table 3-2 defines the behavior in case of a load shed request when utilizing a delayed or closed transition switch
depending on the system conditions.
Load is connected to Pre-transfer In-phase Preferred source Behavior on load shed request
signals monitoring available
Non-preferred source Bypassed Bypassed Yes Immediate transfer to preferred source
Non-preferred source Bypassed Bypassed No LogicsManager flag "Load shed" (20.11) is immediately set to
open to neutral position
If the preferred source restores while the switch is in neutral
position, a transfer to the preferred source is initiated without
waiting for the preferred source stable timer to expire
Preferred source N/A N/A Yes No action performed - load remains connected to preferred source
Table 3-2: Application - load shed with delayed or closed transition switch
Figure 3-9 shows how to wire a load shed relay for applications, which use a standard transition switch (S1 is the
preferred source and S2 is the non-preferred source with this application).
Load Shed Relay

(LM Flag 20.11)
Transfer
Switch
S1 Close S1 Circuit Close S2
S2
(Relay 6) Breaker (Relay 7)
Pair
Figure 3-9: Load shed relay wiring - standard transition switch
Figure 3-10 shows how to wire a load shed relay for applications, which use a delayed or closed transition switch
(S1 is the preferred source and S2 is the non-preferred source with this application).
Load Shed Relay

(LM Flag 20.11)
Open S2 Open S1
(Relay 9) (Relay 8)
Transfer
Switch
S1 Circuit S2
Breaker
Close S1 Pair Close S2
(Relay 6) (Relay 7)
Figure 3-10: Load shed relay wiring - delayed or closed transition switch
NOTE
The load shed relay must always be operated at the non-preferred source side with the power of the
non-preferred source.
If a load shed relay is used, preferred and non-preferred source priority must not be changed since this
would lead to a malfunction of the load shed function.

Service Disconnect
NOTE
Service disconnect is only active, if the "Transfer switch type" (parameter 3424) is configured to
"Delayed" or "Closed". The transfer switch type "Standard" does not support this feature.
This feature allows disconnecting the load from the source in case of a service operation.
If the LogicsManager function "Service Disconnect" becomes TRUE, the transfer switch opens to neutral
position and remains there until this function becomes FALSE again.
No automatic transfers to any source will be performed if the transfer switch has reached neutral position and this
LogicsManager function is enabled.
If the transfer switch is in neutral position and this LogicsManager function becomes FALSE again, the unit
changes to the "preferred source" (if available) automatically. If the "preferred source" is not available, it changes
to the "non-preferred source" automatically.
Service Disconnect Service disconnect enabled LogicsManager

EN
LS nach Neutral
DE
  
12890
A: "LogicsManager".

Breaker
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Breaker: Transfer Switch Type
Transfer switch type Transfer switch type Standard / Delayed / Closed

EN
Transfer Schalter Typ

DE
CL2 {0} {1} {2} This parameter configures the type of ATS switch, which is connected to the
3424    controller. The switch logic behavior depends on the setting configured here.
Standard ......An "open transition" switch is selected.
Delayed ........A "delayed transition" switch is selected.
Closed...........A "closed transition" switch is selected.
Standard Transfer Switch

If an open transition switch is used, "Standard" transfer switch type must be selected.
This switch type may only take on two states:
NOTE
Do not use “Standard” switch mode with breaker type transfer switches. Open commands are not
used! “Standard” mode is used with mechanically interlocked transfer type mechanisms only!
• Position 1: Connected to source 1

Transfer Switch
Source 1 Source 2
Load
Figure 3-11: Open transition switch - connected to source 1

Transfer Switch
Source 1 Source 2
Load
Figure 3-12: Open transition switch - connected to source 2
The following switch commands are enabled in this mode:

• LogicsManager flag (20.07) : Command: Close to Source 1
These signals may be configured to relay outputs to operate the ATS switch mechanics.
The following feedback signals are evaluated by the ATS controller for monitoring the actual switch position:
• Discrete input 1 (ATS breaker in Source 1 position) = signal designation: S1
In this mode Use Limit Switch Open Replies (3434) is disabled (setting “NO”).

The following additional features are recommended for this mode:

• In-phase monitor (refer to the In-Phase Monitor section)
• Motor load disconnect
Delayed Transfer Switch

If a delayed transition switch is used, "Delayed" transfer switch type must be selected.
This switch type may take on three states:

Transfer Switch
Source 1 Source 2
Load
Figure 3-13: Delayed transition switch - connected to source 1
• Position 2: Neutral
Transfer Switch
Source 1 Source 2
Load
Figure 3-14: Delayed transition switch - neutral position

Transfer Switch
Source 1 Source 2
Load
Figure 3-15: Delayed transition switch - connected to source 2

• LogicsManager flag (20.08) : Command: Open Source 1
The following feedback signals are evaluated by the ATS controller for monitoring the actual switch position if
Use Limit Switch Open Replies (3434) is “YES”:
• Discrete input 3 (ATS breaker in Source 1 OPEN position) = signal designation: S1O
If Use Limit Switch Open Replies (3434) is “NO” the evaluated feedback signals are reduces to S1 and S2.

• In-phase monitor (refer to the In-Phase Monitor section)
Closed Transfer Switch

If a closed transition switch is used, "Closed" transfer switch type must be selected.
This switch type may take on four states:

Transfer Switch
Source 1 Source 2
Load
Figure 3-16: Closed transition switch - connected to source 1
• Position 2: Neutral
Transfer Switch
Source 1 Source 2
Load
Figure 3-17: Closed transition switch - neutral position
• Position 3: Synchronized
Transfer Switch
Source 1 Source 2
Load
Figure 3-18: Closed transition switch - connected to source 1 and 2 (overlap position)

Transfer Switch
Source 1 Source 2
Load
Figure 3-19: Closed transition switch - connected to source 2

The following feedback signals are evaluated by the ATS controller for monitoring the actual switch position if
Use Limit Switch Open Replies (3434) is “YES”:

If Use Limit Switch Open Replies (3434) is “NO” the evaluated feedback signals are reduces to S1 and S2.

• In-phase monitor must be used (refer to the In-Phase Monitor section)

Use Limit Switch Open Replies
This function is used to define the limit switch reply signals, which are evaluated for determining the current
ATS switch position.
The following four signals are available for determining the ATS switch position:
NOTE
All reply signals, which are selected for determining the current ATS switch position must be
connected to the discrete inputs of the DTSC to ensure a correct evaluation of the switch replies.
These discrete inputs have an N.C. logic, i.e. the breaker is considered as "in position" if the respective
DI is de-energized.
Use Limit sw. OPEN replies Use limit switch open replies YES / NO
EN
Schalter RM OFFEN verwenden

DE
CL2 {0} {1} {2} This parameter may only be enabled (setting "YES") if parameter 3424 on
3434    page 52 is configured to "Delayed" or "Closed".
This parameter defines whether the limit switch open signals are also used to
determine the ATS switch position.
YES .............. The signals S1, S2, S1O, and S2O are used to determine the ATS
switch position.
This setting provides a higher system safety because the "Switch
Open" replies are also evaluated besides the "Switch Closed"
replies.
NO ................ Only the signals S1 and S2 are used to determine the ATS switch
position.
This setting does not use the DIs 3 and 4 for determining the ATS
switch position and makes them available for other functions.
Delayed Mode Active
This function is only effective if parameter 3424 (Transfer switch type) is configured to "Closed". If the
LogicsManager function "Delayed mode act." becomes TRUE, the transfer switch type will be set to "Delayed"
until function becomes false.
Delayed mode act. Enable delayed mode LogicsManager

EN
Verzög. modus akt.

DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 121 in
12850    Appendix A: "LogicsManager".

Transition Timers
The "Neutral Time S2 -> S1" parameter is only enabled, if "Delayed" or "Closed" is configured as "Transfer
switch type" (parameter 3424).
EN Neutral Time S2->S1 Neutral Time S2 -> S1 1 to 6500 s

Neutral Verweilzeit S2->S1
DE
CL2 {0} {1} {2} This parameter configures the residence time in neutral position when transferring
3426    the load in this transfer direction.
After this timer has expired, the transfer to source 1 will be performed.
If this timer is running, the "Neutral S1 -> S2" message is displayed.
The "Neutral Time S2 <- S1" parameter is only enabled, if "Delayed" or "Closed" is configured as "Transfer
switch type" (parameter 3424).
Neutral Time S1->S2 Neutral Time S1 -> S2 1 to 6500 s

EN
Neutral Verweilzeit S1->S2

DE
CL2 {0} {1} {2} This parameter configures the residence time in neutral position when transferring
3425    the load in this transfer direction.
After this timer has expired, the transfer to source 2 will be performed.
If this timer is running, the "Neutral S1 <- S2" message is displayed.
Limit switch reply timeout Limit switch reply timeout 0.1 to 99.9 s
EN
Zeitüberschreitung Rückmeld.
DE
CL2 {0} {1} {2} This parameter configures the maximum waiting time for a feedback signal from
  
3428
the ATS switch. If no reply is detected within the configured time, a new transition
attempt will be performed after the "Wait time until next XFR attempt"
(parameter 3429) has expired (refer to Figure 3-20 on page 58). If the "Max. of
transfer attempts" (parameter 3427) is exceeded, a switch failure will be issued.
If this timer is running, the Bypass softkey is not displayed. The display message
while the timer is running indicates that a reply is expected and depends on the
command issued:
• If source 1 is to be opened : "Wait S1 open"
• If source 2 is to be opened : "Wait S2 open"
• If source 1 is to be closed : "Wait S1 close"
• If source 2 is to be closed : "Wait S2 close"
Note: The operator coils may be damaged if this timer is configured too long (i.e.
the maximum time, for which the transition pulse may be enabled, must not be
exceeded).
NOTE
The limit switch reply timeout monitoring is only enabled if a transfer command (C2, C1, C2O, or C1O)
has been issued from the ATS controller.

EN
Wait time until next XFR Wait time until next transfer attempt 0.1 to 99.9 s
attempt
Wartezeit vor neuem Transfer This parameter configures the interval between an unsuccessful transfer attempt
DE
CL2 {0} {1} {2}

and the next transfer attempt.
3429   
This time allows the relay coil to cool down between the open/close signals.
Limit switch reply timeout Wait time until next XFR attempt
open/close
pulse
Figure 3-20: Breaker - transition pulse
Max. of transfer attempts Maxímum number of unsuccessful transfer attempts 0 to 10

EN
Max. Anzahl Fehlzuschaltungen

DE
CL2 {0} {1} {2} This parameter configures the maximum number of unsuccessful transfer
3427    attempts before a switch failure will be issued. The counter for the number of
unsuccessful transition attempts will be increased with the start of each waiting
time period (parameter 3429)
Note: If this parameter is configured to “0”, the DTSC-200 will issue infinite
transfer attempts, in case the corresponding switch reply signal is not being
recognized. No “Open failure” or “Close failure” alarm will be issued.

Triggering of the "Fail to close S1" failure

This failure is triggered if the following conditions are met:
• Source 1 is available
• The ATS controller has issued the C1 signal (LogicsManager flag (20.07)) to close to source 1
As soon as the C1 signal (command: close to source 1) is issued, the "Limit switch reply timeout" timer
(parameter 3428) starts to count and the period for monitoring whether the S1 reply (closed to source 1) is fed
back from the ATS switch to the controller starts. The C1 signal is enabled until the "Limit switch reply timeout"
timer has expired. Thus, this defines maximum permissible pulse duration for the transfer command. If the "Limit
switch reply timeout" timer has expired, the C1 signal will be disabled. If the "Wait time until next XFR attempt"
timer (parameter 3429) has expired, the C1 signal will be enabled again and the "Limit switch reply timeout"
timer is restarted. The fail to close S1 failure is issued after exceeding the configured maximum number of
attempts. The message "Fail to close S1" will be displayed and entered into the event logger.
If the reply from the ATS controller is detected while the "Limit switch reply timeout" timer is still counting, the
C1 signal will be disabled immediately since the transfer was successful. The message is not being displayed
anymore and the reply monitoring is terminated.
NOTE
Closing the ATS switch will be attempted until the maximum number of unsuccessful transition
attempts (parameter 3427) is reached. The failure will be issued after the last failed transfer attempt.
Triggering of the "Fail to close S2" failure

• The ATS controller has issued the C2 signal (LogicsManager flag (20.09)) to close to source 2
As soon as the C2 signal (command: close to source 2) is issued, the "Limit switch reply timeout" timer
(parameter 3428) starts to count and the period for monitoring whether the S2 reply (closed to source 2) is fed
back from the ATS switch to the controller starts. The C2 signal is enabled until the "Limit switch reply timeout"
timer has expired. Thus, this defines maximum permissible pulse duration for the transfer command. If the "Limit
switch reply timeout" timer has expired, the C2 signal will be disabled. If the "Wait time until next XFR attempt"
timer (parameter 3429) has expired, the C2 signal will be enabled again and the "Limit switch reply timeout"
timer is restarted. The fail to close S2 failure is issued after exceeding the configured maximum number of
attempts. The message "Fail to close S2" will be displayed and entered into the event logger.
C2 signal will be disabled immediately since the transfer was successful. The message is not being displayed
anymore and the reply monitoring is terminated.
NOTE
Closing the ATS switch will be attempted until the maximum number of unsuccessful transition
NOTE
If a closure failure occurs, the system always tries to close the second breaker to a good source.

Triggering of the "Fail to open S1" failure

• The ATS controller has issued the C1O signal (LogicsManager flag (20.08)) to open source 1
As soon as the C1O signal (command: open source 1) is issued, the "Limit switch reply timeout" timer
(parameter 3428) starts to count and the period for monitoring whether the S1O reply (source 1 is open) is fed
back from the ATS switch to the controller starts. The C1O signal is enabled until the "Limit switch reply
timeout" timer has expired. Thus, this defines maximum permissible pulse duration for the transfer command. If
the "Limit switch reply timeout" timer has expired, the C1O signal will be disabled. If the "Wait time until next
XFR attempt" timer (parameter 3429) has expired, the C1O signal will be enabled again and the "Limit switch
reply timeout" timer is re-started. If the timer expires again without detecting the S1O reply, the "Fail to open S1"
failure is issued. The message "Fail to open S1" will be displayed and entered into the event logger.
C1O signal will be disabled immediately since the transfer was successful. “Fail to open S1” will not be
displayed and reply monitoring is terminated.
NOTE
Opening the ATS switch will be attempted until the maximum number of unsuccessful transition
Triggering of the "Fail to open S2" failure

• The ATS controller has issued the C2O signal (LogicsManager flag (20.10)) to open source 2
As soon as the C2O signal (command: open source 2) is issued, the "Limit switch reply timeout" timer
(parameter 3428) starts to count and the period for monitoring whether the S2O reply (source 2 is open) is fed
back from the ATS switch to the controller starts. The C2O signal is enabled until the "Limit switch reply
timeout" timer has expired. Thus, this defines maximum permissible pulse duration for the transfer command. If
the "Limit switch reply timeout" timer has expired, the C2O signal will be disabled. If the "Wait time until next
XFR attempt" timer (parameter 3429) has expired, the C2O signal will be enabled again and the "Limit switch
reply timeout" timer is re-started. If the timer expires again without detecting the S2O reply, the "Fail to open S2"
failure is issued. The message "Fail to open S2" will be displayed and entered into the event logger.
C2O signal will be disabled immediately since the transfer was successful. “Fail to open S2” will not be
displayed and reply monitoring is terminated.
NOTE
Opening the ATS switch will be attempted until the maximum number of unsuccessful transition

Test Modes
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
There are two different types of system tests:
• Load Test
This is a test with load transfer. If a load test is requested, a failure of the preferred source will be simulated.
The non-preferred source will be started and load will be transferred to the non-preferred source.
This test serves to ensure that the complete system is ready for operation in case of a real failure of the
preferred source.
• No Load Test
This is an engine test. If a no load test is requested, only the non-preferred source will be started, but no load
transfer will be performed.
This test serves to ensure that the non-preferred source is starting and running properly.
NOTE
A "No Load Test" may only be performed if the non-preferred source is a generator.
If the LogicsManager function "Load Test" becomes TRUE (by energizing a DI for example), a load test will be
performed.
Load Test Load Test LogicsManager

EN
Lastprobe
DE
If the LogicsManager function "No Load Test" becomes TRUE (by energizing a DI for example), a no load test
will be performed.
No Load Test No Load Test LogicsManager

EN
Motor Test
DE
12650 ---   A: "LogicsManager".

Timer Exerciser
This feature allows configuring up to 12 independent times, at which either a load test or a no-load test is
performed. For this, 12 independent timers are available, to configure a recurring or single-time event, on which
either a load test or a no-load test can be started.
If such a configured time is reached, a LogicsManager command variable (20.20 for load test, and 20.21 for no-
load test) will be enabled for the configured duration, which again can be used to enable the LogicsManager
functions "Load Test" (parameter 12640) or "No Load Test" (parameter 12650).
A load test will only be performed if command variable 20.20 is enabled and the "Load Test" LogicsManager
function is configured accordingly.
Figure 3-21: Test modes - load test configured for timer exerciser
A no-load test will only be performed if command variable 20.21 is enabled and the "No Load Test"
LogicsManager function is configured accordingly.
Figure 3-22: Test modes - no-load test configured for timer exerciser
The timer exercisers 1 through 12 have identical parameters for configuring the exercise time. The parameters for
timer exerciser 1 are described in the following:
Exerciser Type Exerciser type Off / Daily / Weekly / 14-Day / 28-Day / 365-Day / One Event
EN
Testzyklus Art
DE
CL2 {0} {1} {2} Off ................ This exercise timer is disabled
6490    Daily............. A daily exercise will be performed at the configured time
Weekly ......... A weekly exercise will be performed at the configured time
14-Day ......... A biweekly (every 14 days) exercise will be performed at the
configured time starting with a configured date
28-Day ......... A four-weekly (every 28 days) exercise will be performed at the
365-Day........ A yearly (every 365 days) exercise will be performed at the
One Event .... A one-time exercise will be performed at the configured date and
time.

NOTE
Depending on the setting of the "Exerciser type" (parameter 6490), some of the following settings are
not important (i.e. if a daily exercise is configured, the exerciser day of week is not important, for
example).
Exerciser start time hour Exerciser start: hour 0 to 23 h

EN
Start Zeit
DE
CL2 {0} {1} {2} The hour of the exercise start time is configured here.
6491   
Exerciser start time minute Exerciser start: minute 0 to 59 min

EN
Start Zeit
DE
CL2 {0} {1} {2} The hour of the exercise start time is configured here.
6492   
Exerciser start day of week Exerciser start: weekday 1 to 7

EN
Start Wochentag
DE
CL2 {0} {1} {2} The weekday of a weekly exercise is configured here (1 = Monday, 7 = Sunday).
6493   
Exerciser start day Exerciser start: day 0 to 31

EN
Start Tag
DE
CL2 {0} {1} {2} The date of an exerciser start is configured here.
6494   
Exerciser start month Exerciser start: month 1 to 12

EN
Start Monat
DE
CL2 {0} {1} {2} The month of an exerciser start is configured here.
6495
Exerciser start year Exerciser start: year 0 to 99

EN
Start Jahr
DE
CL2 {0} {1} {2} The year of an exerciser start is configured here (08 corresponds with 2008).
6499
Exerciser duration hours Exerciser duration: hours 0 to 12 h

EN
Testdauer in Stunden
DE
CL2 {0} {1} {2} The exerciser duration in hours is configured here.
6496
Exerciser duration minutes Exerciser duration: minutes 0 to 59 min

EN
Testdauer in Minuten
DE
CL2 {0} {1} {2} The exerciser duration in minutes is configured here.
6497
Exerciser test type Exerciser test type Load / No Load

EN
Test Typ
DE
CL2 {0} {1} {2} Load ............ Command variable 20.20 will be enabled for a "Load Test" at the
6498    configured time
No Load ...... Command variable 20.21 will be enabled for a "No Load Test" at
the configured time
Parameter Ex. #1 IDs #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12

Exerciser Type 6490 6503 6516 6529 6542 6555 6568 6581 6594 6607 6620 6633
Exerciser start time hour 6491 6504 6517 6530 6543 6556 6569 6582 6595 6608 6621 6634
Exerciser start time minute 6492 6505 6518 6531 6544 6557 6570 6583 6596 6609 6622 6635
Exerciser start day of week 6493 6506 6519 6532 6545 6558 6571 6584 6597 6610 6623 6636
Exerciser start day 6494 6507 6520 6533 6546 6559 6572 6585 6598 6611 6624 6637
Exerciser start month 6495 6508 6521 6534 6547 6560 6573 6586 6599 6612 6625 6638
Exerciser start year 6499 6512 6525 6538 6551 6564 6577 6590 6603 6616 6629 6642
Exerciser duration hours 6496 6509 6522 6535 6548 6561 6574 6587 6600 6613 6626 6639
Exerciser duration minutes 6497 6510 6523 6536 6549 6562 6575 6588 6601 6614 6627 6640
Exerciser test type 6498 6511 6524 6537 6550 6563 6576 6589 6602 6615 6628 6641
Figure 3-23: Test modes - parameter IDs of the timer exercisers

Example 1: Daily Exerciser

The following configuration example shows how to configure "Exerciser 1" for a daily "No Load Test" at 14:30
(2:30 pm), which shall last 1 hours and 40 minutes.
ID Parameter Setting
6490 Exerciser Type Daily
6491 Exerciser start time hour 14 h
6492 Exerciser start time minute 30 min
6493 Exerciser start day of week N/A *
6494 Exerciser start day N/A *
6495 Exerciser start month N/A *
6499 Exerciser start year N/A *
6496 Exerciser duration hours 1h
6497 Exerciser duration minutes 40 min
6498 Exerciser test type No Load
Figure 3-24: Test modes - configuring exerciser 1 for a daily exercise
Example 2: Weekly Exerciser

The following configuration example shows how to configure "Exerciser 2" for a weekly "Load Test" every
Wednesday at 12:00 (noon), which shall last 0 hours and 30 minutes.
6503 Exerciser Type Weekly
6506 Exerciser start day of week 3 (Wednesday)
6507 Exerciser start day N/A *
6508 Exerciser start month N/A *
6512 Exerciser start year N/A *
6511 Exerciser test type Load
Figure 3-25: Test modes - configuring exerciser 2 for a weekly exercise
Example 3: 14-Day Exerciser

The following configuration example shows how to configure "Exerciser 3" for a "Load Test" every 14 days at
18:45 (6:45 pm), which shall last 2 hours and 45 minutes, starting on October 12, 2008. The next test would take
place on October 26, 2008, i.e. 14 days later.
6516 Exerciser Type 14-Day
6520 Exerciser start day 12
6521 Exerciser start month 10
6525 Exerciser start year 08
6524 Exerciser test type Load
Figure 3-26: Test modes - configuring exerciser 3 for a 14-day exercise
* N/A means that this setting is not important for the respective Exerciser Type

Example 4: One Event Exerciser

The following configuration example shows how to configure "Exerciser 4" for a "No Load Test" for only once
at 08:00 (8:00 am) on November 11, 2008, which shall last 0 hours and 15 minutes. If the test has started once, it
will not be repeated anymore. A new test must be configured by the operator.
6529 Exerciser Type One Event
6533 Exerciser start day 11
6534 Exerciser start month 11
6538 Exerciser start year 08
6537 Exerciser test type No Load
Figure 3-27: Test modes - configuring exerciser 4 for a one event exercise
* N/A means that this setting is not important for the respective Exerciser Type
If an exercise event is pending at the current date, this is indicated by the *E* in the start screen. This *E* is
displayed until the exercise event has expired. Moreover, the date of the next event is displayed in the
configuration screen of the respective event exerciser.
Figure 3-28: Test modes - display screen with pending exercise event
If a Load Test is currently running (the load is supplied by the non-preferred source), the remaining test time is
displayed as a count-down timer. The running test may be terminated using the Bypass button.
Figure 3-29: Test modes - display screen with running load test

Monitoring
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Monitoring: Alarm Acknowledgement
Time until horn reset Self acknowledgment of the centralized alarm (horn) 0 to 1,000 s
EN
Zeit Hupenreset
DE
CL2 {0} {1} {2} After each alarm occurs, the alarm LED flashes and the command variable 03.05
1756    (horn) is issued. After the delay time 'time until horn reset' has expired, the flashing
LED changes into a steady light and the command variable 03.05 (horn) is reset.
The alarm LED is illuminated continuously until the alarm has been acknowledged.
Note: If this parameter is configured to 0, the horn will remain active until it will be
acknowledged.
External acknowledge Protection: External acknowledgment of alarms LogicsManager

EN
Ext. Quittierung
DE
CL2 {0} {1} {2} It is possible to acknowledge all alarms simultaneously from remote, e.g. with a
12490    discrete input. The command variables of the LogicsManager have to become
TRUE twice.
 The first high signal into the discrete input acknowledges the command
variable 03.05 (horn). The second high signal acknowledges all inactive
alarm messages.
The ON-delay time is the minimum time the input signals have to be "1". The OFF-
delay time is the time how long the input conditions have to be "0" before the next
high signal is accepted.
The LogicsManager and its default settings are explained on page 121 in Appendix
A: "LogicsManager".
Monitoring: Limit Switch Monitoring
Limit switch monitoring Limit switch monitoring ON / OFF

EN
Rückmeldungswächter
DE
CL2 {0} {1} {2} Limit switch monitoring evaluates the ATS limit switch replies and checks them
3430    after limit switch failure delay time (3463) for plausibility with reference to the
operating state. If the replies are not plausible, the "Actual" and "Expected" replies
are displayed.
Meanwhile, the status of the breaker replies cannot be reset with the Reset button
and all further transfers are inhibited.
A table with the actual and expected replies may be found in the Operation Manual
37484.
ON ................The replies of the ATS limit switch are evaluated and compared with
the expected replies.
OFF ..............The replies of the ATS limit switch are not evaluated.
Note: Do not enable this monitoring function before the system is commissioned
and fully operational. Otherwise, missing reply signals would lead to a limit switch
failure, which blocks the control unit. This can only be solved by wiring the reply
signals correctly or disabling this function using ToolKit. The Limit switch failure
can be reset with Reset Limit Switch Failure (12891).

Limit switch failure delay time Limit switch failure delay time 0.00 to 10.00 s
EN
DE
Verzög. Depending on application switching process has an impact on the limit switch
CL2 {0} {1} {2}
monitoring signal (e.g. for EMC reasons). Limit Switch Failure Delay Time (3463)
3463
enables to eliminate known impact by waiting for stable signaling.
The preset value of 0.02 s is based on experience and valid for standard application
environment.
Note: The theoretically possible setting 0.00s would permanently trigger limit
switch monitoring (3430) – may be used for test.
Reset limit switch failure External acknowledgment of Limit switch failure LogicsManager
EN
DE
rücksetzen. It is possible to acknowledge Limit Switch Failure from remote (alternatively to the
CL2 {0} {1} {2}
Reset button on display), e.g. with a discrete input. The command variables of the
12891   
LogicsManager have to become TRUE.
The LogicsManager and its default settings are explained on page 121 in Appendix
A: "LogicsManager".
Monitoring: Source 1 Monitoring
Voltage monitoring S1 Voltage monitoring source 1 Ph - Ph / Phase - N

EN
Spg.-Überwachung S1
DE
CL2 {0} {1} {2} The unit can either monitor the wye voltages (phase-neutral: 3ph-4w, 1ph-3w and
1787    1ph-2w) or the delta voltages (phase-phase: 3ph-3w and 3ph-4w).
! WARNING:
This parameter influences the protective functions.
Ph - Ph ......... The phase-phase voltage will be measured and all subsequent

parameters concerning voltage monitoring "source 1" are referred to
this value (VL-L).
Phase - N ..... The phase-neutral voltage will be measured and all subsequent
this value (VL-N).
Monitoring: Source 1 Monitoring: Undervoltage

Voltage is monitored depending on parameter 1787 "Voltage monitoring S1".
S1 undervoltage restore Source 1 undervoltage restore 50.0 to 125.0 %

EN
S1 Unterspannung rücksetzen
DE
CL2 {0} {1} {2}  This value refers to the Rated voltage Source 1 (parameter 1774 on
4450    page 25).
This parameter configures the threshold, which must be exceeded to consider

source 1 as "OK" again.
S1 undervoltage fail Source 1 undervoltage fail 50.0 to 125.0 %

EN
S1 Unterspannung auslösen
DE
4451    page 25).
This parameter configures the threshold, which must be fallen below to consider
source 1 as "not OK".

Monitoring: Source 1 Monitoring: Underfrequency

Frequency is correctly measured using 1 to 3 phase inputs, with the voltage higher than 15 % of rated value.
However, with three phase inputs, the frequency measurement is very rapid and highly accurate.
S1 underfrequency monitoring Source 1 underfrequency monitoring ON / OFF

EN
S1 Unterfrequenz Wächter
DE
CL2 {0} {1} {2} This parameter configures, whether underfrequency monitoring for source 1 is
4452    performed.
OFF.............. No underfrequency monitoring is performed for source 1.
ON................ Underfrequency monitoring is performed for source 1.
S1 underfrequency restore Source 1 underfrequency restore 50.0 to 130.0 %

EN
S1 Unterfrequenz rücksetzen
DE
CL2 {0} {1} {2}  This value refers to the Rated system frequency (parameter 1750 on
4453    page 25).

source 1 as "OK" again..
S1 underfrequency fail Source 1 underfrequency fail 50.0 to 130.0 %

EN
S1 Unterfrequenz auslösen
DE
4454    page 25)
Monitoring: Source 1 Monitoring: Overvoltage

S1 overvoltage monitoring Source 1 overvoltage monitoring ON / OFF

EN
S1 Überspannung Wächter
DE
CL2 {0} {1} {2} This parameter configures, whether overvoltage monitoring for source 1 is
OFF.............. No overvoltage monitoring is performed for source 1.
ON................ Overvoltage monitoring is performed for source 1.
S1 overvoltage restore Source 1 overvoltage restore 50.0 to 125.0 %

EN
S1 Überspannung rücksetzen
DE
4456    page 25).
S1 overvoltage fail Source 1 overvoltage fail 50.0 to 125.0 %

EN
S1 Überspannung auslösen
DE
4457    page 25).


Monitoring: Source 1 Monitoring: Overfrequency

Frequency is correctly measured using 1 to 3 phase inputs, with the voltage higher than 15 % of rated value.
However, with three phase inputs, the frequency measurement is very rapid and highly accurate.
EN S1 overfrequency monitoring Source 1 overfrequency monitoring ON / OFF

S1 Überfrequenz Wächter
DE
CL2 {0} {1} {2} This parameter configures, whether overfrequency monitoring for source 1 is
OFF.............. No overfrequency monitoring is performed for source 1.
ON................ Overfrequency monitoring is performed for source 1.
S1 overfrequency restore Source 1 overfrequency restore 50.0 to 130.0 %

EN
S1 Überfrequenz rücksetzen
DE
4459    page 25).
S1 overfrequency fail Source 1 overfrequency fail 50.0 to 130.0 %

EN
S1 Überfrequenz auslösen
DE
4460    page 25).


Monitoring: Source 1 Monitoring: Voltage Imbalance

The voltage imbalance monitoring is practically used to detect defective fuses in certain phases. The voltage
imbalance monitoring measures voltage differences between the phases of source 1. The voltage is measured
three-phase. If the phase-to-phase voltage difference between the three phases exceeds the configured imbalance
limit the alarm will be issued.
S1 voltage imbalance monitoring Source 1 voltage imbalance monitoring ON / OFF

EN
S1 Asymmetrie Wächter
DE
CL2 {0} {1} {2} This parameter configures, whether voltage imbalance monitoring for source 1 is
OFF.............. No voltage imbalance monitoring is performed for source 1.
ON................ Voltage imbalance monitoring is performed for source 1.
S1 volt. Imbalance restore Source 1 voltage imbalance restore 0.5 to 99.9 %

EN
S1 Asymmetrie rücksetzen
DE
4462    page 25).
S1 volt. Imbalance fail Source 1 voltage imbalance fail 0.5 to 99.9 %

EN
S1 Asymmetrie auslösen
DE
4463    page 25).

Delay Source 1 voltage imbalance delay 0.02 to 99.99 s

EN
Verzögerung
DE
CL2 {0} {1} {2} If the monitored voltage imbalance of source 1 exceeds the threshold value for the
3914    delay time configured here, an alarm will be issued.

Monitoring: Source 1 Monitoring: Phase Rotation
CAUTION
Please ensure during installation that all voltages applied to this unit are wired correctly to both sides
of the circuit breaker. Failure to do so may result in damage to the control unit and/or generation
equipment due to closing the breaker asynchronous or with mismatched phase rotations and phase
rotation monitoring enabled at all connected components (engine, generator, breakers, cable, busbars,
etc.).
This function may block a connection of systems with mismatched phases systems only under the
following conditions:
• The voltages being measured are wired correctly with respect to the phase rotation at the
measuring points (i.e. the voltage transformer in front and behind the circuit breaker)
• The measuring voltages are wired without angular phase shift or interruption from the measuring
point to the control unit
• The measuring voltages are wired to the correct terminals of the control unit (i.e. L1 of the
generator is connected with the terminal of the control unit which is intended for the L1 of the
generator)
Correct phase rotation of the phase voltages ensures that damage will not occur during a transfer to either source
1 or source 2. The voltage phase rotation monitoring checks the phase rotation of the voltages and the configured
phase rotation to ensure they are identical. The directions of rotation are differentiated as "clockwise" and
"counter-clockwise". With a clockwise field the direction of rotation is "L1-L2-L3"; with a counter clockwise
field the direction of rotation is "L1-L3-L2". If the control is configured for a clockwise rotation and the voltages
into the unit are calculated as counterclockwise the alarm will be initiated.
A connection to any source can occur only if the incoming source has the correct phase sequence in relation to
the source that is connected to the load. No transfer will occur if the incoming source has an incorrect phase
sequence with this parameter enabled.
S1 phase rotation monitoring Source 1 phase rotation monitoring ON / OFF

EN
S1 Drehfeldüberwachung
DE
CL2 {0} {1} {2} This parameter configures, whether phase rotation monitoring for source 1 is
OFF.............. No phase rotation monitoring is performed for source 1.

ON................ Phase rotation monitoring is performed for source 1.
S1 phase rotation Source 1 phase rotation CW / CCW

EN
S1 Drehfeld
DE
CL2 {0} {1} {2} This parameter configures the phase rotation of the system. If a different phase
4563    rotation is detected at source 1, source 1 is considered as "not OK" and a transfer to
source 2 is initiated.
CW ............... The three-phase measured Source 1 voltage is rotating CW

(clockwise; that means the voltage rotates in direction L1-L2-L3;
standard setting).
CCW ............ The three-phase measured Source 1 voltage is rotating CCW
(counter-clockwise; that means the voltage rotates in direction L1-
L3-L2; standard setting).

Monitoring: Source 2 Monitoring
Voltage monitoring S2 Voltage monitoring source 2 Ph - Ph / Phase - N

EN
Spg.-Überwachung S2
DE
CL2 {0} {1} {2} The unit can either monitor the wye voltages (phase-neutral: 3ph-4w, 1ph-3w and
1786    1ph-2w) or the delta voltages (phase-phase: 3ph-3w and 3ph-4w).
! WARNING:
This parameter influences the protective functions.
Ph - Ph .........The phase-phase voltage will be measured and all subsequent

this value (VL-L).
Phase - N ......The phase-neutral voltage will be measured and all subsequent
this value (VL-N).
Monitoring: Source 2 Monitoring: Undervoltage

S2 undervoltage restore Source 2 undervoltage restore 50.0 to 125.0 %

EN
S2 Unterspannung rücksetzen
DE
  
4465
page 25).

S2 undervoltage fail Source 2 undervoltage fail 50.0 to 125.0 %

EN
S2 Unterspannung auslösen
DE
4466    page 25).

Monitoring: Source 2 Monitoring: Underfrequency

Frequency is correctly measured using 1 to 3 phase inputs, with the voltage higher than 15% of rated value.
However, with three phase inputs, the frequency measurement is very rapid, and highly accurate.
EN S2 underfrequency monitoring Source 2 underfrequency monitoring ON / OFF

S2 Unterfrequenz Wächter
DE
CL2 {0} {1} {2} This parameter configures, whether underfrequency monitoring for source 2 is
OFF .............. No underfrequency monitoring is performed for source 2.
ON ................ Underfrequency monitoring is performed for source 2.
S2 underfrequency restore Source 2 underfrequency restore 50.0 to 130.0 %

EN
S2 Unterfrequenz rücksetzen
DE
4468    page 25).

S2 underfrequency fail Source 2 underfrequency fail 50.0 to 130.0 %

EN
S2 Unterfrequenz auslösen
DE
4469    page 25)
Monitoring: Source 2 Monitoring: Overvoltage

S2 overvoltage monitoring Source 2 overvoltage monitoring ON / OFF

EN
S2 Überspannung Wächter
DE
CL2 {0} {1} {2} This parameter configures, whether overvoltage monitoring for source 2 is
OFF .............. No overvoltage monitoring is performed for source 2.
ON ................ Overvoltage monitoring is performed for source 2.
S2 overvoltage restore Source 2 overvoltage restore 50.0 to 125.0 %

EN
S2 Überspannung rücksetzen
DE
4471    page 25).
S2 overvoltage fail Source 2 overvoltage fail 50.0 to 125.0 %

EN
S2 Überspannung auslösen
DE
4472    page 25).


Monitoring: Source 2 Monitoring: Overfrequency

Frequency is correctly measured using 1 to 3 phase inputs, with the voltage higher than 15% of rated value.
However, with three phase inputs, the frequency measurement is very rapid, and highly accurate.
S2 overfrequency monitoring Source 2 overfrequency monitoring ON / OFF

EN
S2 Überfrequenz Wächter
DE
CL2 {0} {1} {2} This parameter configures, whether overfrequency monitoring for source 2 is
OFF ..............No overfrequency monitoring is performed for source 2.
ON ................Overfrequency monitoring is performed for source 2.
S2 overfrequency restore Source 2 overfrequency restore 50.0 to 130.0 %

EN
S2 Überfrequenz rücksetzen
DE
4474    page 25).
S2 overfrequency fail Source 2 overfrequency fail 50.0 to 130.0 %

EN
S2 Überfrequenz auslösen
DE
4475    page 25).


Monitoring: Source 2 Monitoring: Voltage Imbalance

The voltage imbalance monitoring is practically used to detect defective fuses in certain phases. The voltage
imbalance monitoring measures voltage differences between the phases of source 2. The voltage is measured
three-phase. If the phase-to-phase voltage difference between the three phases exceeds the configured imbalance
limit the alarm will be issued.
S2 voltage imbalance monitoring Source 2 voltage imbalance monitoring ON / OFF

EN
S2 Asymmetrie Wächter
DE
CL2 {0} {1} {2} This parameter configures, whether voltage imbalance monitoring for source 1 is
OFF ..............No voltage imbalance monitoring is performed for source 1.
ON ................Voltage imbalance monitoring is performed for source 1.
S2 volt. Imbalance restore Source 2 voltage imbalance restore 0.5 to 99.9 %

EN
S2 Asymmetrie rücksetzen
DE
4477    page 25).
S2 volt. Imbalance fail Source 2 voltage imbalance fail 0.5 to 99.9 %

EN
S2 Asymmetrie auslösen
DE
4478    page 25).

Delay Source 2 voltage imbalance delay 0.02 to 99.99 s

EN
Verzögerung
DE
CL2 {0} {1} {2} If the monitored voltage imbalance of source 2 exceeds the threshold value for the
3904    delay time configured here, an alarm will be issued.

Monitoring: Source 2 Monitoring: Phase Rotation
CAUTION
Please ensure during installation that all voltages applied to this unit are wired correctly to both sides
of the circuit breaker. Failure to do so may result in damage to the control unit and/or generation
equipment due to closing the breaker asynchronous or with mismatched phase rotations and phase
rotation monitoring enabled at all connected components (engine, generator, breakers, cable, busbars,
etc.).
This function may block a connection of systems with mismatched phases systems only under the
following conditions:
• The voltages being measured are wired correctly with respect to the phase rotation at the
measuring points (i.e. the voltage transformer in front and behind the circuit breaker)
• The measuring voltages are wired without angular phase shift or interruption from the measuring
point to the control unit
• The measuring voltages are wired to the correct terminals of the control unit (i.e. L1 of the
generator is connected with the terminal of the control unit which is intended for the L1 of the
generator)
Correct phase rotation of the phase voltages ensures that damage will not occur during a transfer to either source
1 or source 2. The voltage phase rotation monitoring checks the phase rotation of the voltages and the configured
phase rotation to ensure they are identical. The directions of rotation are differentiated as "clockwise" and
"counter-clockwise". With a clockwise field the direction of rotation is "L1-L2-L3"; with a counter clockwise
field the direction of rotation is "L1-L3-L2". If the control is configured for a clockwise rotation and the voltages
into the unit are calculated as counterclockwise the alarm will be initiated.
A connection to any source can occur only if the incoming source has the correct phase sequence in relation to
the source that is connected to the load. No transfer will occur if the incoming source has an incorrect phase
sequence with this parameter enabled.
S2 phase rotation monitoring Source 2 phase rotation monitoring ON / OFF

EN
S2 Drehfeldüberwachung
DE
CL2 {0} {1} {2} This parameter configures, whether phase rotation monitoring for source 2 is
OFF ..............No phase rotation monitoring is performed for source 2.

ON ................Phase rotation monitoring is performed for source 2.
S2 phase rotation Source 2 phase rotation CW / CCW

EN
S2 Drehfeld
DE
CL2 {0} {1} {2} This parameter configures the phase rotation of the system. If a different phase
4567    rotation is detected at source 2, source 2 is considered as "not OK" and a transfer to
source 1 is initiated.
CW ...............The three-phase measured Source 2 voltage is rotating CW

(clockwise; that means the voltage rotates in direction L1-L2-L3;
standard setting).
CCW ............The three-phase measured Source 2 voltage is rotating CCW
(counter-clockwise; that means the voltage rotates in direction L1-
L3-L2; standard setting).

Monitoring: In-Phase Monitoring (Synch Check)
The in-phase monitoring function is used to determine whether the phase angles of the preferred source and the
non-preferred source are in phase, i.e. whether the relative phase difference of the two sources is within specified
limits.
Whenever one power source fails, the control follows the programmed transition operation sequence. If in-phase
monitoring is enabled and both sources are available as determined by the "restore value" levels, the control shall
follow the in-phase monitoring operation sequence.
In-phase Monitoring may be used to improve the transfer with open transition switches. An open (standard)
transition transfer switch is the most simple and commonly used ATS. It may only take on two positions,
connected with source 1, or connected with source 2. If it transfers a load, this will be performed according to the
break-before-make process, i.e. the load will be disconnected from the previous source before it will be
connected with the next source. This results a dead time of approximately 160 ms (depending on the ATS) during
which the load is not connected to a source. Most of the load consumers are not affected by this dead time in the
transfer phase (lamps may only flicker, etc.), but some appliances may be effected seriously, like computers and
motor loads, etc. This could lead up data loss or equipment damage. The problem is that the consumers behave
like generators during this dead time and supply power. While some consumers are running out when changing to
the other source, very high current may flow between generator and load because the phase angles between the
two systems are not synchronous.
This high equalizing current may be minimized by two means:
• Using a transfer switch with neutral position

If delayed transition is used, the residence time in neutral position can be extended long enough before
transfer for the voltages at the load to decay.
• Using inphase monitoring
Inphase monitoring checks the phase angle between source 1 and source 2 prior to a transfer and enables the
transfer signal only if the phase angle has fallen below a configured threshold. Moreover, the unit calculates
the leading angle for the closing commands by entering the "Switch reaction time" to enable a transfer with
almost 0° phase shift. This ensures a nearly synchronous transfer to the other source and reduces the
equalizing current to a minimum. Compared with the neutral position of a delayed transition switch, the
advantage is that the load must not be shut down completely prior to a transfer.
Inphase monitoring may be used with open, delayed, and closed transition switches. As mentioned above, high
equalizing current after a transfer may be minimized when utilizing inphase monitoring. However, the behavior
of the ATS in case of a failed inphase transition must be considered. This may happen if the generator is
equipped with a poorly adjusted frequency controller. Then, it may happen that it is not possible to achieve
synchronicity. But the load must be transferred to the other source in any case.
NOTE
Refer to parameter 4582 "Outcome on in-phase timeout" for the ATS behavior in case of a failed
inphase transition.
Acceptable Unacceptable Acceptable

switch transfer switch transfer switch transfer
Source 2 power Source 2 power Source 2 power
Source 1 power
Phase window Time delay in neutral

Source 1 power
Figure 3-30: Inphase monitoring

Monitoring: In-phase Monitoring: Parameters
In-Phase monitor In-phase monitoring ON / OFF

EN
Synchrocheck
DE
CL2 {0} {1} {2} This parameter configures, whether in-phase monitoring is performed.
  
4570
OFF ..............No in-phase monitoring is performed prior to a transfer.
ON ................In-phase monitoring is performed prior to a transfer. If the phase
angle between both systems is within the permissible limits, the
NOTE
If in-phase monitoring is enabled and the measurement principle for source 1 (parameter 1862) is
configured as "1Ph 2W", the measurement principle for source 2 (parameter 1861) must also be
Monitoring: Load transfer between two utility sources with special (phase angle) conditions
NOTE
To transfer the load between two utility sources for a self adjusted phase angle range is valid for
application mode UTIL-UTIL only.
Monitoring: Connect synchronous mains: Parameters
Connect synchronous mains Connect synchronous mains ON / OFF

EN
Synchrones Netz anschließen

DE
CL2 {0} {1} {2} This parameter configures, whether special in-phase monitoring is performed if the
8820  --- --- phase angle between both mains voltages is in a defined range. This range is
defined from zero to the value of parameter 8821 Max. phase angle (see below).
OFF ..............In-phase monitoring is performed as configured with parameter 4570
In-phase monitoring (see above).
ON ................Special in-phase monitoring is performed prior to a transfer. If the
phase angle between both systems is within the adjusted limits, the
Monitoring: Max. phase angle: Parameters
Max. phase angle Maximum phase angle 2° to 20°

EN
Max. Phasenwinkel
DE
CL2 {0} {1} {2} This parameter configures the maximum admissible phase angle between both
8821  --- --- voltage systems in case of connecting synchronous mains.
The monitored range starts from 0 (zero) and goes through the value set with this
parameter.
Example:
If the Max. phase angle is set to 10,
the covered range for the phase angle is 0° … 10°.

In-phase check for DLY trans. Inphase check for DLY trans ON / OFF
EN
Sync bei verzögertem Transfer
DE
CL2 {0} {1} {2} Note: This parameter is used only if “Delayed” transition mode is selected.
4585   
OFF.............. If parameter “Transfer switch type” is set to “Delayed”, and this
parameter is “Off”, then no In-Phase check will be performed even if
parameter “In-phase monitor” is configured to “On”. The system will
always transfer using timed neutral position in account during each
transfer.
ON................ If the “Transfer switch type” is set to “Delayed”, and this parameter
is set to “On”, then the In-Phase monitoring is also active for a
delayed transition transfer. If transferring between two live sources (
S1 & S2 ) In-Phase check will always be performed and the
“Neutral” position timer will be automatically bypassed.
Application example:
1.................. Parameter “Transfer switch type” is configured to “Closed”

2.................. Parameter “In-phase monitor” is configured to “On”
3. LogicsManager “Delayed mode act.” is used, to switch between
operating modes “Delayed and Closed” transition via an externally
mounted Keyswitch.
Note: During commissioning it can happen that the utility company does not allow
closed transition transfers between two sources unless they have permitted the ATS
system owner to do it. In that case a key-switch can be installed to the ATS cabinet
to toggle the operating modes between “Closed” and “Delayed” transition. If set to
“Closed” transition mode, the DTSC-200 will always perform in-phase transfers
between the two sources. If the customer switches the transition mode to “Delayed”
(via the external keyswitch) and he does not want the “In-Phase monitor” to be
active, the parameter “In-Phase check for DLY transfer” shall be set to “Off”. This
ensures that “In-phase monitoring” is definitely deactivated for delayed transition
transfers even if parameter “In-phase monitor” is configured to “On”. If the
customer switches the Keyswitch back to “closed” transition mode, then the system
will perform closed transition transfers.

Voltage window Voltage window for synchronization 0.50 to 20.00 %

EN
Spannungsdifferenz
DE
CL2 {0} {1} {2}  This value refers to the Rated voltage Source 1/2 (parameters 1774/1772 on
4571    page 25).
This parameter configures the maximum permissible voltage difference in each of

the three phases. The voltage differences in all three phases (VL1 (Source 1) - VL1 (Source
2) / VL2 (Source 1) - VL2 (Source 2) / VL3 (Source 1) - VL3 (Source 2)) must be within the limit
configured here to be able to synchronize.
If the voltage difference in at least one phase exceeds this limit, the synchronization
will not be enabled.
Positive frequency window Positive frequency window for synchronization 0.02 to 0.49 Hz
EN
Maximaler Schlupf
DE
CL2 {0} {1} {2} This parameter configures the maximum permissible positive frequency difference
4572    between source 2 and source 1 (Δf = S2-S1).
If the frequency difference is not within the limits configured here, the
synchronization will not be enabled because the frequency difference of the source
to be connected to is too high.
Negative frequency window Negative frequency window for synchronization -0.02 to -0.49 Hz
EN
Maximaler Schlupf
DE
CL2 {0} {1} {2} This parameter configures the minimum permissible negative frequency difference
4573    between source 2 and source 1 (Δf = S2-S1).
If the frequency difference is not within the limits configured here, the
synchronization will not be enabled because the frequency difference of the source
to be connected to is too low.

Maximum Overlap Time
NOTE
This function is only effective if the transfer switch type (parameter 3424) is configured to "Closed" and
in-phase monitoring (parameter 4570) is enabled.
NOTE
If the LogicsManager function "Extended parallel time" (parameter 12860) is TRUE, the maximum
overlap time is not effective.
If a closed transition is performed, the overlap time of the make-before-break process, in which both sources are
parallel, is less than 100 ms. If this time is to be extended, an overlap timer is available to keep the transition
switch in overlap position for a configured time. The timer starts as soon as the transition switch is in overlap
position. The source, from which the transfer has been initiated, will be disconnected and the load will be
supplied by the new source as soon as this timer has expired.
Max. overlap time Maximum overlap time 0.1 to 9.99 s

EN
Max. Synchronzeit
DE
CL2 {0} {1} {2} 0.11 - 9.99 .... The time for which the transfer switch shall remain in overlap
4577    position is configured here.
0.10............... Special case: With this setting Overlap times below 100 ms are
possible if transfer switch is fast enough.
NOTE
If one source fails before this timer expires, the failed source will automatically be disconnected.
The following example shows a typical transfer sequence from source 1 to source 2 with overlap timer:
Initial situation:
S1 S2 Load is supplied by source 1.
A transfer is initiated (e.g. by a load test):

S1 S2 As soon as source 2 is detected as stable and synchronicity is
achieved, the transfer switch is closed to source 2.
2
Overlap timer is active:

S1 S2 The transfer switch remains in overlap position as long as the
overlap timer has not expired and load is supplied by both
3 sources.
Maximum overlap time expires:

S1 S2 As soon as the configured maximum overlap time has expired,
the transfer switch opens from source 1.
4
Final situation:
S1 S2 Load is supplied by source 2.

Switch Reaction Time Configuration
Open trans. Switch reac. Time Open transition switch reaction time 15 to 300 ms
EN
Schaltzeit bei nicht Überlapp.

DE
CL2 {0} {1} {2} The time, which is required by the switch in open transition mode to open from
  
4578
one source and close to the other source, is configured here.
This time is required for calculating the lead angle for inphase transfers.
Closed trans. Switch reac. Time Closed transition switch reaction time 15 to 300 ms
EN
Schalterzeit bei Überlapp.

DE
CL2 {0} {1} {2} The time, which is required by the switch in closed transition mode to close to the
4583    other source to parallel, is configured here.
This time is required for calculating the lead angle for inphase transfers.
t Transfer
Figure 3-31: Switch reaction time
Vector Group Angle Adjustment
WARNING
It is critical that the following parameter is configured correctly to prevent incorrect synchronization
settings. This parameter cannot compensate for incorrect wiring of the system!
Vector group angle adjustment Vector group angle adjustment -180° to 180°
EN
Schaltgruppe Winkel Anpassung

DE
CL2 {0} {1} {2} This parameter compensates phase angle deviations, which can be caused by
  
4581
transformers (e.g. a delta to wye transformer) located within the electrical system.
Ensure the following parameters are configured correctly to prevent erroneous
synchronization settings. Incorrect wiring of the system cannot be compensated
for with this parameter.
Please act as follows: If a transformer is not located between source S1 and S2 or

if the transformer has a vector group without a phase angle deviation, then a
phase angle deviation of 0° should be configured in this parameter.
NOTE: Further information can be found in chapter “Commissioning Note” on

the next page.
WARNING: Ensure this parameter is configured correctly to prevent erroneous

synchronization settings. Incorrect wiring of the system cannot be compensated
for with this parameter.

Outcome on Inphase Timeout
In-phase timeout after Inphase timeout after 0 to 6,500 s
EN
Synchr. Zeitüberschr.
DE
CL2 {0} {1} {2} This parameter configures the maximum time for attempting to detect
  
4576
synchronization. This timer starts to count as soon as inphase monitoring is enabled
prior to a transfer. If synchronicity is detected between the two sources, the transfer
command will be issued. The timer will be bypassed.
Outcome on In-phase timeout Outcome on inphase timeout Abort / Delayed

EN
Aktion bei Sync. Zeitüberschr.

DE
CL2 {0} {1} {2} This parameter determines the behavior of the unit after unsuccessful
4582    synchronization using the following 2 options:
Abort ........... The transfer will be aborted.

Delayed ........ A delayed transition will be performed.
Example:
If a load test is requested and inphase monitoring is enabled (parameter 4570 is
configured to "ON"), the inphase timeout timer (parameter 4576) starts prior to a
transfer and the unit attempts to detect synchronization between the two sources. If
no synchronization can be detected before the timer expires (because of a
misadjusted voltage or speed controller at the engine for example), the behavior
configured here determines the further transfer proceeding.
If Abort is configured here, the complete transfer request will be aborted. This
means that all remote start requests (like load test) will be ignored if they are still
present and the system will remain on the available source.
If Delayed is configured here, a delayed transition will be performed. This means

that the switch changes to neutral position for a configured time to ramp down
connected motor loads before it changes to the other source. This is important for
de-energized motors to ramp down, because, for a short time, they act as
generators.
Note: This function may only be used, if "Delayed" or "Closed" is configured as

"Transfer switch type" (parameter 3424). If "Standard" is configured as "Transfer
switch type" (parameter 3424) and "Outcome on In-phase timeout" is configured to
"Delayed", the unit behaves as if "Abort" would have been configured here.

External sync. permission

This parameter allows to externally control the in-phase monitoring function. “Closed transfer enable” (parameter
12880) LogicsManager statement must be made logically “TRUE” for operation of parameter 4584.
Examples external sync permission:
Scenario 1 ..... Elevator pre-transfer signal is “Disabled”

Scenario 2 ..... Elevator pre-transfer signal is “Enabled”


Scenario 3 ..... Elevator pre-transfer signal is “Enabled”

Motor load disconnect signal is “Enabled”
Ext. permit for cld. trans. Ext. permit for cld. trans. ON / OFF
EN
Ext. Freigabe für LS überlapp.

DE
CL2 {0} {1} {2}  This value refers to in-phase monitoring (parameter 4570). This parameter
4584    must be configured to “On”.
ON ............... In-Phase monitoring is initiated via LogicsMananger

(parameter 12880).
OFF ............. In-Phase monitoring is initiated by the DTSC-200.
Enable closed transition Enable closed transition LogicsManager

EN
Freig. LS Überlappung
DE
Note:
This parameter is only visible if “Ext. permit for cld. trans.” (parameter 4584 is
configured to “On”.

Monitoring: Overcurrent
Current is monitored depending on the parameters 1860 "S2 Load current measuring" and 1863 "S1 Load current
measuring". Only the current of the source, which is connected to the load, is measured, because the CT is
located at the load connection. The load overcurrent alarm contains three limits and can be setup as a step definite
time overcurrent alarm as illustrated in the figure below. Monitoring of the maximum phase current is performed
in three steps. Every step can be provided with a delay time independent of the other steps.
If this protective function is triggered, the alarm list indicates "Overcurrent 1", "Overcurrent 2", or
"Overcurrent 3".
IRated [%]
Lim.1 < Lim.2 < Lim.3
t[Lim.1] > t[Lim.2] > t[Lim.3]
Lim.3 [%/IRated]
Protected Area
Lim.2 [%/IRated]
Lim.1 [%/IRated]
t[Lim.3] t[Lim.2] t[Lim.1] t [s]

Figure 3-32: Monitoring - load time-overcurrent
Parameter table Level Text Setting range Standard value

Overcurrent (the hysteresis is 1 % of the rated value)
The parameters represented in Level 1 Monitoring ON / OFF ON
this table are specified in the Limit 50.0 to 300.0 % 110.0 %
following, whereas the Delay 0.02 to 99.99 s 30.00 s
description is identical for all Self-acknowledgment YES / NO NO
levels; the levels may only Level 2 Monitoring ON / OFF ON
differ in their setting ranges. Limit 50.0 to 300.0 % 150.0 %
Delay 0.02 to 99.99 s 1.00 s
Self-acknowledgment YES / NO NO
Level 3 Monitoring ON / OFF ON
Limit 50.0 to 300.0 % 250.0 %
Delay 0.02 to 99.99 s 0.40 s
Table 3-3: Monitoring - standard values - load time-overcurrent

Monitoring Load overcurrent, TOC: Monitoring (Level 1/Level 2/Level 3) ON / OFF
EN
Überwachung
DE
CL2 {0} {1} {2} ON................ Overcurrent monitoring is carried out according to the following
2200    parameters. Monitoring is performed at three levels. All three values
2206
2212 may be configured independent from each other (prerequisite:
Level 1 < Level 2 < Level 3).
OFF.............. Monitoring is disabled for level 1, level 2, and/or level 3.
Limit Load overcurrent, TOC: Threshold value (Level 1/Level 2/Level 3) 50.0 to 300.0 %
EN
Limit
DE
CL2 {0} {1} {2}  This value refers to the Rated current (parameter 1754, see page 25).
2204   
2210
2216 The percentage values that are to be monitored for each threshold limit are defined
here. If this value is reached or exceeded for at least the delay time without
interruption, an alarm is issued.
Delay Load overcurrent, TOC: Delay (Level 1/Level 2/Level 3) 0.02 to 99.99 s
EN
Verzögerung
DE
CL2 {0} {1} {2} If the monitored load current exceeds the threshold value for the delay time
2205    configured here, an alarm will be issued. If the monitored load current falls below
2211
2217 the threshold (minus the hysteresis) before the delay expires the time will be reset.
Self acknowledge Load overcurrent, TOC: Self acknowledgment (Level 1/Level 2/Level 3) ON / OFF
EN
Selbstquittierend
DE
CL2 {0} {1} {2} YES .............. The control automatically clears the alarm if it is no longer valid.
  
2202
2208
NO................ An automatic reset of the alarm does not occur. The reset occurs
2214 manually by pressing the appropriate buttons, by activating the
LogicsManager output "External acknowledgement" via an discrete
input, or via an interface.

Monitoring: Overload
Power is monitored depending on the parameters 1861 "S2 voltage measuring", 1862 "S1 voltage measuring",
1860 "S2 Load current measuring" and 1863 "S1 Load current measuring". Only the power of the source, which
is connected to the load, is measured, because the CT is located at the load connection. If the real power is above
the configured limit an alarm will be issued.
If this protective function is triggered, the alarm list indicates "Overload 1" or "Overload 2".
[%] delay level 2 delay level 2
Limit level 2
Limit level P2Hysteresis
Limit level 1
Limit level 1Hysteresis
Rated value
[100 %]
delay level 1 delay level 1 delay level 1 delay level 1
Alarm level 1
(Alarm limit 1)
Alarm level 2
(Alarm limit 2)
Figure 3-33: Monitoring - overload

Overload (the hysteresis is 1 % of the rated value)
this table are specified in the Limit 50.0 to 300.0 % 110.0 %
description is identical for all Self-acknowledgment YES / NO NO
levels; the levels may only Level 2 Monitoring ON / OFF ON
differ in their setting ranges. Limit 50.0 to 300.0 % 120.0 %
Delay 0.02 to 99.99 s 0.10 s
Table 3-4: Monitoring - standard values - overload

Monitoring Overload: Monitoring (Level 1/Level 2) ON / OFF
EN
Überwachung
DE
CL2 {0} {1} {2} ON................ Overload monitoring is carried out according to the following
2300    parameters. Monitoring is performed at two levels. Both values may
2306
be configured independent from each other (prerequisite: limit 1
< limit 2).
OFF.............. Monitoring is disabled for level 1 and/or level 2.
Limit Overload: Threshold value (Level 1/Level 2) 50.0 to 300.00 %

EN
Limit
DE
CL2 {0} {1} {2}  This value refers to the Rated active power (parameter 1752, see page 25).
2304   
2310
The percentage values that are to be monitored for each threshold limit are defined
here. If this value is reached or exceeded for at least the delay time without
Delay Overload: Delayed (Level 1/Level 2) 0.02 to 99.99 s

EN
Verzögerung
DE
CL2 {0} {1} {2} If the monitored load exceeds the threshold value for the delay time configured
2305    here, an alarm will be issued. If the monitored load falls below the threshold (minus
2311
the hysteresis) before the delay expires the time will be reset.
Self acknowledge Overload: Self acknowledgment (Level 1/Level 2) YES / NO

EN
Selbstquittierend
DE
  
2302
2308
NO................ An automatic reset of the alarm does not occur. The reset occurs
manually by pressing the appropriate buttons, by activating the

Monitoring: Engine, Start Failure Source 1

If this protective function is triggered, the alarm list indicates "Start Fail S1".
S1 start fail delay time Source 1 start fail: delay time 1 to 6500 s
EN
S1 Startfehler Zeit
DE
CL2 {0} {1} {2} If the "S1 start delay" timer has expired, the engine start signal will be issued. If the
3341 --- --- 
"engine start" relay de-energizes, "Source 1 start fail delay" timer starts to count.
Now, the controller expects the engine to start within the time configured here. If
this time will be exceeded, a "Start Fail S1" alarm will be issued.
If this timer is running, the "Starting S1" message is displayed.
This parameter is only visible, if the application mode (parameter 4148) is

configured to "Gen-Gen".
Monitoring: Engine, Start Failure Source 2

If this protective function is triggered, the alarm list indicates "Start Fail S2".
S2 start fail delay time Source 2 start fail: delay time 1 to 6500 s
EN
S2 Startfehler Zeit
DE
CL2 {0} {1} {2} If the "S2 start delay" timer has expired, the engine start signal will be issued. If the
3331    "engine start" relay de-energizes, "Source 2 start fail delay" timer starts to count.
Now, the controller expects the engine to start within the time configured here. If
this time will be exceeded, a "Start Fail S2" alarm will be issued.
If this timer is running, the "Starting S2" message is displayed.

Monitoring: Battery, Overvoltage

There are two battery overvoltage alarm levels available in the control. Both alarms are definite time alarms and
are illustrated in the below figure. The figure diagrams a frequency trend and the associated pickup times and
length of the alarms. It should be noted that this figure illustrates a level 1 alarm that is self-acknowledged.
Monitoring of the voltage is done in two steps.
If this protective function is triggered, the alarm list indicates "Batt.overvolt.1" or
"Batt.overvolt.2".
[%] delay level 2 delay level 2
Limit level 2
Limit level P2Hysteresis
Limit level 1
Rated value
[100 %]
delay level 1 delay level 1 delay level 1 delay level 1
Alarm level 1
(Alarm limit 1)
Alarm level 2
(Alarm limit 2)
Figure 3-34: Monitoring - battery overvoltage

Battery overvoltage (the hysteresis is 0,7 % of the rated value.)
this table are specified in the Limit 8.0 to 42.0 V 32.0 V
description is identical for all
levels; the levels may only Self-acknowledgment YES / NO NO
differ in their setting ranges. Level 2 Monitoring ON / OFF OFF
Limit 8.0 to 42.0 V 35.0 V
Delay 0.02 to 99.99 s 1.00 s
Table 3-5: Monitoring - standard values - battery overvoltage

EN
Monitoring Battery overvoltage: Monitoring (Level 1/Level 2) ON / OFF
Überwachung
DE
CL2 {0} {1} {2} ON ................Overvoltage monitoring of the battery voltage is carried out
3450    according to the following parameters.
3456
OFF ..............Monitoring is disabled for level 1 and/or level 2.
Limit Battery overvoltage: Threshold value (Level 1/Level 2) 8.0 to 42.0 V

EN
Limit
DE
CL2 {0} {1} {2} The threshold values that are to be monitored are defined here. If the monitored
3454    battery voltage reaches or exceeds this value for at least the delay time without
3460
Delay Battery overvoltage: Delay time (Level 1/Level 2) 0.02 to 99.99 s

EN
Verzögerung
DE
CL2 {0} {1} {2} If the monitored battery voltage exceeds the threshold value for the delay time
3455    configured here, an alarm will be issued. If the monitored battery voltage falls
3461
below the threshold (minus the hysteresis) before the delay expires the time will be
reset.
Self acknowledge Battery overvoltage: Self acknowledgment (Level 1/Level 2) YES / NO

EN
Selbstquittierend
DE
CL2 {0} {1} {2} YES ..............The control automatically clears the alarm if it is no longer valid.
3452    NO ................An automatic reset of the alarm does not occur. The reset occurs
3458

Monitoring: Battery, Undervoltage

There are two battery undervoltage alarm levels available in the control. Both alarms are definite time alarms and
are illustrated in the below figure. The figure diagrams a frequency trend and the associated pickup times and
length of the alarms. It should be noted that this figure illustrates a level 1 alarm that is self-acknowledged.
Monitoring of the voltage is done in two steps.
If this protective function is triggered, the alarm list indicates "Batt.undervolt.1" or
"Batt.undervolt.2".
[%]
Rated value
[100 %]

Limit level 1
Limit level 2
delay level 2 delay level 2
Alarm level 1
(Alarm limit 1)
Alarm level 2
(Alarm limit 2)
Figure 3-35: Monitoring - battery undervoltage

Battery undervoltage (The hysteresis is 0,7 % of the rated value).
this table are specified in the Limit 8.0 to 42.0 V 24.0 V
description is identical for all
levels; the levels may only Self-acknowledgment YES / NO NO
differ in their setting ranges. Level 2 Monitoring ON / OFF ON
Limit 8.0 to 42.0 V 20.0 V
Delay 0.02 to 99.99 s 10.00 s
Table 3-6: Monitoring - standard values - battery undervoltage

EN
Monitoring Battery undervoltage: Monitoring (Level 1/Level 2) ON / OFF
Überwachung
DE
CL2 {0} {1} {2} ON ................Undervoltage monitoring of the battery voltage is carried out
3500    according to the following parameters.
3506
OFF ..............Monitoring is disabled for level 1 and/or level 2.
Limit Battery undervoltage: Threshold value (Level 1/Level 2) 8.0 to 42.0 V

EN
Limit
DE
CL2 {0} {1} {2} The threshold values that are to be monitored are defined here. If the monitored
3504    battery voltage reaches or falls below this value for at least the delay time without
3510
Note:
The default monitoring limit for battery undervoltage is 24 Vdc after 60 seconds.
This is because in normal operation the terminal voltage is approximately 26 Vdc
(alternator charged battery).
Delay Battery undervoltage: Delay time (Level 1/Level 2) 0.02 to 99.99 s

EN
Verzögerung
DE
CL2 {0} {1} {2} If the battery voltage falls below the threshold value for the delay time configured
3505    here, an alarm will be issued. If the battery voltage exceeds the threshold (plus the
3511
hysteresis) again before the delay expires the time will be reset.
Self acknowledge Battery undervoltage: Self acknowledgment (Level 1/Level 2) YES / NO

EN
Selbstquittierend
DE
CL2 {0} {1} {2} YES ..............The control automatically clears the alarm if it is no longer valid.
3502    NO ................An automatic reset of the alarm does not occur. The reset occurs
3508

Monitoring: CANopen Interface

The CANopen interface is monitored. If the interface does not receive a CANopen protocol message before the
delay expires, an alarm will be initiated.
If this protective function is triggered, the alarm list indicates "CAN Open Fault".
Monitoring CANopen Interface: Monitoring ON / OFF

EN
Überwachung
DE
CL2 {0} {1} {2} ON................ Monitoring of the CANopen interface is carried out according to the
3150    following parameters.
OFF.............. Monitoring is disabled.
Delay CANopen Interface: Delay 0.1 to 650.0 s

EN
Verzögerung
DE
CL2 {0} {1} {2} The delay is configured with this parameter. If the interface does not receive a
3154    CANopen protocol message before the delay expires, an alarm is issued. The delay
timer is re-initialized after every message is received.
Self acknowledge CANopen Interface: Self acknowledgment YES / NO

EN
Selbstquittierend
DE
3152    NO................ An automatic reset of the alarm does not occur. The reset occurs
NOTE
This protection is only available if an external digital I/O board (e.g. IKD 1) is connected.

Discrete Inputs
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Number Terminal Function
Internal discrete inputs
[DI 1] 51 Reply from ATS limit switch: Breaker in source 1 position [S1]
[DI 2] 52 Reply from ATS limit switch: Breaker in source 2 position [S2]
[DI 3] 53 Reply from ATS limit switch: Breaker in source 1 open position [S1O] #1
[DI 4] 54 Reply from ATS limit switch: Breaker in source 2 open position [S2O] #1
[DI 5] 55 Control input (LogicsManager), pre-assigned with Inhibit ATS
[DI 6] 56 Control input (LogicsManager)
External discrete inputs (via CANopen; not included in DTSC delivery; can be e.g. IKD1, etc.)
[Dex01] --- Control input (LogicsManager)
#1..If the transfer switch type (parameter 3424) is configured to "Standard", this DI may be used as control input (LogicsManager)
Table 3-7: Discrete inputs - assignment
Discrete inputs may be configured to normally open (N.O.) or normally closed (N.C.) states. In the state N.O., no
potential is present during normal operation; if a control operation is performed, the input is energized. In the
state N.C., a potential is continuously present during normal operation; if a control operation is performed, the
input is de-energized.
Vdc (GND)
Discrete input (N.O.)
GND (Vdc)
Vdc (GND)
Discrete input (N.C.)
GND (Vdc)
Figure 3-36: Discrete inputs - control inputs - operation logic
NOTE
The discrete inputs for the breaker position reply messages (DIs 1 through 4) are fixed to N.C. and are
evaluated as N.C., i.e. the breaker is considered as "in position" if the respective DI is de-energized.

DI {x} operation Discrete input: Operation N.O. / N.C.
EN
DI {x} Funktion
DE
CL2 {0} {1} {2} The discrete inputs may be operated by an normally open (N.O.) or normally closed
1281    (N.C.) contact. The idle circuit current input can be used to monitor for a wire
break. A positive or negative voltage polarity referred to the reference point of the
DI may be applied.
N.O............... The discrete input is analyzed as "enabled" by energizing the input
(normally open).
N.C. .............. The discrete input is analyzed as "enabled" by de-energizing the input
(normally closed).
DI {x} delay Discrete input: Delay 0.08 to 650.00 s

EN
DI {x} Verzögerung
DE
CL2 {0} {1} {2} A delay time in seconds can be assigned to each alarm or control input. The discrete
1280    input must be enabled without interruption for the delay time before the unit reacts.
If the discrete input is used within the LogicsManager this delay is taken into
account as well.
The preceding parameters are used to configure the discrete inputs 5 through 12. The parameter IDs refer to DI 5.
Refer to Table 3-8 for the parameter IDs of the parameters DI 6 through DI 12. The DIs 1 through 4 are fixed for
breaker position feedback signals to the settings, which are indicated in the List Of Parameters starting on
page 143 and cannot be configured. However, they may still be used for other purposes if the breaker position
feedback signals are not used.
DI 5 DI 6 DI 7 DI 8 DI 9 DI 10 DI 11 DI 12
Operation 1281 1301 1321 1341 1361 1381 1206 1226
Delay 1280 1300 1320 1340 1360 1380 1205 1225
Table 3-8: Discrete inputs - parameter IDs
If a Woodward IKD 1 or other external expansion board (Phoenix BK 16DiDo) is connected to the DTSC via the
CAN bus, it is possible to use 16 additional discrete inputs.
The configuration of these external DIs is performed in a similar way like for the internal DIs. Refer to Table 3-9
for the parameter IDs of the parameters for external DIs 1 through 16.
External DI 1 DI 2 DI 3 DI 4 DI 5 DI 6 DI 7 DI 8
Operation 16001 16011 16021 16031 16041 16051 16061 16071
Delay 16000 16010 16020 16030 16040 16050 16060 16070
External DI 9 DI 10 DI 11 DI 12 DI 13 DI 14 DI 15 DI 16
Operation 16081 16091 16101 16111 16121 16131 16141 16151
Delay 16080 16090 16100 16110 16120 16130 16140 16150
Table 3-9: External discrete inputs - parameter IDs

Discrete Outputs (LogicsManager)

≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The discrete outputs are controlled via the LogicsManager.
 Please note the description of the LogicsManager starting on page 121.
Some outputs are assigned a function according to the application mode (see following table).
Relay Function
Number Term.
Internal relay outputs
[R 1] 31/32 'Ready for operation '; additionally programmable with LogicsManager
[R 2] 31/33 LogicsManager
[R 3] 31/34 LogicsManager
[R 4] 35/36/37 LogicsManager
[R 5] 39/40/41 LogicsManager (pre-defined with engine 2 start)
[R 6] 42/43 LogicsManager (pre-defined with command: close to source 1 position) [C1]
[R 7] 44/45 LogicsManager (pre-defined with command: close to source 2 position) [C2]
[R 8] 46/47 LogicsManager (pre-defined with command: open from source 1 to neutral position) [C1O]
[R 9] 48/49 LogicsManager (pre-defined with command: open from source 2 to neutral position) [C2O]
External relay output (via CANopen; not included in DTSC-200 delivery; can be an expansion card like IKD1)
[Rex01] --- LogicsManager
Table 3-10: Relay outputs - Assignment

Relay {x} Discrete outputs: LogicsManager for relay {x} LogicsManager
EN
Relais {x}
DE
CL2 {0} {1} {2} Once the conditions of the LogicsManager have been fulfilled, the relay will be
12580    energized. The LogicsManager and its default settings are explained on page 121 in
Appendix A: "LogicsManager".
Above parameter IDs refers to R 1. Refer to Table 3-11 for the parameter IDs of the parameters for R 2 to R 9.
R1 R2 R3 R4 R5 R6 R7 R8 R9
Parameter ID 12580 12110 12310 12320 12130 12140 12150 12160 12170
Table 3-11: Discrete outputs - parameter IDs
If a Woodward IKD 1 or other external expansion board (Phoenix BK 16DiDo) is connected to the DTSC via the
CAN bus, it is possible to use 16 additional discrete outputs.
The configuration of these external DOs is performed in a similar way like for the internal DOs. Refer to Table
3-12 for the parameter IDs of the parameters for external DOs 1 through 16.
DO 1 DO 2 DO 3 DO 4 DO 5 DO 6 DO 7 DO 8
Parameter ID 12330 12340 12350 12360 12370 12380 12390 12400
DO 9 DO 10 DO 11 DO 12 DO 13 DO 14 DO 15 DO 16
Parameter ID 12410 12420 12430 12440 12450 12460 12470 12480
Table 3-12: External discrete outputs - parameter IDs

Counters
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Configure Counters: Operation Hours, kWh, and kvarh
Counter value preset Counter: Set point value for counters 0 to 99,999,999
EN
Zähler-Setzwert
DE
CL2 {0} {1} {2} This value is utilized to set the hours in the following parameters:
2515   
• kWh counter
• kvarh counter
The number entered into this parameter is the number that will be set to the
parameters listed above when they are enabled.
S1 active power [0.00MWh] Counter: Set Source 1 kWh counter YES / NO

EN
S1 Wirkarbeit [0,00MWh]
DE
CL2 {0} {1} {2} YES .............. The current value of this counter is overwritten with the value
2514    configured in "set point value for counters". After the counter has
been (re)set, this parameter changes back to "NO" automatically.
NO ............... The value of this counter is not changed.
S1 react. power [0.00Mvarh] Counter: Set Source 1 kvarh counter YES / NO

EN
S1 Blindarbeit [0,00Mvarh]
DE
Transfers to S1 Counter: Transfers to S1 0 to 65535

EN
Transfers nach S1
DE
CL2 {0} {1} {2} This parameter is used to configure the transfer counters to a pre-set value, or
2576    reset it to “0” in case a new transfer switch has been build into the ATS cabinet.
The counter for “Transfers to S1” counts, how often the ATS switch has been
closed to the Source 1 position.
S2 active power [0.00MWh] Counter: Set Source 2 kWh counter YES / NO

EN
S2 Wirkarbeit [0,00MWh]
DE
S2 react. power [0.00Mvarh] Counter: Set Source 2 kvarh counter YES / NO

EN
S2 Blindarbeit [0,00Mvarh]
DE

Transfers to S2 Counter: Transfers to S2 0 to 65535
EN
Transfers nach S2
DE
CL2 {0} {1} {2} This parameter is used to configure the transfer counters to a pre-set value, or
2577    reset it to “0” in case a new transfer switch has been build into the ATS cabinet.
The counter for “Transfers to S2” counts, how often the ATS switch has been
closed to the Source 2 position.
NOTE
Example: The counter value preset (parameter 2515 on page 100) is configured to "3456".
If parameter 2510 will be configured to YES, the S2 active power counter will be set to 34.56MWh.

LogicsManager
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
LogicsManager: Internal Flags
Internal flags within the LogicsManager logical outputs may be programmed and used for multiple functions. For
conditions and explanation of programming please refer to page 121 in chapter "LogicsManager").
Flag {x] Internal flags: Flag {x} [x = 1 to 8] LogicsManager

EN
Merker {x]
DE
CL2 {0} {1} {2} The flags may be used as auxiliary flags for complex combinations by using the
yyyyy    logical output of these flags as command variable for other logical outputs.
Parameter ID yyyyy Flag {x}

12230 Flag 1
12240 Flag 2
12250 Flag 3
12260 Flag 4
12270 Flag 5
12280 Flag 6
12290 Flag 7
12300 Flag 8
Table 3-13: Internal flags - parameter IDs
NOTE
Flag 1 is also used as placeholder in other logical combinations. Flag 8 is preset with a timer start.

LogicsManager: Timer
LogicsManager: Daily Time Set Point
Utilizing the LogicsManager it is possible to establish specific times of the day that functions (i.e. generator
exerciser) can be enabled. The two daily time set points are activated each day at the configured time. Using the
LogicsManager these set points may be configured individually or combined to create a time range.
Setpoint {x}: Hour Timer: Daily time set point {x} [x = 1/2]: hour 0 to 23 h
EN
Setpoint {x}: Stunde

DE
CL2 {0} {1} {2} Enter the hour of the daily time set point here. Example:
1652    0.................... 0th hour of the day (midnight).
1657
23.................. 23rd hour of the day (11pm).
Setpoint {x}: Minute Timer: Daily time set point {x} [x = 1/2]: minute 0 to 59 min
EN
Setpoint {x}: Minute

DE
CL2 {0} {1} {2} Enter the minute of the daily time set point here. Example:
1651    0.................... 0th minute of the hour.
1656
59.................. 59th minute of the hour.
Setpoint {x}: Second Timer: Daily time set point {x} [x = 1/2]: second 0 to 59 s
EN
Setpoint {x}: Sekunde

DE
CL2 {0} {1} {2} Enter the second of the daily time set point here. Example
1650    0.................... 0th second of the minute.
1655
59.................. 59th second of the minute.
LogicsManager: Active Time Set Point

Utilizing the LogicsManager it is possible to establish specific days (or hours, minutes, seconds) that functions
(i.e. generator exerciser) can be enabled. The active switching point is activated only on a specified day (or hour,
minute, second). The set points may be configured individually or combined via the LogicsManager. You may
configure monthly, daily, hourly, minutely, or even secondly time set points depending on how you combine the
set points in the LogicsManager.
Active day Timer: Active time set point: day 1 to 31

EN
Aktiver Tag
DE
CL2 {0} {1} {2} Enter the day of the active switch point here. Example:
1663    01.................. 1st day of the month.
31.................. 31st day of the month.
The active time set point is enabled during the indicated day from 0:00:00 hours to
23:59:59 hours.
Active hour Timer: Active time set point: hour 0 to 23 h

EN
Aktive Stunde
DE
CL2 {0} {1} {2} Enter the hour of the active switch point here. Example:
1662    0.................... 0th hour of the day.
23.................. 23rd hour if the day.
The active time set point is enabled every day during the indicated hour from
minute 0 to minute 59.
Active minute Timer: Active time set point: minute 0 to 59 min

EN
Aktive Minute
DE
CL2 {0} {1} {2} Enter the minute of the active switch point here. Example:
The active time set point is enabled every hour during the indicated minute from
second 0 to second 59.

EN
Active second Timer: Active time set point: second 0 to 59 s
Aktive Sekunde
DE
CL2 {0} {1} {2} Enter the second of the active switch point here. Example:
1660    0 ....................0th second of the minute.
59 ..................59th second the minute.
The active time set point is enabled every minute during the indicated second.
LogicsManager: Weekly Time Set Point

Utilizing the LogicsManager it is possible to establish specific days of the week that functions (i.e. generator
exerciser) can be enabled. The weekly time set point is enabled during the indicated day from 0:00:00 hours to
23:59:59 hours.
Monday active Timer: Weekly time set points Monday: days YES / NO
EN
Montag aktiv
DE
CL2 {0} {1} {2} Please enter the days of the weekly workdays.
1670    Monday ........... YES - The switch point is enabled every Monday
NO - The switch point is disabled every Monday
Tuesday active Timer: Weekly time set points Tuesday: days YES / NO
EN
Dienstag aktiv
DE
1671    Tuesday ........... YES - The switch point is enabled every Tuesday
NO - The switch point is disabled every Tuesday
Wednesday active Timer: Weekly time set points Wednesday: days YES / NO
EN
Mittwoch aktiv
DE
1672    Wednesday ..... YES - The switch point is enabled every Wednesday
NO - The switch point is disabled every Wednesday
Thursday active Timer: Weekly time set points Thursday: days YES / NO
EN
Donnerstag aktiv
DE
1673    Thursday......... YES - The switch point is enabled every Thursday
NO - The switch point is disabled every Thursday
Friday active Timer: Weekly time set points Friday: days YES / NO
EN
Freitag aktiv
DE
1674    Friday.............. YES - The switch point is enabled every Friday
NO - The switch point is disabled every Friday
Saturday active Timer: Weekly time set points Saturday: days YES / NO
EN
Samstag aktiv
DE
1675    Saturday ......... YES - The switch point is enabled every Saturday
NO - The switch point is disabled every Saturday
Sunday active Timer: Weekly time set points Sunday: days YES / NO
EN
Sonntag aktiv
DE
  
1676
Sunday ............ YES - The switch point is enabled every Sunday
NO - The switch point is disabled every Sunday

Interfaces
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
NOTE
Please refer to the Interface Manual 37486 for a detailed description of the interface parameters.
Device number Interfaces: Device address 1 to 127

EN
Gerätenummer
DE
CL2 {0} {1} {2} So that this control unit may be positively identified on the CAN bus, the unit
1702    address must be set in this parameter. The address may only be represented once on
the CAN bus. All other addresses on the CAN bus are calculated on the basis of the
address entered in this parameter.
Interfaces: CAN Bus (FlexCAN)
NOTE
The CAN bus is a field bus and subject to various disturbances. Therefore, it cannot be guaranteed that
every request will be answered. We recommend repeating a request, which is not answered within
reasonable time.
Baudrate CAN bus: Baud rate 20 / 50 / 100 / 125 / 250 / 500 / 800 / 1,000 kBaud
EN
Baudrate
DE
CL2 {0} {1} {2} This parameter defines the used Baud rate. Please note, that all participants on the
3156    CAN bus must use the same Baud rate.

Interfaces: CAN BUS: CANopen
CAN-Open Master CANopen Master YES / NO

EN
CAN-open Master
DE
CL2 {0} {1} {2} YES ..............The DTSC-200 is the CANopen Master.
  
9000
The unit automatically changes into operational mode and transmits
Remote Start messages since Broadcast
Attached external devices were configured from the unit with SDO
messages. The unit sends a SYNC message all 20ms on COB ID 80
Hex.
NO ................The DTSC-200 is a CANopen Slave.
Producer heartbeat time CAN bus: Producer heartbeat time 20 to 65,530 ms

EN
Producer heartbeat time

DE
CL2 {0} {1} {2} Independent from the CANopen Master configuration, the unit transmits a heartbeat
9120    message with this configured heartbeat cycle time. If the producer heartbeat time is
equal 0, the heartbeat will only be sent as response to a remote frame request. The
time configured here will be rounded up to the next 20 ms step.
COB-ID SYNC Message COB-ID SYNC Message 1 to FFFFFFFF

EN
COB-ID SYNC Message

DE
CL2 {0} {1} {2} This parameter defines whether the unit generates the SYNC message or not.
9100   
Complies with CANopen specification: object 1005, subindex 0; defines the COB ID of the
synchronization object (SYNC). The structure of this object is shown in the following tables:
UNSIGNED 32 MSB LSB

bits bits 31 30 29 28-11 10-0
11 bit ID 11 bit ID X 0/1 X 000000000000000000 11 bit identifier
bit number value meaning

31 (MSB) X N/A
30 0 Unit does not generate SYNC message
1 Unit generates SYNC message
29 X N/A
28-11 0 always
10-0 (LSB) X bits 10-0 of SYNC COB ID
Configure external devices Configure external devices YES / NO

EN
Externe Geräte konfigurieren

DE
CL2 {0} {1} {2} This parameter starts the configuration of external Phoenix expansion boards.
15134   
Proceed as follows to configure an external device:
• Connect external device
• Configure parameters at the DTSC (Node ID, DI/Os, AI/Os)
• Set this parameter to “Yes”
• Verify the successful configuration of the external device
Note: This parameter can only be used to configure a Phoenix expansion board.
Refer to the IKD 1 manual 37135 for configuring the IKD 1 expansion boards.

Interfaces: CAN BUS: CANopen: Additional Server SDOs
2nd Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
EN
2. Client->Server COB-ID (rx)
DE
CL2 {0} {1} {2} In a multi-master application, each master must have a unique identifier (Node ID)
  
9020
to be able to receive remote signals (i.e. acknowledge). The additional SDO
channel will be made available by configuring this Node ID to a value different
than zero. This is the additional CAN ID for the PLC.
2nd Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
EN
2. Server->Client COB-ID (tx)

DE
9022    to be able to receive remote signals (i.e. acknowledge). The additional SDO
than zero. This is the additional CAN ID for the unit.
3rd Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
EN

DE
3rd Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
EN

DE
4th Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
EN

DE
4th Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
EN

DE
5th Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
EN

DE
5th Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
EN

DE

NOTE
The COB IDs must be entered in decimal numbers in ToolKit and in hexadecimal numbers in the unit.
Here are some important conversions:
Hexadecimal value Decimal value
80h 128
181h 385
201h 513
281h 641
301h 769
381h 897
401h 1025
481h 1153
501h 1281
581h 1409
601h 1537
80000000h 2147483648
Interfaces: CAN BUS: CANopen: Receive PDO (RPDO) {x} ({x} = 1/2)
Figure 3-37 shows the principle of PDO mapping.
Object Dictionary
xxxxh Application Object 1
PDO Mapping
0 3
1 yyyyh 1
2 zzzzh 1 yyyyh Application Object 2
3 xxxxh 1
zzzzh Application Object 3
PDO: App. Object 2 Application Object 3 App. Object 1

Figure 3-37: Interfaces - Principle of PDO mapping

COB-ID Receive PDO 1/2 - COB-ID 1 to FFFFFFFF
EN
COB-ID
DE
CL2 {0} {1} {2} This parameter contains the communication parameters for the PDOs, the device is
9300    able to receive.
9310
Complies with CANopen specification: object 1400 (for RPDO 1 and 1401 for RPDO 2), subindex 1.
The structure of this object is shown in the following tables:
UNSIGNED 32 MSB LSB

bits 31 30 29 28-11 10-0
11 bit ID 0/1 X X 000000000000000000 11 bit identifier

31 (MSB) 0 PDO exists / is valid
1 PDO does not exist / is not valid
30 X N/A
29 X N/A
28-11 0 always
10-0 (LSB) X bits 10-0 of COB ID
PDO valid / not valid allows selecting, which PDOs are used in the operational state.
CAUTION
The COB-IDs have to be configured different, even if one RPDO is configured to "no func.".
Function Function for RPDO 1/2 no func. / 1st IKD /2nd IKD / Bk 16DIDO
EN
Funktion
DE
CL2 {0} {1} {2} The unit provides pre-configured CAN bus settings for the connection of different
9050    units. The unit to be connected must be selected here.
9051
No func. ....... No external unit is selected for connection. The CAN bus is disabled.
Values are not sent or received.
1st IKD ......... The unit is pre-configured for the connection of a Woodward IKD 1
expansion board.
2nd IKD ........ The unit is pre-configured for the connection of a second Woodward
IKD 1 expansion board.
BK 16 DIDO The unit is pre-configured for the connection of a Phoenix Contact
BK 16 DIDO expansion board.
The following table shows several possible functional combinations:
PDO1 PDO2 1st IKD 2nd IKD OFF

1st IKD NO YES YES
2nd IKD YES NO YES
Bk 16DIDO NO NO YES
no func. YES YES YES
Read: If PDO1 is configured as 1. IKD, then PDO2 can only be configured as either 2. IKD or "no func.".
Node-ID of the device Node-ID of the device 1 to 127

EN
Node-ID des Gerätes

DE
CL2 {0} {1} {2} Node-ID of the attached device. The SDO messages were sent on the standard
9060    SDO-IDs or the answers were expected.
9061

EN
RPDO-COP-ID ext. device {x} RPDO-COB-ID ext. device 1 1 to FFFFFFFF
RPDO-COP-ID ext. Gerät {x}
DE
CL2 {0} {1} {2} Value to be written in the object 1800h sub index 1h of the external device.
9070   
9072
CAUTION
COB-IDs already used in other PDOs should be used.
COB-IDs in a CANopen device after loading the standard values:
280h + Node-ID = 640 + Node-ID Object 1801h Subindex 1
The receiving COB-IDs are preallocated:
500h + Node-ID = 1280 + Node-ID Object 1403h Subindex 1.
Problems may be encountered if a COB-ID is assigned multiple times.
Interfaces: CAN Bus: CANopen: Transmit PDO (TPDO) {x} ({x} = 1 to 4)
COB-ID CAN bus 1: Transmit PDO 1 - COB ID 1 to FFFFFFFF

EN
COB-ID
DE
CL2 {0} {1} {2} This parameter contains the communication parameters for the PDOs the unit is
9600    able to transmit. The unit transmits data (i.e. visualization data) on the CAN ID
9610
9620 configured here.
9630
Complies with CANopen specification: object 1800 for (TPDO 1, 1801 for TPDO 2, 1802 for TPDO 3,
and 1803 for TPDO 4), subindex 1. The structure of this object is shown in the following tables:
UNSIGNED 32 MSB LSB

bits bits 31 30 29 28-11 10-0
11 bit ID 11 bit ID 0/1 X X 000000000000000000 11 bit identifier

31 (MSB) 0 PDO exists / is valid
1 PDO does not exist / is not valid
30 X N/A
29 X N/A
28-11 0 always
10-0 (LSB) X bits 10-0 of COB ID
PDO valid / not valid allows selecting, which PDOs are used in the operational state.

Transmission type CAN bus 1: Transmit PDO 1 - Transmission type 0 to 255
EN
Transmission type
DE
9602    able to transmit. It defines whether the unit broadcasts all data automatically (value
9612
9622 254 or 255) or only upon request with the configured address of the COB ID SYNC
9632
message (parameter 9100).
Complies with CANopen specification: object 1800 (for TPDO 1, 1801 for TPDO 2, 1802 for TPDO 3,
and 1803 for TPDO 4), subindex 2. The description of the transmission type is shown in the following
table:
transmission type PDO transmission

cyclic acyclic synchronous asynchronous RTR only
0 will not be sent
1-240 X X
241-251 will not be sent
252 will not be sent
253 will not be sent
254 X
255 X
A value between 1 and 240 means that the PDO is transferred synchronously and cyclically. The
transmission type indicating the number of SYNC, which is necessary to trigger PDO transmissions.
Receive PDOs are always triggered by the following SYNC upon reception of data independent of the
transmission types 0 to 240. For TPDOs, transmission type 254 and 255 means, the application event is
the event timer.
Event-timer CAN bus 1: Transmit PDO 1 – Event timer 0 to 65000 ms

EN
Event-timer
DE
9604    able to transmit. The broadcast cycle for the transmitted data is configured here.
9614
9624 The time configured here will be rounded up to the next 5 ms step.
9634
Complies with CANopen specification: object 1800 (for TPDO 1, 1801 for TPDO 2, 1802 for TPDO 3,
and 1803 for TPDO 4), subindex 5
Number of Mapped Objects CAN bus 1: Transmit PDO 1 - Number of mapped objects 0 to 4
EN
Anzahl der Mapped Objekte

DE
CL2 {0} {1} {2} This parameter contains the mapping for the PDOs the unit is able to transmit. This
9609    number is also the number of the application variables, which shall be transmitted
9619
9629 with the corresponding PDO.
9639
Complies with CANopen specification: object 1A00 (for TPDO 1, 1A01 for TPDO 2, 1A02 for TPDO 3,
and 1A03 for TPDO 4), subindex 0
1. Mapped Object CAN bus 1: Transmit PDO 1 - 1. Mapped object 0 to 65535

EN
1. Mapped Objekt
DE
CL2 {0} {1} {2} This parameter contains the information about the mapped application variables.
9605    These entries describe the PDO contents by their index. The sub-index is always 1.
9615
9625 The length is determined automatically.
9635

EN
2. Mapped Objekt
DE
9616
9636

EN
3. Mapped Objekt
DE
9617
9637

EN
4. Mapped Objekt
DE
9618
9638
NOTE
CANopen allows sending 8 byte of data with each Transmit PDO. These may be defined separately if no
pre-defined data protocol is used.
All data protocol parameters with a parameter ID may be sent as an object with a CANopen Transmit
PDO.
In this case, the data length will be taken from the data byte column (refer to the Data Protocols section
in the Interface Manual 37486):
• 1,2 UNSIGNED16 or SIGNED16
• 1,2,3,4 UNSIGNED32 or SIGNED32
• 3,4,5,6 UNSIGNED32 or SIGNED32
• etc.
The object ID is identical with the parameter ID when configuring via front panel or ToolKit.

Interfaces: Serial Interface 1 (RS-232)
Baudrate Serial interface: Baud rate 2.4 / 4.8 / 9.6 / 14.4 / 19.2 / 38.4 / 65 / 115 kBaud
EN
Baudrate
DE
CL2 {0} {1} {2}  A DPC (P/N 5417-557 or 5417-1257) must be used for connecting the
3163    control unit from the service interface to a PC or to another participant.
The serial interface of this unit connects to an RJ45-plug on the side of the
housing. This parameter defines the baud rate that communications will be
performed. Please note, that all participants on the service interface must use the
same Baud rate.
Parity Serial interface: Parity no / even / odd

EN
Parity
DE
CL2 {0} {1} {2} The used parity of the service interface is set here.
3161   
Stop Bits Serial interface: Stop bits one / two

EN
Stop Bits
DE
CL2 {0} {1} {2} The number of stop bits is set here.
3162   
Interfaces: Serial Interface 2 (RS-485)
Baudrate Serial interface 2: Baud rate 2.4 / 4.8 / 9.6 / 14.4 / 19.2 / 38.4 / 56 / 115 kBaud
EN
Baudrate
DE
CL2 {0} {1} {2} This parameter defines the baud rate for communications. Please note, that all
3170    participants on the service interface must use the same baud rate.
Parity Serial interface 2: Parity no / even / odd

EN
Parity
DE
CL2 {0} {1} {2} The used parity of the service interface is set here.
3171   
Stop bits Serial interface 2: Stop bits one / two

EN
Stop Bits
DE
CL2 {0} {1} {2} The number of stop bits is set here.
3172   
Full-, halfduplex mode Serial interface 2: Full-/halfduplex mode Fullduplex / Halfduplex

EN
Voll-, Halbduplex Modus

DE
CL2 {0} {1} {2} Fullduplex ... Fullduplex mode is enabled.

3173    Halfduplex .. Halfduplex mode is enabled.
ModBus Slave ID Serial interface: Modbus Slave ID 0 to 255

EN
ModBus Slave ID
DE
CL2 {0} {1} {2} The Modbus device address is entered here, which is used to identify the device
3185    via Modbus. If 0 is entered here, the Modbus Slave module is disabled.
Modbus Reply delay time Serial interface: Reply delay time 0.00 to 0.20 s
EN
Modbus Zeitverzöger. Der

DE
Antwort This is the minimum delay time between a request from the Modbus master and
CL2 {0} {1} {2}
the sent response of the slave. This time is also required if an external interface
3186   
converter to RS-485 is used for example. Please note that you also need the
DPC (refer to page 14) in this case.

System
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
System: Configure Display Backlight
Configure display backlight Display backlight ON / OFF / Auto / Key actv.

EN
Konfig. Display Beleuchtung

DE
CL2 {0} {1} {2} This parameter determines the behavior of the display backlight. The following
4556    options are available:
ON ................The display backlight is always enabled.

OFF ..............The display backlight is always disabled.
Auto ..............The display backlight will be disabled if no voltage is detected
anymore at both connected sources.
Key actv. ......The display backlight will be disabled if no softkey has been pressed
for the time configured in parameter 4557. It will be enabled again
after any softkey of the unit has been pressed.
Time until backlight shutdown Time until backlight shutdown 1 to 999 s

EN
Zeit bis Abschaltung

DE
CL2 {0} {1} {2}  This parameter is only visible if parameter 4556 has been configured to
4557    "Key actv.".
If no softkey has been pressed for the time configured here, the display backlight
will be disabled.

System: Configure Daylight Saving Time
It is possible to configure the real-time clock for an automatic change to daylight saving time. Start and end
date/time of the daylight saving time period have to be entered for this.
Example: If daylight saving time starts at 2:00 am on the 2nd Sunday in March and ends at 2:00 am on the 1st
Sunday in November, the unit has to be configured like shown in Table 3-14 to enable an automatic change to
daylight saving time and back to standard time.
4591 Daylight saving time On
4594 DST begin time 2
4598 DST begin weekday Sunday
4592 DST begin nth weekday 2nd
4593 DST begin month 3
4597 DST end time 2
4599 DST end weekday Sunday
4595 DST end sunday 1st
4596 DST end month 11
Table 3-14: Daylight saving time - configuration example
USA, Canada European Union

Year DST Begins 2 a.m. DST Ends 2 a.m. DST Begins 1 a.m. UTC=GMT DST Ends 1 a.m. UTC=GMT
(Second Sunday in March) (First Sunday in November) (Last Sunday in March) (Last Sunday in October)
2008 March 9, 2008 November 2, 2008 March 30, 2008 October 26, 2008
Table 3-15: Daylight saving time - examplary dates
Daylight saving time Daylight saving time ON / OFF

EN
Sommer-Winterzeit Erkennung
DE
CL2 {0} {1} {2} ON ................ Daylight saving time is enabled.

  
4591
OFF .............. Daylight saving time is disabled.
NOTE
The following parameters will only be displayed, if Daylight saving time (parameter 4591) has been
configured to “On” and the enter button has been pressed.
DST begin time Daylight saving time begin time 0 to 23 h

EN
Sommerzeitbeginn Uhrzeit
DE
CL2 {0} {1} {2} The real-time clock will be advanced by one hour when this time is reached on the
4594    DST begin date. Example:
0 .................... 0th hour of the day (midnight).
23 .................. 23rd hour of the day (11 pm).
DST begin weekday Daylight saving time begin weekday weekday

EN
Sommerzeitbeginn Wochentag
DE
CL2 {0} {1o} {1oc} {2oc} The weekday for the DST begin date is configured here
4598    

th
EN
DST begin nth. weekday Daylight saving time begin n weekday weekday order no.
Sommerzeitbeginn x. Wochentag
DE
CL2 {0} {1o} {1oc} {2oc} The order number of the weekday for the DST begin date is configured here.
4592     Example:
1st .................DST starts on the 1st configured weekday of the DST begin month.
2nd................DST starts on the 2nd configured weekday of the DST begin month.
3rd ................DST starts on the 3rd configured weekday of the DST begin month.
4th ................DST starts on the 4th configured weekday of the DST begin month.
Last...............DST starts on the last configured weekday of the DST begin month.
LastButOne .DST starts on the last but one configured weekday of the DST
begin month.
LastButTwo .DST starts on the last but two configured weekday of the DST
begin month.
LastButThree . DST starts on the last but three configured weekday of the DST
begin month.
DST begin month Daylight saving time begin month 1 to 12

EN
Sommerzeitbeginn Monat
DE
CL2 {0} {1o} {1oc} {2oc} The month for the DST begin date is configured here. Example:
4593     1 ....................1st month of the year.
12 ..................12th month of the year.
DST end time Daylight saving time end time 0 to 23 h

EN
Sommerzeitende Uhrzeit
DE
CL2 {0} {1o} {1oc} {2oc} The real-time clock will fall back by one hour when this time is reached on the
4597     DST end date. Example:
0 ....................0th hour of the day (midnight).
23 ..................23rd hour of the day (11 pm).
DST end weekday Daylight saving time end weekday weekday

EN
Sommerzeitende Wochentag
DE
CL2 {0} {1o} {1oc} {2oc} The weekday for the DST end date is configured here
4599    
DST end nth. weekday Daylight saving time end nth weekday weekday order no.
EN
Sommerzeitende x. Wochentag
DE
CL2 {0} {1o} {1oc} {2oc} The order number of the weekday for the DST end date is configured here.
4595     Example:
1st .................DST ends on the 1st configured weekday of the DST end month.
2nd................DST ends on the 2nd configured weekday of the DST end month.
3rd ................DST ends on the 3rd configured weekday of the DST end month.
4th ................DST ends on the 4th configured weekday of the DST end month.
Last...............DST ends on the last configured weekday of the DST end month.
LastButOne .DST ends on the last but one configured weekday of the DST end
month.
LastButTwo .DST ends on the last but two configured weekday of the DST end
month.
LastButThree . DST ends on the last but three configured weekday of the DST
end month.
DST end month Daylight saving time end month 1 to 12

EN
Sommerzeitende Monat
DE
CL2 {0} {1o} {1oc} {2oc} The month for the DST end date is configured here. Example:
4596     1 ....................1st month of the year.
12 ..................12th month of the year.

System: Password System

Refer to the Password section on page 23 for a detailed description of the password system.
Code level display Password system: Code level via display Info
EN
DE
Codeebene Display
CL2 {0} {1} {2} This value displays the code level, which is currently enabled for access via the
  
10405
front panel display.
Code level CAN port Password system: Code level via CAN-Bus Info
EN
Codeebene CAN Schnittstelle

DE
CL2 {0} {1} {2} This value displays the code level, which is currently enabled for access via the
10407    CAN interface.
Code level serial port/DPC Password system: Code level via serial RS-232 (DPC) interface Info
EN
Codeebene RS232/DPC
DE
CL2 {0} {1} {2} This value displays the code level, which is currently enabled for access via RS-
10406    232 serial interface #1.
Supercommissioning level code Password system: Password "Supercommissioning" (CL5) 0001 to 9999
EN
Code Supercommissioning Ebene

DE
CL5 {0} {1} {2} The password for the code level "Supercommissioning" is defined in this
10411    parameter. Refer to the Password section on page 23 for default values.
Temp. supercomm. Level code Password system: Password "Temporary Supercommissioning" (CL4) 00001to 9999
EN
Code temp. Supercomm. Ebene

DE
CL5 {0} {1} {2} The algorithm for calculating the password for the code level "Temporary
10412    Supercommissioning" is defined in this parameter.
Commissioning level code Password system: Password "Commission" (CL3) 0001 to 9999
EN
Code Inbetriebnahme Ebene

DE
CL3 {0} {1} {2} The password for the code level "Commission" is defined in this parameter.
10413    Refer to the Password section on page 23 for default values.
Temp. commissioning level code Password system: Password "Temporary Commission" (CL2) 0001 to 9999
EN
Code temp. Inbetriebn. Ebene

DE
CL3 {0} {1} {2} The algorithm for calculating the password for the code level "Temporary
10414    Commissioning" is defined in this parameter.
Basic level code Password system: Password "Service Level" (CL1) 0001 to 9999
EN
Code Serviceebene
DE
CL1 {0} {1} {2} The password for the code level "Service" is defined in this parameter. Refer to
10415    the Password section on page 23 for default values.
Password Password system: Entry via front panel 0000 to 9999

EN
Passwort
DE
CL0 {0} {1} {2} To configure the control via the front panel bus enter the password.
10416   
Password CAN Password system: Entry via CAN bus 0000 to 9999
EN
Passwort CAN
DE
CL0 {0} {1} {2} To configure the control via CAN bus enter "password CAN".
10402   
Password DPC Password system: Entry via DPC 0000 to 9999

EN
Passwort RS232 / DPC

DE
CL0 {0} {1} {2} To configure the control via DPC please enter "password DPC".
10401   

EN
Factory Settings Factory settings: Factory settings CAN YES / NO
Werkseinstellung
DE
CL2 {0} {1} {2} YES ..............The resetting of the factory settings via CAN bus will be enabled.
1703    NO ................The resetting of the factory settings via CAN bus will not be enabled.
Note: This parameter is not visible in ToolKit.
Factory Settings DPC/RS232 Factory settings: Factory settings DPC/RS-232 YES / NO

EN
Werkseinstellung DPC/RS232
DE
CL2 {0} {1} {2} YES ..............The resetting of the factory settings via DPC/RS-232 will be enabled.
  
1704
NO ................The resetting of the factory settings via DPC/RS-232 will not be
enabled.
Factory Settings CAN Factory settings: Factory settings CAN YES / NO

EN
Werkseinstellung CAN
DE
CL2 {0} {1} {2} YES ..............The resetting of the factory settings via CAN bus will be enabled.
1705    NO ................The resetting of the factory settings via CAN bus will not be enabled.
Set default values Factory settings: Set default values YES / NO

EN
Standardwerte
DE
CL2 {0} {1} {2} YES ..............The default values, which have been enabled with parameter 1703,
1701    1704 or parameter 1705, will be loaded by the unit.
NO ................The factory settings will not be loaded by the unit.
Start Bootloader Factory settings: Start Bootloader 00000

EN
Bootloader starten
DE
CL3 {0} {1} {2} This function may be used to start the Bootloader. In order to do this, the correct
10500    code must be entered here while the unit is in the code level required for this.
CAUTION
The Start Bootloader function is used to flash the software and may only be used by authorized
Woodward technicians!
NOTE
If the DTSC-200 parameters are read out via CAN / DPC and stored as standard values, all parameters
behind parameter 1701 (Set default values) will not be overwritten when writing back the standard
value file via CAN / DPC.
This prevents an unintentional start of the Bootloader or an overwriting of the time or date in the unit
with a wrong (old) value. The following version information is only for info anyway and cannot be
overwritten.

System: Real-Time Clock Set

This screen shows the current date and time. The clock is implemented as
real time clock. In case of a voltage supply failure an internal battery
guarantees that the information is not lost. The data stand for:
XX:YY:ZZ ............. hour:minute:second.

AAAA-BBB-CC ...... Year-month-day.
System: Adjust Clock

Hour Adjust clock: hour 0 to 23 h
EN
Stunden
DE
CL2 {0} {1} {2} The current hour of the clock time is set here. Example:
1710    0.................... 0th hour of the day.
23.................. 23th hour of the day.
Minute Adjust clock: minute 0 to 59 min

EN
Minuten
DE
CL2 {0} {1} {2} The current minute of the clock time is set here. Example:
Second Adjust clock: second 0 to 59 s

EN
Sekunden
DE
CL2 {0} {1} {2} The current second of the clock time is set here. Example:
1708    0.................... 0th second of the minute.
59.................. 59th second of the minute.
Transfer time to clock Adjust clock: transfer time to clock YES / NO

EN
Zeit in Uhr übernehmen

DE
CL2 {0} {1} {2} YES .............. Adjusted time will be transferred to the unit.
1698    NO................ Adjusted time will be not transferred to the unit.
System: Adjust Date

Day Adjust clock: day 1 to 31
EN
Tag
DE
CL2 {0} {1} {2} The current day of the date is set here. Example:
1711    1.................... 1st day of the month.
31.................. 31st day of the month.
Month Adjust clock: month 1 to 12

EN
Monat
DE
CL2 {0} {1} {2} The current month of the date is set here. Example:
1712    1.................... 1st month of the year.
12.................. 12th month of the year.
Year Adjust clock: year 0 to 99

EN
Jahr
DE
CL2 {0} {1} {2} The current year of the date is set here. Example:
1713    0.................... Year 2000.
99.................. Year 2099.
Transfer date to clock Adjust clock: transfer date to clock YES / NO

EN
Datum in Uhr übernehmen

DE
CL2 {0} {1} {2} YES .............. Adjusted date will be transferred to the unit.
1699    NO................ Adjusted date will be not transferred to the unit.

System: Versions
The parameters in this section are informational only and cannot be modified.
The control unit may be identified from the numbers located on the unit and in the software. The most important
technical information is located on the unit data plate. Technical data can be located in manual 37482.
1 S/N serial number (numeric)

2 S/N manufactured date (YYMM)
3 S/N serial number (as Barcode)
4 P/N part number
5 REV part number revision
6 Details technical data
7 Type description (long)
8 Type Description (short)
9 UL UL sign
Serial number Version: Serial number (S/N) info

EN
Seriennummer
DE
{0} {1} {2} The serial number (S/N) is utilized to identify individual control units. The number
900    can also be found on the data plate (items #1 & #3).
Boot item number Version: Part number of the firmware (P/N) info
EN
Boot Artikelnummer
DE
{0} {1} {2} The part number (P/N) is the firmware in the control unit.
950   
Boot revision Version: Revision of the item number of the firmware (REV) info
EN
Boot Revision
DE
{0} {1} {2} The revision number (REV) is the revision of the control unit firmware.
960   
Boot version Version: Version of the firmware info

EN
Boot Version
DE
{0} {1} {2} This number (Vx.xxxx) represents the version of the control unit firmware.
965   
Program item number Version: Item number of the application software (P/N) info
EN
Programm Artikelnummer
DE
{0} {1} {2} The part number (P/N) is the application software running the control unit.
930   
Program revision Version: Revision of the item number of the software (REV) info
EN
Programm Revision
DE
{0} {1} {2} The revision number (REV) is the revision of the application software running the
940    control unit.
Program version Version: Version of the application software info

EN
Programm Version
DE
{0} {1} {2} This number (Vx.xxxx) represents the version of the application software running
945    the control unit.

Appendix A.
LogicsManager
The LogicsManager is used to customize the sequence of events in the control unit such as the start command of
the engine or the operation of control unit relay outputs. For example, the start routine may be programmed so
that it requires the closing of a discrete input or a preset time of day. Two independent time delays are provided
for the configured action to take place and be reset. The following table shows the function of each relay in each
of the application modes.
Starting the engine can be carried out externally via a discrete input. With it the LogicsManager is used whose
conditions and programming is defined as follows.
Table 3-10 on page 98 shows the assignment of different functions to various discrete outputs.

Structure and description of the LogicsManager
Command [C1] Sign [S1]
Figure 3-38: LogicsManager - function overview
• Command (variable) - A list of over 100 parameters and functions is provided for the command inputs.
Examples of the parameters that may be configured into these commands are Source 1 undervoltage, Start
fail, and Cool down. These command variables are used to control the output function or relay. Refer to
Logical Command Variables starting on page 126 for a complete list of all command variables.
• Sign - The sign field can be used to invert the state of the command or to fix its output to a logical true or
false if the command is not needed. Setting the sign to the NOT state changes the output of the command
variable from true to false or vise versa.
• Operator - A logical device such as AND or OR.
• (Logical) output - The action or control sequence that occurs when all parameters set into the
LogicsManager are met.
[Cx] - Command {x} [Sx] - Sign {x} [Ox] - Operator {x} [Ax] - Output {x}
Value {[Cx]}
The value [Cx] is
passed 1:1. AND
Logical AND
NOT Value {[Cx]} NAND

The opposite of the Logical negated AND
value [Cx] is passed.
The description and the tables of OR The description and the tables of
all values, flags, and internal Logical OR all logical outputs, flags, and
functions that are able to functions that are able to
0 [False; always "0"]
combine via the LogicsManager NOR combine via the LogicsManager
The value [Cx] is ignored and
can be found in the Logical Logical negated OR can be found in the Logical
this logic path
Command Variables section will always be FALSE. Outputs section starting on
starting on page 126. XOR page 124.
Exclusive OR
1 [True; always "1"]
NXOR
The value [Cx] is ignored and
Exclusive negated OR
this logic path
will always be TRUE.
(See Table 3-17 for symbols)
Table 3-16: LogicsManager - command overview
NOTE
A logical output may either be delayed when switching on or switching off. The time starts when all
logical functions of the operation have been met.

Configuration of the chain of commands

Using the values specified in the above table, the chain of commands of the LogicsManager (for example:
operating the relays, setting the flags, specification of the automatic functions) is configured as follows:
[Ax] = ( ( [C1] & [S1] ) & [O1] & ( [C2] & [S2] ) ) & [O2] & ( [C3] & [S3] )
Programming example for the LogicsManager:

Flag 8 shall become TRUE, whenever "Setpoint 1" is TRUE "AND" "Setpoint 2" is "NOT" TRUE "AND" the
"Active week day" is TRUE 
Figure 3-39: LogicsManager - display in ToolKit

Figure 3-40: LogicsManager - display in LCD
Logical Symbols
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The following symbols are used for the graphical programming of the LogicsManager.
AND OR NAND NOR NXOR XOR

DTSC
DIN 40 700
ASA
US MIL
IEC617-12
& >=1 & >=1 = =1
Truth x1 x2 y x1 x2 y x1 x2 y x1 x2 y x1 x2 y x1 x2 y
table 0 0 0 0 0 0 0 0 1 0 0 1 0 0 1 0 0 0
0 1 0 0 1 1 0 1 1 0 1 0 0 1 0 0 1 1
1 0 0 1 0 1 1 0 1 1 0 0 1 0 0 1 0 1
1 1 1 1 1 1 1 1 0 1 1 0 1 1 1 1 1 0
Table 3-17: LogicsManager - logical symbols

Logical Outputs
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The logical outputs or combinations may be grouped into three categories:
• internal logical flags

• Internal functions
• relay outputs
NOTE
The numbers of the logical outputs in the third column may again be used as input variable for other
outputs in the LogicsManager.
Logical Outputs: Internal Flags

8 internal logical flags may be programmed to activate/deactivate functions. This permits more than 3 commands
to be included in a logical function. The may be used as "auxiliary flags".
Name Function Number

Flag 1 Internal flag 1 00.01
Logical Outputs: Internal functions

The following logical functions may be used to activate/deactivate functions.

External acknowledge The alarm acknowledgement is performed from an external source (refer to 00.15
parameter 12490 on page 66)

Logical Outputs: Relay Outputs

All relays may be controlled directly by the LogicsManager depending on the respective application mode.

Relay 1 If this logical output becomes true, the relay output 1 will be activated 13.01
External DO 1 If this logical output becomes true, the external relay output 1 will be activated 14.01

Logical Command Variables

≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The logical command variables are grouped into 14 categories:
• [00.00] Internal flags

• [01.00] Alarm classes
• [03.00] Engine control
• [04.00] Operating status
• [05.00] Alarms of the engine
• [06.00] Load alarms
• [08.00] System alarms
• [09.00] Discrete inputs
• [11.00] Time functions
• [12.00] External discrete inputs
• [13.00] Internal relay output status
• [14.00] External relay outputs status
• [19.00] ATS status flags
• [20.00] ATS status flags
Logical Command Variables: [00.00] - Internal Flags

Internal flag, Logic command variables 00.01-00.20
Internal Flags are the result of the output of the logic ladders from Flag 1 to 8. Flags are internal logic that can be
sent to other flags or Command variables.
No. Name Function Note

00.01 Flag 1 Internal flag 1 Internal calculation; page 124
00.09 - - not used
00.10 - - not used
00.11 - - not used
00.12 - - not used
00.13 - - not used
00.14 - - not used
00.15 External acknowledge The alarm acknowledgement is performed from Internal calculation; page 66
an external source
00.16 Operation mode AUTO - not used
00.18 - - not used
00.19 - - not used
00.20 - - not used

Logical Command Variables: [01.00] - Alarm Classes

Alarm class commands, Logic command variables 01.01-01.10
Alarm classes may be configured as command variables for all logical outputs in the LogicsManager.
Number Name / Function Note

- - not used
- - not used
- - not used
- - not used
- - not used
- - not used
- - not used
- - not used
- - not used
01.10 Centralized alarm TRUE as long as at least one of the alarm classes B/C/D/E/F is active
Logical Command Variables: [03.00] - Engine Control

Engine control commands, Logic command variables 03.01-03.14
These variables may be used as command variable in a logical output to set parameters for customized
operations.

03.01 - not used
03.02 - not used
03.03 - not used
03.04 - not used
03.05 Horn (active) TRUE if alarm class B to F is activated until
the time until horn reset is expired or it is
acknowledged for the first time.
03.06 - not used
03.07 - not used
03.08 - not used
03.09 - not used
03.10 - not used
03.11 - not used
03.12 - not used
03.13 - not used
03.14 - not used
03.15 - not used
03.16 - not used
03.17 - not used
03.18 - not used
03.19 - not used
03.20 - not used

Logical Command Variables: [04.00] - Operating Status

Operating status commands, 4.01-04.15
Operating status may be used as command variables in a logical output to set parameters for customized
operations.
No. Name Function Note

04.01 - - not used
04.02 - - not used
04.03 - - not used
04.04 Lamp test A lamp test is being performed TRUE if the lamp test is active
04.05 Acknowledge "Acknowledge" push button has been pressed Note: this condition is TRUE for approx.
or an external acknowledgment via 40 ms and must be extended utilizing a delay
LogicsManager time
04.06 - - not used
04.07 - - not used
04.08 - - not used
04.09 - - not used
04.10 - - not used
04.11 - - not used
04.12 - - not used
04.13 - - not used
04.14 Remote Request over remote control to acknowledge TRUE if the acknowledgement bit is set
acknowledge
04.15 - - not used
04.16 - - not used
04.17 - - not used
04.18 - - not used
04.19 - - not used
04.20 - - not used
Logical Command Variables: [06.00] - Load Alarms

Load alarm status commands, 06.01-06.15
These engine alarms may be used as command variables in a logical output to set parameters for customized
operations.

06.01 - not used
06.02 - not used
06.03 - not used
06.04 - not used
06.05 - not used
06.06 - not used
06.07 - not used
06.08 - not used
06.09 Overcurrent 1
06.10 Overcurrent 2
06.11 Overcurrent 3
06.12 - not used
06.13 - not used
06.14 Overload 1
06.15 Overload 2
06.16 - not used
06.17 - not used
06.18 - not used
06.19 - not used
06.20 - not used

Logical Command Variables: [08.00] - System Alarms

System alarms status commands, 08.01-08.10
These system alarms may be used as command variables in a logical output n to set parameters for customized
operations.
Number Function Note

08.01 Battery overvoltage (limit) 1
08.02 Battery overvoltage (limit) 2
08.03 Battery undervoltage (limit) 1
08.04 Battery undervoltage (limit) 2
TRUE = limit value reached
08.05 -
FALSE = alarm acknowledged
08.06 -
08.07 -
08.08 -
08.09 CANopen fault
08.10 - not used
08.11 - not used
08.12 - not used
08.13 - not used
08.14 - not used
08.15 - not used
08.16 - not used
08.17 - not used
08.18 - not used
08.19 - not used
08.20 - not used
Logical Command Variables: [09.00] - Discrete Inputs

Control discrete input commands, 09.01-09.08
The discrete inputs may be used as command variables in a logical output to set parameters for customized
operations.
Number Function Note

09.01 DI 1 (Discrete input [D1])
09.04 DI 4 (Discrete input [D4]) TRUE = logical "1" (delay times and NO/NC
09.05 DI 5 (Discrete input [D5]) parameters are ignored)
09.06 DI 6 (Discrete input [D6]) FALSE = logical "0" (alarm has been
09.07 DI 7 (Discrete input [D7]) acknowledged or immediately after TRUE
09.08 DI 8 (Discrete input [D8]) condition is no longer present , if the Control
09.09 DI 9 (Discrete input [D9]) is configured as alarm class)
09.13 - not used
09.14 - not used
09.15 - not used
09.16 - not used
09.17 - not used
09.18 - not used
09.19 - not used
09.20 - not used

Logical Command Variables: [11.00] - Time Functions

Time function commands, 11.01-11.10
Time functions may be used as command variables in a logical output.

11.01 Timer 1 (exceeded) see page 103
11.02 Timer 2 (exceeded) see page 103
11.03 Active weekday (equal to setting) see page 103
11.04 Active day (equal to setting) see page 103
11.05 Active hour (equal to setting) see page 103
11.06 Active minute (equal to setting) see page 103
11.07 Active second (equal to setting) see page 103
11.08 - not used
11.09 - not used
11.10 - not used
11.11 - not used
11.12 - not used
11.13 - not used
11.14 - not used
11.15 - not used
11.16 - not used
11.17 - not used
11.18 - not used
11.19 - not used
11.20 - not used
Logical Command Variables: [12.00] - External Discrete Inputs (Expansion

Board)
External discrete input commands, 12.01-12.16
Additional discrete inputs from an expansion board (i.e. IKD 1 extension board) may be used as command
variables in a logical output.

12.01 External discrete input 1 [D.E01]
12.06 External discrete input 6 [D.E06] TRUE = logical "1" (delay times and NO/NC
12.07 External discrete input 7 [D.E07] parameters are ignored)
12.08 External discrete input 8 [D.E08] FALSE = logical "0" (alarm has been
12.09 External discrete input 9 [D.E09] acknowledged, or immediately after TRUE
12.10 External discrete input 10 [D.E10] condition is no longer present, if the Control is
12.11 External discrete input 11 [D.E11] configured as alarm class)
12.17 - not used
12.18 - not used
12.19 - not used
12.20 - not used

Logical Command Variables: [13.00] - Internal Relay Output Status

Discrete output commands, 13.01-13.08
The discrete outputs may be used as command variables in a logical output.

13.01 Discrete output DO1 [R01]
TRUE = logical "1" (this condition indicates
the logical status of the internal relays)
FALSE = logical "0" (this condition indicates
the logical status of the internal relays)
13.10 - not used
13.11 - not used
13.12 - not used
13.13 - not used
13.14 - not used
13.15 - not used
13.16 - not used
13.17 - not used
13.18 - not used
13.19 - not used
13.20 - not used
Logical Command Variables: [14.00] - External Relay Outputs Status

Discrete output commands, 14.01-14.16
The external discrete outputs may be used as command variables in a logical output.

14.01 External discrete output DO1 [R01]
14.06 External discrete output DO6 [R06] TRUE = logical "1" (this condition indicates
14.07 External discrete output DO7 [R07] the logical status of the relays, which are
14.08 External discrete output DO8 [R08] connected via external expansion boards)
14.09 External discrete output DO9 [R09] FALSE = logical "0" (this condition indicates
14.10 External discrete output DO10 [R10] the logical status of the relays, which are
14.11 External discrete output DO11 [R11] connected via external expansion boards)
14.17 - not used
14.18 - not used
14.19 - not used
14.20 - not used

Logical Command Variables: [19.00] - ATS Status Flags

ATS status flags, 19.01-19.20
No. Name / Function Note

19.01 Source 1 OK (voltage and frequency are in range)
19.02 Source 1 voltage OK (in range)
19.03 Source 1 overvoltage (“fail” level exceeded)
19.04 Source 1 undervoltage (“fail” level exceeded)
19.05 Source 1 frequency OK (in range)
19.06 Source 1 overfrequency (“fail” level exceeded)
19.07 Source 1 underfrequency (“fail” level exceeded)
19.08 Source 1 voltage imbalance (“fail” level exceeded)
19.09 Source 1 rotation (field =) CCW
19.10 Source 1 rotation (field =) CW
19.11 Source 2 OK (voltage and frequency are in range)
19.12 Source 2 voltage OK (in range)
19.13 Source 2 overvoltage (“fail” level exceeded)
19.14 Source 2 undervoltage (“fail” level exceeded)
19.15 Source 2 frequency OK (in range)
19.16 Source 2 overfrequency (“fail” level exceeded)
19.17 Source 2 underfrequency (“fail” level exceeded)
19.18 Source 2 voltage imbalance (“fail” level exceeded)
19.19 Source 2 rotation (field =) CCW
19.20 Source 2 rotation (field =) CW
19.21 S1 failed status
19.22 S2 failed status
Logical Command Variables: [20.00] - ATS Status Flags

ATS status flags, 20.01-20.22

20.01 Status Flag: Elevator Pre Signal (is active)
20.02 Status Flag: Motor Load Disconnect (signal is active)
20.03 Status Flag: Load Test (is) active
20.04 Status Flag: No Load Test (is) active
20.05 Status Flag: S1 start signal
20.06 Status Flag: S2 start signal
20.07 Command: Close to S1
20.08 Command: Open from S1
20.09 Command: Close to S2
20.10 Command: Open from S2
20.11 Status Flag: Load shed (is active)
20.12 Status Flag: Shunt trip enable (is active)
20.13 Status Flag: S1 closed TRUE if S1 is closed and S2 is open
20.14 Status Flag: S2 closed TRUE if S2 is closed and S1 is open
20.15 Status Flag: S1 and S2 open
20.16 Status Flag: S1 and S2 closed
20.17 Status Flag: S1 is stabling (at the moment)
20.18 Status Flag: S2 is stabling (at the moment)
20.19 Status Flag: Dis. Ext. Sw. Inter. (disable external interlock)
20.20 Status Flag: Timer exe. Load Test Load test has automatically been triggered by
exercise timer
20.21 Status Flag: Timer exe. No Load No load test has automatically been triggered by
exercise timer
20.22 Sync check active This flag is set as soon as the DTSC-200 starts to do
In-phase monitoring, and resets after the In-Phase
transfer to the other source has been accomplished.

Logical Command Variables: [21.00] - ATS Alarms

ATS alarms, 21.01-21.20

21.01 Engine Alarm: Start fail S1
21.02 Engine Alarm: Start fail S2
21.03 Engine Alarm: Unintended Stop S1
21.04 Engine Alarm: Unintended Stop S2
21.05 Alarm: S1 phase rotation mismatch (failure present)
21.06 Alarm: S2 phase rotation mismatch (failure present)
21.07 Switch alarm: Fail to open (from switch position) S1
21.08 Switch alarm: Fail to open (from switch position) S2
21.09 Switch alarm: Fail to close (to switch position) S1
21.10 Switch alarm: Fail to close (to switch position) S2
21.11 Switch alarm: Mechanical fail (not plausible limit switch Delayed by 3463 ‘Limit switch failure delay time’
feedbacks have been detected by the DTSC-200)
21.12 In-Phase monitor alarm: In-phase timeout (the system was not
able to establish a "Sync" situation within the configured time)
21.13 Switch alarm: Overlap timeout (the contacts have been in a
"parallel" position for longer than the configured time)
21.14 Switch alarm: Out of phase XFR-Status
21.15 - not used
21.16 - not used
21.17 - not used
21.18 - not used
21.19 - not used
21.20 - not used
Logical Command Variables: [98.00] - LogicsManager Outputs

LogicsManager outputs, 98.01-98.20

98.01 LogicsManager "Inhibit ATS" is TRUE
98.02 LogicsManager "Inhib. XFR to S1" is TRUE
98.03 LogicsManager "Inhib. XFR to S2" is TRUE
98.04 LogicsManager "Remote peak shave" is TRUE
98.05 LogicsManager "Interruptible power rate provisions" is TRUE
98.06 LogicsManager "Gen-Gen enable" is TRUE
98.07 LogicsManager "Delayed mode activation" is TRUE
98.08 LogicsManager "Extended parallel time" is TRUE
98.09 LogicsManager "Load Test" is TRUE
98.10 LogicsManager "No Load Test" is TRUE
98.11 LogicsManager "Source 1 priority" is TRUE
98.12 LogicsManager "Source 2 priority" is TRUE
98.13 LogicsManager "External bypass" is TRUE
98.14 LogicsManager "Load shed" is TRUE
98.15 LogicsManager "Cld tr. enable" is TRUE (enable closed
transition)
98.16 LogicsManager "Service disconnect" is TRUE
98.17 - not used
98.18 - not used
98.19 - not used
98.20 - not used

Factory Setting
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The inputs, outputs, and internal flags, which may be programmed via the LogicsManager, have the following
factory default settings when delivered:
simple (function) extended (configuration) result
Factory Setting: Functions
Inhibit ATS
(parameter 12600 on page 38)
{0}  If TRUE, the unit is blocked against
{1}  automatic transfers.
{2} 
TRUE, if DI 5 is NOT energized
dependent
on DI 5
Inhibit XFR to Source 1

{0}  If TRUE, the unit is blocked against a
{1}  transfer to source 1.
{2} 
Prepared for: -
Deactivated by default FALSE
Inhibit XFR to Source 2

{0}  If TRUE, the unit is blocked against a
{1}  transfer to source 2.
{2} 
Prepared for: -

Remote peak shave

{0}  If TRUE, the remote peak shave
{1}  function will be performed.
{2} 
Prepared for: -
Interruptible power rates

{0}  If TRUE, the interruptible power rate
{1}  provision function will be performed.
{2} 
Prepared for: -
External timer bypass

{0}  If TRUE, all timers, which are
{1}  currently in progress, will be
{2}  bypassed.
Prepared for: - FALSE

Deactivated by default
Gen-Gen enable
{0} --- If TRUE, the gen-gen mode will be
{1} --- enabled.
{2} 
Prepared for: -

Source 1 priority
{0}  If TRUE, source 1 is preferred.
{1} 
{2}  Prepared for: -
Activated by default
TRUE
Source 2 priority
{0}  If TRUE, source 2 is preferred.
{1} 
FALSE
Extended parallel time

{0}  If TRUE, the transfer switch remains
{1} --- in overlap position.
{2} 
Prepared for: -
Load shed
{0}  If TRUE, a load shed from the non-
{1} --- preferred source will be performed.
{2} 
Prepared for: -

Delayed mode active

{0}  If TRUE, the transfer switch type will
{1}  be set to Delayed.
{2} 
Prepared for: -
Load test
{0}  If TRUE, a load test will be
{1}  performed.
{2} 
Prepared for: -
No load test
{0}  If TRUE, a no-load test will be
{1}  performed.
{2} 
Prepared for: -

External acknowledge
{0}  If TRUE, alarms are acknowledged
{1}  from an external source.
{2} 
Prepared for: -
Remote acknowledgement FALSE
Reset limit switch failure

{0}  If TRUE, limit switch failure is
{1}  acknowledged from an external
{2}  source.
FALSE

Factory Setting: Relay Outputs
Relay {x} [R0x]; {x} = 1 to 4

(parameters 12, 12110, 12310, and 12320 on page 99)
{0}  If TRUE, relay 2 will be energized.
{1} 
FALSE
Relay 5 [R05]
{1} 
{2}  True, if the Source 2 start signal is dependent
issued on Logics
Command
Variable
[20.06]
Relay 6 [R06]
{1} 
{2}  True, if the command: Close to dependent
Source 1 is issued on Logics
Command
Variable
[20.07]
Relay 7 [R07]
{1} 
{2}  True, if the command: Close to dependent
Command
Variable
[20.09]

Relay 8 [R08]
{1} 
{2}  True, if the command: Open from dependent
Command
Variable
[20.08]
Relay 9 [R09]
{1} 
{2}  True, if the command: Open from dependent
Command
Variable
[20.10]
External discrete output {x] [REx{x}] - free (external expansion card, if connected; {x} = 1-16)
(refer to Table 3-12 on page 99 for the parameter IDs of the parameters for external DOs 1 through 16)
{0}  If TRUE, the external relay {x} will
{1}  be energized, if this is connected
{2} 
Prepared for: -

Factory Setting: Internal Flags
Internal flag {x}; {x} = 1 to 7

(refer to Table 3-13 on page 102 for the parameter IDs of the parameters for internal flags 1 through 7)
{0}  If TRUE, the internal flag {x} will be
{1}  enabled.
{2} 
Prepared for: -
Note:
Internal flag 1 is used as default
setting in all logical outputs.
Internal flag 8
{0}  If TRUE, the internal flag 8 will be
{1}  enabled. dependent
{2}  on Logics
TRUE, once the configured time 1 has Command
been reached [11.01], and the Variables
configured time 2 [11.02] has not [11.01],
been reached as well, if the current [11.02], and
day is the configured day [11.03] [11.03]

Discrete Inputs
[D1] {0}
{1} Reply from ATS switch: Breaker in source 1 position
{2}
[D2] {0}
{1} Reply from ATS switch: Breaker in source 2 position
{2}
[D3] {0}
{1} Reply from ATS switch: Breaker in source 1 open position
{2}
[D4] {0}
{1} Reply from ATS switch: Breaker in source 2 open position
{2}
[D5] {0}
{1} freely configurable discrete input (pre-configured to Inhibit ATS)
{2}
[D6] {0}
{1} freely configurable discrete input (unassigned)
{2}
[D7] {0}
{2}
[D8] {0}
{2}
[D9] {0}
{2}
[D10] {0}
{2}
[D11] {0}
{2}
[D12] {0}
{2}
NOTE
The discrete inputs for the breaker position reply messages (DIs 1 through 4) are fixed to N.C. and are
evaluated as N.C., i.e. the breaker is considered as "in position" if the respective DI is de-energized.

Appendix B.
List Of Parameters
Unit number P/N _____________________________ Rev _______________________________
Version DTSC- ________________________________________________________________
Project _____________________________________________________________________
Serial number S/N _______________ Date ______________________________
Par.
Parameter Setting range Default value Customer setting Data type
ID.
MAIN MENU
English / Deutsch / UNSIGNED 16
Language English
Espacñol / Polski / Russian
10416 Password 0000 to 9999 --- UNSIGNED 16
EVENT LOG
1706 Clear event log YES / NO NO Y N Y N UNSIGNED 16
MEASUREMENT
1750 Rated system frequency 50/60 Hz 50 Hz UNSIGNED 16
1774 Rated voltage S1 50 to 650000 V 400 V UNSIGNED 32
1772 Rated voltage S2 50 to 650000 V 400 V UNSIGNED 32
3Ph 4W  3Ph4W  3Ph4W
1862 S1 voltage measuring 3Ph 4W UNSIGNED 16
1861 S2 voltage measuring 3Ph 4W UNSIGNED 16
Phase - N  p-n  p-n
1858 1Ph2W voltage measuring Ph - Ph UNSIGNED 16
Ph - Ph  p-p  p-p
 CW  CW
1859 1Ph2W phase rotation CW / CCW CW UNSIGNED 16
 CCW  CCW
L1 L2 L3  L123  L123
Phase L1  Ph.L1  Ph.L1
1863 S1 Load current measuring L1 L2 L3 UNSIGNED 16
L1 L2 L3  L123  L123
1860 S2 Load current measuring L1 L2 L3 UNSIGNED 16
1752 Rated active power [kW] 0.5 to 99999.9 kW 200.0 kW UNSIGNED 32
1754 Rated current 5 to 32000 A 300 A UNSIGNED 16
Transformer
1819 S1 voltage transf. primary 50 to 650000 V 400 V UNSIGNED 32
1818 S1 voltage transf. secondary 50 to 480 V 400 V UNSIGNED 16
1816 S2 voltage transf. primary 50 to 650000 V 400 V UNSIGNED 32
1815 S2 voltage transf. secondary 50 to 480 V 400 V UNSIGNED 16
1821 Load current transformer 1 to 32000/5 A 500/5 A UNSIGNED 16
1822 Load current transformer 1 to 32000/1 A 500/1 A UNSIGNED 16

Par.
ID.
APPLICATION
Util-Gen  Util-Gen  Util-Gen
4148 Application mode Gen-Gen Util-Gen  Gen-Gen  Gen-Gen UNSIGNED 16
Util-Util  Util-Util  Util-Util
4146 Transfer Commit YES / NO NO Y N Y N UNSIGNED 16
4149 S1 start delay time 0 to 300 s 10 s UNSIGNED 16
3330 S2 start delay time 0 to 300 s 10 s UNSIGNED 16
3333 S1 source stable time 1 to 6500 s 10 s UNSIGNED 16
3332 S2 source stable time 1 to 6500 s 10 s UNSIGNED 16
2804 S1 outage delay 0.1 to 10.0 s 1.0 s UNSIGNED 16
2803 S2 outage delay 0.1 to 10.0 s 1.0 s UNSIGNED 16
3343 S1 cooldown time 1 to 6500 s 20 s UNSIGNED 16
3344 S2 cooldown time 1 to 6500 s 20 s UNSIGNED 16
4496 Transfer delay timer S1->S2 0 to 6500 5 UNSIGNED 16
4497 Transfer delay timer S2->S1 0 to 6500 5 UNSIGNED 16
12600 Inhibit ATS see descr. in LogicsManager chap. starting p. 134; default: (!09.05 & 1) & 1 Logman
12610 Inhib. XFR to S1 see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
12620 Inhib. XFR to S2 see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
12630 Remote peak shave see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
12660 Int. pow. rates see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
12820 Ext. bypass see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
12830 Gen-Gen enable see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
Elevator Pre Signal
4490 Elevator Pre signal ON / OFF OFF 1 0 1 0 UNSIGNED 16
4491 Elevator pre-signal duration 1 to 6500 s 5s UNSIGNED 16
Motor Load Disconnect
4550 Motor Load Disconnect ON / OFF OFF 1 0 1 0 UNSIGNED 16
S1->S2  S1->S2  S1->S2
4553 Active direction S2->S1 S1->S2  S2->S1  S2->S1 UNSIGNED 16
Both  Both  Both
4551 Disconnect time S1->S2 1 to 6500 s 5s UNSIGNED 16
4552 Disconnect time S2->S1 1 to 6500 s 5s UNSIGNED 16
Source Priority
12680 S1 Priority see descr. in LogicsManager chap. starting page 134; default: (1 & 1) & 1 Logman
12810 S2 Priority see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
12860 Ext. para.time see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
12870 Load shed see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
12890 Service Disconnect see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
BREAKER
Standard  Standard  Standard
3424 Transfer switch type Delayed Standard  Delayed  Delayed UNSIGNED 16
Closed  Closed  Closed
3434 Use limit sw. OPEN replies YES / NO YES Y N Y N UNSIGNED 16
12850 Delayed mode act. see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
3426 Neutral time S2->S1 1 to 6500 s 3s UNSIGNED 16
3425 Neutral time S1->S2 1 to 6500 s 3s UNSIGNED 16
3428 Limit switch reply timeout 0.1 to 99.9 s 1.0 s UNSIGNED 16
3429 Wait time until next XFR attempt 0.1 to 99.9 s 3.0 s UNSIGNED 16
3427 Max. of transfer attempts 0 to 10 2 UNSIGNED 16
TESTMODES
12640 Load Test see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman
12650 No Load Test see descr. in LogicsManager chap. starting page 134; default: (0 & 1) & 1 Logman

Par.
ID.
MONITORING
1756 Time until horn reset 0 to 1000 s 180 s UNSIGNED 16
12490 External acknowledge see descr. in LogicsManager chap. starting page 134; default: (0 & 0)+ 0 Logman
3430 Limit switch monitoring ON / OFF OFF 1 0 1 0 UNSIGNED 16
3463 Limit switch failure delay 0.00 to 10.00 s 0.02 s UNSIGNED 16
12981 Reset limit switch failure ON / OFF OFF 1 0 1 0 UNSIGNED 16
S1 Monitoring
1787 Voltage monitoring S1 Ph – Ph/ Phase - N Ph - Ph 3 4 3 4 UNSIGNED 16
4450 S1 undervoltage restore 50.0 to 125.0 % 90.0 % UNSIGNED 16
4451 S1 undervoltage fail 50.0 to 125.0 % 80.0 % UNSIGNED 16
4452 S1 underfrequency monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
4453 S1 underfrequency restore 50.0 to 130.0 % 95.0 % UNSIGNED 16
4454 S1 underfrequency fail 50.0 to 130.0 % 90.0 % UNSIGNED 16
4455 S1 overvoltage monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
4456 S1 overvoltage restore 50.0 to 125.0 % 105.0 % UNSIGNED 16
4457 S1 overvoltage fail 50.0 to 125.0 % 110.0 % UNSIGNED 16
4458 S1 overfrequency monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
4459 S1 overfrequency restore 50.0 to 130.0 % 102.0 % UNSIGNED 16
4460 S1 overfrequency fail 50.0 to 130.0 % 105.0 % UNSIGNED 16
4461 S1 voltage imbalance monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
4462 S1 volt. imbalance restore 0.5 to 99.9 % 8.0 % UNSIGNED 16
4463 S1 volt. imbalance fail 0.5 to 99.9 % 10.0 % UNSIGNED v
3914 Delay 0.02 to 99.99 s 5.00 s UNSIGNED 16
4562 S1 phase rotation ON / OFF ON 1 0 1 0 UNSIGNED 16
CW  CW  CW
4563 S1 phase rotation CW UNSIGNED 16
CCW  CCW  CCW
S2 Monitoring
1786 Voltage monitoring S2 Ph - Ph/ Phase - N Ph - Ph 3 4 3 4 UNSIGNED 16
4465 S2 undervoltage restore 50.0 to 125.0 % 90.0 % UNSIGNED 16
4466 S2 undervoltage fail 50.0 to 125.0 % 80.0 % UNSIGNED 16
4467 S2 underfrequency monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
4468 S2 underfrequency restore 50.0 to 130.0 % 95.0 % UNSIGNED 16
4469 S2 underfrequency fail 50.0 to 130.0 % 90.0 % UNSIGNED 16
4470 S2 overvoltage monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
4471 S2 overvoltage restore 50.0 to 125.0 % 105.0 % UNSIGNED 16
4472 S2 overvoltage fail 50.0 to 125.0 % 110.0 % UNSIGNED 16
4473 S2 overfrequency monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
4474 S2 overfrequency restore 50.0 to 130.0 % 102.0 % UNSIGNED 16
4475 S2 overfrequency fail 50.0 to 130.0 % 105.0 % UNSIGNED 16
4476 S2 voltage imbalance monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
4477 S2 volt. imbalance restore 0.5 to 99.9 % 8.0 % UNSIGNED 16
4478 S2 volt. imbalance fail 0.5 to 99.9 % 10.0 % UNSIGNED 16
4566 S2 phase rotation ON / OFF ON 1 0 1 0 UNSIGNED 16
CW  CW  CW
4567 S2 phase rotation CW UNSIGNED 16
CCW  CCW  CCW
In-Phase Monitoring
4570 In-Phase monitor ON / OFF OFF 1 0 1 0 UNSIGNED 16
8820 Connect synchronous mains ON / OFF OFF UNSIGNED 16
8821 Max. phase angle 0 to 20° 2 UNSIGNED 16
4585 In-Phase check for DLY trans. ON / OFF OFF 1 0 1 0 UNSIGNED 16
4571 Voltage window 0.50 to 20.00 % 1.00 % UNSIGNED 16
4572 Positive frequency window 0.02 to 0.49 Hz 0.18 Hz SIGNED 16
4573 Negative frequency window -0.02 to -0.49 Hz -0.18 Hz SIGNED 16
0.10 s
4577 Max. overlap time 0.1 to 9.99 s UNSIGNED 16
(see page 81)
4578 Open trans. switch reac. time 15 to 300 ms 30 ms UNSIGNED 16
4583 Closed trans. switch reac. time 15 to 300 ms 30 ms UNSIGNED 16
4581 Vector group angle adjustment -180° to 180° 0° SIGNED 16
4576 In-phase timeout after 0 to 6500 s 60 s UNSIGNED 16
Abort  Abort  Abort
4582 Outcome on In-phase timeout Abort UNSIGNED 16
Delayed  Delayed  Delayed
4584 Ext. permit for cld. trans. ON / OFF OFF 1 0 1 0 UNSIGNED 16

Par.
ID.
MONITORING
Load Monitoring
Overcurrent Monitoring level 1
2200 Monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
2204 Limit 50.0 to 300.0 % 110.0 % UNSIGNED 16
2202 Self acknowledge YES / NO NO Y N Y N UNSIGNED 16
Overload Monitoring level 1
Overload Monitoring level 2
Engine Monitoring
Start Failure S1 Monitoring
3341 S1 Start fail delay time 1 to 6500 s 8s UNSIGNED 16
Start Failure S2 Monitoring
3331 S2 Start fail delay time 1 to 6500 s 8s UNSIGNED 16
Battery Voltage Monitoring
Overvoltage Monitoring level 1
3454 Limit 8.0 to 42.0 V 32.0 V UNSIGNED 16
3452 Self acknowledge level 1 YES / NO NO Y N Y N UNSIGNED 16
Overvoltage Monitoring level 2
3456 Monitoring ON / OFF OFF 1 0 1 0 UNSIGNED 16
Undervoltage Monitoring level 1
Undervoltage Monitoring level 2
CANopen Interface Monitoring
3150 Monitoring ON / OFF OFF 1 0 1 0 UNSIGNED 16

Par.
ID.
DISCRETE INPUTS
Discrete Input 1
N.O.
DI 1 operation N.C. UNSIGNED 16
N.C.
DI 1 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Discrete Input 2
N.O.
N.C.
Discrete Input 3
N.O.
N.C.
Discrete Input 4
N.O.
N.C.
Discrete Input 5
N.O.  N.O.  N.O.
1281 DI 5 operation N.O. UNSIGNED 16
N.C.  N.C.  N.C.
1280 DI 5 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Discrete Input 6
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
Discrete Input 7
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
Discrete Input 8
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
Discrete Input 9
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
Discrete Input 10
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
Discrete Input 11
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
Discrete Input 12
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
External Discrete Input 1
N.O.  N.O.  N.O.
16001 Operation N.O. UNSIGNED 16
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.

Par.
ID.
DISCRETE INPUTS
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.
N.O.  N.O.  N.O.
N.C.  N.C.  N.C.

Par.
ID.
DISCRETE OUTPUTS
12 Relay 1 see descr. in LogicsManager chap. starting page 139; default: (0 & 1) & 1 Logman
12130 Relay 5 see descr. in LogicsManager chap. starting p. 139; default: (!20.06 & 1) & 1 Logman
12140 Relay 6 see descr. in LogicsManager chap. starting page 139; default: (20.07 & 1) & 1 Logman
12330 External DO 1 see descr. in LogicsManager chap. starting page 139; default: (0 & 1) & 1 Logman
COUNTERS
2515 Counter value preset 0 to 99999999 UNSIGNED 32
2514 S1 active power [0.00MWh] YES / NO NO Y N Y N UNSIGNED 16
2516 S1 reactive power [0.00Mvarh] YES / NO NO Y N Y N UNSIGNED 16
2576 Transfers to S1 0 to 65535 UNSIGNED 16
2510 S2 active power [0.00MWh] YES / NO NO Y N Y N UNSIGNED 16
2511 S2 reactive power [0.00Mvarh] YES / NO NO Y N Y N UNSIGNED 16
2577 Transfers to S2 0 to 65535 UNSIGNED 16
LOGICSMANAGER
Internal Flags
12230 Flag 1 see descr. in LogicsManager chap. starting page 139; default: (0 & 1) & 1 Logman
12300 Flag 8 see descr. in LogicsManager ch. start. p. 139; def.: (11.01 & !11.02) & 11.03 Logman
Set Timers
1652 Setpoint 1: Hour 0 to 23 h 8h UNSIGNED 8
1651 Setpoint 1: Minute 0 to 59 min 0 min UNSIGNED 8
1650 Setpoint 1: Second 0 to 59 s 0s UNSIGNED 8
1657 Setpoint 2: Hour 0 to 23 h 17 h UNSIGNED 8
1656 Setpoint 2: Minute 0 to 59 min 0 min UNSIGNED 8
1655 Setpoint 2: Second 0 to 59 s 0s UNSIGNED 8
1663 Active day 1 to 31 1 UNSIGNED 8
1662 Active hour 0 to 23 h 12 h UNSIGNED 8
1661 Active minute 0 to 59 min 0 min UNSIGNED 8
1660 Active second 0 to 59 s 0s UNSIGNED 8
1670 Monday active YES / NO YES Y N Y N UNSIGNED 16
1671 Tuesday active YES / NO YES Y N Y N UNSIGNED 16
1672 Wednesday active YES / NO YES Y N Y N UNSIGNED 16
1673 Thursday active YES / NO YES Y N Y N UNSIGNED 16
1674 Friday active YES / NO YES Y N Y N UNSIGNED 16
1675 Saturday active YES / NO NO Y N Y N UNSIGNED 16
1676 Sunday active YES / NO NO Y N Y N UNSIGNED 16

Par.
ID.
COMMUNICATION INTERFACES
1702 Device number 1 to 127 1 UNSIGNED 16
CAN Interfaces
20/50/100/125/250/500/
3156 Baudrate 125 kBd UNSIGNED 16
800/1000 kBd
CANopen Interfaces
9000 CAN-Open Master YES / NO YES Y N Y N UNSIGNED 16
9120 Producer Heartbeat Time 20 to 65530 ms 2000 ms UNSIGNED 16
9100 COB-ID SYNC Message 1 to FFFFFFFF 80 UNSIGNED 32
15134 Configure external devices YES / NO NO Y N Y N UNSIGNED 16
Additional Server SDOs
9020 2nd Client->Server COB-ID (rx) 1 to FFFFFFFF 80000601 UNSIGNED 32
9022 2nd Server->Client COB-ID (tx) 1 to FFFFFFFF 80000581 UNSIGNED 32
9024 3rd Client->Server COB-ID (rx) 1 to FFFFFFFF 80000602 UNSIGNED 32
9026 3rd Server->Client COB-ID (tx) 1 to FFFFFFFF 80000582 UNSIGNED 32
9028 4th Client->Server COB-ID (rx) 1 to FFFFFFFF 80000603 UNSIGNED 32
9030 4th Server->Client COB-ID (tx) 1 to FFFFFFFF 80000583 UNSIGNED 32
9032 5th Client->Server COB-ID (rx) 1 to FFFFFFFF 80000604 UNSIGNED 32
9034 5th Server->Client COB-ID (tx) 1 to FFFFFFFF 80000584 UNSIGNED 32
Receive PDO 1
9300 COB-ID 1 to FFFFFFFF 201 UNSIGNED 32
no func.  no func.  no func.
1st IKD  1st IKD  1st IKD
9050 Function no func. UNSIGNED 16
2nd IKD  2nd IKD  2nd IKD
BK 16DIDO  BK 16  BK 16
9060 Node-ID of the device 1 to 127 2 UNSIGNED 16
9070 RPDO-COB-ID ext. device 1 1 to FFFFFFFF 181 UNSIGNED 32
Receive PDO 2
no func.  no func.  no func.
1st IKD  1st IKD  1st IKD
9051 Function no func. UNSIGNED 16
2nd IKD  2nd IKD  2nd IKD
BK 16DIDO  BK 16  BK 16
9061 Node-ID of the device 1 to 127 3 UNSIGNED 16
9072 RPDO-COB-ID ext. device 2 1 to FFFFFFFF 182 UNSIGNED 32
Transmit PDO 1
9602 Transmission type 0 to 255 255 UNSIGNED 8
9604 Event-timer 20 to 65000 ms 20 ms UNSIGNED 16
9609 Number of mapped objects 0 to 4 4 UNSIGNED 8
9605 1.Mapped Object 0 to 65535 8001 UNSIGNED 16
Transmit PDO 2

Par.
ID.
COMMUNICATION INTERFACES
Transmit PDO 3
Transmit PDO 4
Serial Interface 1
2400 Bd  2400 Bd  2400 Bd
4800 Bd  4800 Bd  4800 Bd
9600 Bd  9600 Bd  9600 Bd
14.4 kBd  14.4 kBd  14.4 kBd
3163 Baudrate 9600 Bd UNSIGNED 16
19.2 kBd  19.2 kBd  19.2 kBd
38.4 kBd  38.4 kBd  38.4 kBd
56 kBd  56 kBd  56 kBd
115 kBd  115 kBd  115 kBd
No  No  No
3161 Parity Even No  Even  Even UNSIGNED 16
Odd  Odd  Odd
One  One  One
3162 Stop Bits One UNSIGNED 16
Two  Two  Two
Serial Interface 2
2400 Bd
4800 Bd  9600 Bd  9600 Bd
9600 Bd  14.4 kBd  14.4 kBd
14.4 kBd  19.2 kBd  19.2 kBd
3170 Baudrate 19200 Bd UNSIGNED 16
19.2 kBd  38.4 kBd  38.4 kBd
38.4 kBd  56 kBd  56 kBd
56 kBd  115 kBd  115 kBd
115 kBd
No  No  No
3171 Parity Even No  Even  Even UNSIGNED 16
Odd  Odd  Odd
One  One  One
3172 Stop Bits One UNSIGNED 16
Two  Two  Two
Fullduplex  Full  Full
3173 Full-, halfduplex mode Fullduplex UNSIGNED 16
Halfduplex  Half  Half
3185 ModBus Slave ID 0 to 255 1 UNSIGNED 16
3186 Modbus Reply delay time 0.00 to 1.00 s 0.00 s UNSIGNED 16

Par.
ID.
SYSTEM PARAMETER
Display Backlight
On  On  On
Off  Off  Off
4556 Configure display backlight On UNSIGNED 16
Auto  Auto  Auto
Key actv.  Key act.  Key act.
4557 Time until backlight shutdown 1 to 999 s 600 s UNSIGNED 16
Daylight saving time
On  On  On
4591 Daylight saving time Off UNSIGNED 16
Off  Off  Off
4594 DST begin time 0 to 23 2 UNSIGNED 8
Sunday / Monday / Sunday
Tuesday / Wednesday /
4598 DST begin weekday UNSIGNED 16
Thursday / Friday /
Saturday
1st / 2nd / 3rd / 4th / Last / 1st
4592 DST begin nth. weekday LastButOne / LastButTwo UNSIGNED 16
/ LastButThree
4593 DST begin month 1 to 12 3 UNSIGNED 8
4597 DST end time 0 to 23 3 UNSIGNED 8
Sunday / Monday / Sunday
Tuesday / Wednesday /
4599 DST end weekday UNSIGNED 16
Thursday / Friday /
Saturday
1st / 2nd / 3rd / 4th / Last / 4th
4595 DST end nth. weekday LastButOne / LastButTwo UNSIGNED 16
/ LastButThree
4596 DST end month 1 to 12 10 UNSIGNED 8
Password System
10405 Code level display 0000 to 9999 --- UNSIGNED 16
10407 Code level CAN port 0000 to 9999 --- UNSIGNED 16
10406 Code level serial port / DPC 0000 to 9999 --- UNSIGNED 16
10411 Supercomm. level code 0001 to 9999 --- UNSIGNED 16
10412 Temp. supercomm. level code 0001 to 9999 --- UNSIGNED 16
10413 Commissioning level code 0001 to 9999 --- UNSIGNED 16
10414 Temp. commissioning level code 0001 to 9999 --- UNSIGNED 16
10415 Basic level code 0001 to 9999 --- UNSIGNED 16
1703 Factory settings YES / NO NO Y N Y N UNSIGNED 16
1704 Factory settings DPC/RS232 YES / NO NO Y N Y N UNSIGNED 16
1705 Factory settings CAN YES / NO NO Y N Y N UNSIGNED 16
1701 Set default values YES / NO NO Y N Y N UNSIGNED 16
10500 Start Bootloader 00000 to 99999 --- UNSIGNED 16
Clock Set
1710 Hour 0 to 23 h --- UNSIGNED 8
1709 Minute 0 to 59 min --- UNSIGNED 8
1708 Second 0 to 59 s --- UNSIGNED 8
1698 Transfer time to clock YES / NO NO Y N Y N UNSIGNED 16
1711 Day 1 to 31 --- UNSIGNED 8
1712 Month 1 to 12 --- UNSIGNED 8
1713 Year 0 to 99 --- UNSIGNED 8
1699 Transfer date to clock YES / NO NO Y N Y N UNSIGNED 16
Version
900 Serial number Info --- UNSIGNED 8
950 Boot item number Info --- UNSIGNED 8
960 Boot revision Info --- UNSIGNED 8
965 Boot version Info --- UNSIGNED 8
930 Program item number Info --- UNSIGNED 8
940 Program revision Info --- UNSIGNED 8
945 Program version Info --- UNSIGNED 8
NOTE
All parameters shaded in gray color are fixed parameters and cannot be configured by the operator.

Appendix C.
Service Options
Product Service Options

≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The following factory options are available for servicing Woodward equipment, based on the standard
Woodward Product and Service Warranty (5-01-1205) that is in effect at the time the product is purchased from
Woodward or the service is performed. If you are experiencing problems with installation or unsatisfactory
performance of an installed system, the following options are available:
• Consult the troubleshooting guide in the manual.

• Contact Woodward technical assistance (see "How to Contact Woodward" later in this chapter) and discuss
your problem. In most cases, your problem can be resolved over the phone. If not, you can select which
course of action you wish to pursue based on the available services listed in this section.
Returning Equipment For Repair

≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
If a control (or any part of an electronic control) is to be returned to Woodward for repair, please contact
Woodward in advance to obtain a Return Authorization Number. When shipping the unit(s), attach a tag with the
following information:
• name and location where the control is installed;

• name and phone number of contact person;
• complete Woodward part numbers (P/N) and serial number (S/N);
• description of the problem;
• instructions describing the desired repair.
CAUTION
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.

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.
Return Authorization Number RAN

When returning equipment to Woodward, please telephone and ask for the Customer Service Department in
Stuttgart [+49 (0) 711 789 54-510]. They will help expedite the processing of your order through our distributors
or local service facility. To expedite the repair process, contact Woodward in advance to obtain a Return
Authorization Number, and arrange for issue of a purchase order for the unit(s) to be repaired. No work can be
started until a purchase order is received.
NOTE
We highly recommend that you make arrangement in advance for return shipments. Contact a
Woodward customer service representative at +49 (0) 711 789 54-510 for instructions and for a
Return Authorization Number.
Replacement Parts
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
When ordering replacement parts for controls, include the following information:
• the part numbers P/N (XXXX-XXX) that is on the enclosure nameplate;
• the unit serial number S/N, which is also on the nameplate.

How To Contact Woodward

≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Please contact following address if you have questions or if you want to send a product for repair:
Woodward GmbH
Handwerkstrasse 29
70565 Stuttgart - Germany
Phone: +49 (0) 711 789 54-510 (8.00 - 16.30 German time)
Fax: +49 (0) 711 789 54-101
e-mail: SalesPGD_EUROPE@woodward.com
stgt-info@woodward.com
For assistance outside Germany, please consult our worldwide directory on Woodward’s website
(www.woodward.com) for the name of your nearest Woodward distributor or service facility.
[For worldwide directory information, go to www.woodward.com/ic/locations.]

Engineering Services
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Woodward Industrial Controls Engineering Services offers the following after-sales support for Woodward
products. For these services, you can contact us by telephone, by e-mail, or through the Woodward website.
• Technical support
• Product training
• Field service during commissioning
Technical Support is available through our many worldwide locations, through our authorized distributors,
depending on the product. This service can assist you with technical questions or problem solving during normal
business hours. For technical engineering support, please contact us via our local phone numbers, e-mail us, or
use our website and reference technical support.
Product Training is available on-site from several of our worldwide facilities or at your location, depending on
the product. This training, conducted by experienced personnel, will assure that you will be able to maintain
system reliability and availability. For information concerning training, please contact us via our local phone
numbers, e-mail us, or use our website and reference customer training.
Field Service engineering on-site support is available, depending on the product and location, from one of many
worldwide Woodward offices or authorized distributors. Field engineers are experienced on both Woodward
products as well as on much of the non-Woodward equipment with which our products interface. For field
service engineering assistance, please contact us via our local phone numbers, e-mail us, or use our website and
reference field service.

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:
Contact
Your company ____________________________________________________
Your name _______________________________________________________
Phone number ____________________________________________________
Fax number ______________________________________________________
Control (see name plate)

Unit no. and revision: P/N: ____________________ REV: _____________
Unit type DTSC-200 __________________________________
Serial number S/N _______________________________________
Description of your problem

_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
Please be sure you have a list of all parameters available. You can print this using ToolKit Additionally you can
save the complete set of parameters (standard values) and send them to our Service department via e-mail.

We appreciate your comments about the content of our publications.
Please send comments to: stgt-documentation@woodward.com
Please include the manual number from the front cover of this publication.
Designed in Germany
Woodward GmbH
Handwerkstrasse 29 - 70565 Stuttgart - Germany
Phone +49 (0) 711 789 54-510 • Fax +49 (0) 711 789 54-101
SupportPGD_EMEA@woodward.com
Homepage
http://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/e-mail information

for all locations is available on our website (www.woodward.com).
2014/01/Stuttgart

Woodward DTSC-200 Configuration

Uploaded by

Copyright:

Available Formats

Woodward DTSC-200 Configuration

Uploaded by

Document Information

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

Woodward DTSC-200 Configuration

Uploaded by

Copyright:

Available Formats

37483C

Page 2/158 © Woodward

Rev. Date Editor Changes

Changes to previous software version

CHAPTER 1. GENERAL INFORMATION ....................................................................................... 8

© Woodward Page 3/158

CHAPTER 3. PARAMETERS ..................................................................................................... 22

Logical Command Variables: [09.00] - Discrete Inputs ............................................................. 129

© Woodward Page 5/158

Illustrations And Tables

Page 6/158 © Woodward

© Woodward Page 7/158

Type English German

Page 8/158 © Woodward

Configuration Via The Front Panel

© Woodward Page 9/158

Install ToolKit Software

Minimum system requirements for ToolKit:

• Microsoft Windows® 7, Vista SP1 or later, XP (32- & 64-bit);

Page 10/158 © Woodward

Install ToolKit Configuration Files

© Woodward Page 11/158

Starting ToolKit Software

Page 12/158 © Woodward

Configure ToolKit Software

2. The options window will be displayed

a. Adjust the default locations of the configuration files

© Woodward Page 13/158

Connect ToolKit and the DTSC-200 Unit

6. The connect dialog window will open if the option is enabled.

a. Select the COM port that is connected to the communication cable.

9. If the device is security enabled, the Login dialog will appear.

Page 14/158 © Woodward

<?xml version="1.0" encoding="utf-8"?>

© Woodward Page 15/158

View DTSC-200 Data with ToolKit

Figure 2-1: ToolKit - visualization screen

Figure 2-2: ToolKit - analog value trending screen

Page 16/158 © Woodward

Configure the DTSC-200 with ToolKit

Figure 2-3: ToolKit - configuration screen

© Woodward Page 17/158

Signal and Command Abbreviations

Page 18/158 © Woodward

© Woodward Page 19/158

Function Of The Inputs And Outputs

Page 20/158 © Woodward

LogicsManager Relay {all} programmable to relay [R4], terminals 35/36/37

Start engine {all} pre-defined to relay [R5], terminals 39/40/41

© Woodward Page 21/158

Page 22/158 © Woodward

Language Set language English / Deutsch / Español / Polski / Russian

Code level CL0 (User Level) Standard password = none

Code level CL1 (Basic Level) Standard password = "0 0 0 1"

Code level CL2 (Temporary Commissioning Level) No standard password available

Code level CL3 (Commissioning Level) Standard password = "0 0 0 3"

Password Password: Entry via front panel 0000 to 9999

© Woodward Page 23/158

Figure 3-1: Event history- display

Event history display Event history: Display event history Info