DTSC-200A ATS Controller: Configuration
37940A
DTSC-200A
ATS Controller - Configuration
Configuration
Release 1.0 - 0
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:
[Link]
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.
Revision History
Content
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...............................................................................................................................41
Figure 3-4: Elevator pre-signal - example 1......................................................................................................................................44
Figure 3-5: Elevator pre-signal - example 2......................................................................................................................................44
Figure 3-6: Elevator pre-signal - example 3......................................................................................................................................44
Figure 3-7: Source priority selection - S1 preferred .........................................................................................................................48
Figure 3-8: Source priority selection - S2 preferred .........................................................................................................................48
Figure 3-9: Load shed relay wiring - standard transition switch .....................................................................................................52
Figure 3-10: Load shed relay wiring - delayed or closed transition switch ....................................................................................52
Figure 3-11: Open transition switch - connected to source 1...........................................................................................................55
Figure 3-12: Open transition switch - connected to source 2...........................................................................................................55
Figure 3-13: Delayed transition switch - connected to source 1 ......................................................................................................56
Figure 3-14: Delayed transition switch - neutral position ................................................................................................................56
Figure 3-15: Delayed transition switch - connected to source 2 ......................................................................................................56
Figure 3-16: Closed transition switch - connected to source 1 ........................................................................................................57
Figure 3-17: Closed transition switch - neutral position ..................................................................................................................57
Figure 3-18: Closed transition switch - connected to source 1 and 2 (overlap position) ...............................................................57
Figure 3-19: Closed transition switch - connected to source 2 ........................................................................................................57
Figure 3-20: Breaker - transition pulse..............................................................................................................................................61
Figure 3-21: Test modes - load test configured for timer exerciser.................................................................................................66
Figure 3-22: Test modes - no-load test configured for timer exerciser ...........................................................................................66
Figure 3-23: Test modes - parameter IDs of the timer exercisers....................................................................................................67
Figure 3-24: Test modes - configuring exerciser 1 for a daily exercise ..........................................................................................68
Figure 3-25: Test modes - configuring exerciser 2 for a weekly exercise ......................................................................................68
Figure 3-26: Test modes - configuring exerciser 3 for a 14-day exercise.......................................................................................68
Figure 3-27: Test modes - configuring exerciser 4 for a one event exercise ..................................................................................69
Figure 3-28: Test modes - display screen with pending exercise event ..........................................................................................69
Figure 3-29: Inphase monitoring .......................................................................................................................................................81
Figure 3-30: Switch reaction time......................................................................................................................................................86
Figure 3-31: Monitoring - load time-overcurrent .............................................................................................................................90
Figure 3-32: Monitoring - overload ...................................................................................................................................................92
Figure 3-33: Monitoring - battery overvoltage .................................................................................................................................95
Figure 3-34: Monitoring - battery undervoltage ...............................................................................................................................97
Figure 3-35: Discrete inputs - control inputs - operation logic ......................................................................................................100
Figure 3-36: Interfaces - Principle of PDO mapping......................................................................................................................112
Figure 3-37: LogicsManager - function overview..........................................................................................................................126
Figure 3-38: LogicsManager - display in ToolKit..........................................................................................................................127
Figure 3-39: LogicsManager - display in LCD ..............................................................................................................................127
Tables
Table 1-1: Manual - overview ............................................................................................................................................................. 8
Table 3-1: Application - load shed with standard transition switch ................................................................................................ 51
Table 3-2: Application - load shed with delayed or closed transition switch ................................................................................. 52
Table 3-3: Monitoring - standard values - load time-overcurrent ................................................................................................... 90
Table 3-4: Monitoring - standard values - overload ......................................................................................................................... 92
Table 3-5: Monitoring - standard values - battery overvoltage ....................................................................................................... 95
Table 3-6: Monitoring - standard values - battery undervoltage ..................................................................................................... 97
Table 3-7: Discrete inputs - assignment .......................................................................................................................................... 100
Table 3-8: Discrete inputs - parameter IDs ..................................................................................................................................... 101
Table 3-9: External discrete inputs - parameter IDs....................................................................................................................... 101
Table 3-10: Relay outputs - Assignment......................................................................................................................................... 102
Table 3-11: Discrete outputs - parameter IDs ................................................................................................................................. 103
Table 3-12: External discrete outputs - parameter IDs .................................................................................................................. 103
Table 3-13: Internal flags - parameter IDs ...................................................................................................................................... 106
Table 3-14: Daylight saving time - configuration example ........................................................................................................... 119
Table 3-15: Daylight saving time - examplary dates ..................................................................................................................... 119
Table 3-16: LogicsManager - command overview ........................................................................................................................ 126
Table 3-17: LogicsManager - logical symbols ............................................................................................................................... 127
Chapter 1.
General Information
DTSC-200A
DTSC-200A - Installation 37939 -
DTSC-200A - Configuration this manual 37940 -
DTSC-200A - Operation 37941 -
DTSC-200A - Application 37942 -
DTSC-200A - Interfaces 37943 -
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.
QR Code
To get access to the complete product documentation, scan this QR code or use the following link:
➔ [Link]
Chapter 2.
Configuration
Configuration Via PC
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Install ToolKit Configuration and Visualization Software
NOTE
Woodward’s ToolKit software is required to configure the unit via PC.
══▷ [Link]
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.
Configuration files and Technical Manual are available on a Woodward server. Refer to chapter QR Code.
The latest versions are available at the Woodward web site.
• Configuration
◦ msi-file (installing application files and ToolKit)
◦ eds-file (zipped)
• Technical Manual (PDF)
NOTE
ToolKit is using the following files:
*.WTOOL
File name composition: [P/N1]*1-[Revision]_[Language ID]_[P/N2]* 2-[Revision]_[# of visualized
gens].WTOOL
Example file name: 8440-1234-NEW_US_5418-[Link]
Content of the file: Display screens and pages for online configuration, which are associated with
the respective *.SID file
*.SID
File name composition: [P/N2]*2-[Revision].SID
Example file name: [Link]
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.
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-[Link]) and click
“Open” to start the configuration file
4. Now the home page of the ToolKit configuration screen appears
NOTE
Please use the ToolKit online help for further information.
1. Plug the USB cable into your windows compatible computer and into the DTSC200A device. The USB
driver should be automatically recognized. Check your Device Manager for proper running.
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.
SID Files for Using ToolKit on the CAN Bus with other CANopen Devices
If a PC with ToolKit is connected to the DTSC-200A 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-200A 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:
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 121) must be entered before being able to
edit the parameters.
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:
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.
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-200A 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
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
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 100.
Reply from ATS limit switch: Breaker in source 1 position fixed to discrete input [DI 1], terminal 10
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 11
Note: Normally closed (break) contact!
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 12
Note: Normally closed (break) contact!
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 13
Note: Normally closed (break) contact!
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 14
Note: Normally closed (break) contact!
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.
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 102.
LogicsManager Relay {all} programmable to relay [R2, R3, R4, R6, R7]
Note: Normally open (make) contact!
All relays not assigned with a defined function, may be configured via the LogicsManager.
All relays not assigned with a defined function, may be configured via the LogicsManager.
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 3/4
Note: Normally open (make) contact!
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 3/5
Note: Normally open (make) contact!
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 36/37/38
Note: Normally open (make) contact!
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 39/40
Note: Normally open (make) contact!
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.
EN
Language
CL0 {0} {1} {2} The desired language for the unit display text is configured here.
1700 ✓ ✓ ✓
Password
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The DTSC-200A 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:
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.
EN
Passwort
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 37941. The operation states, which are stored in the event history, are listed
in the table below.
The event history display is password-protected.
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 "-".
EN
Ereignisspeicher anzeigen
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 37941 for a complete list of all entries, which
may appear in the event history.
DE EN
Measuring
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
NOTE
This controller is only available with 5A [../5] current transformer inputs.
NOTE
It is absolutely necessary for correct rated voltage values to be entered, as many measurement and
monitoring functions refer to these values.
Nennfrequenz im System
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.
EN
Nennspannung S1
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.
EN
Nennspannung S2
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.
DE EN
S1 voltage measuring Measurement principle: Source 1 3Ph 4W / 3Ph 3W / 1Ph 2W / 1Ph 3W
S1 Spannungsmessung
CL2 {0} {1} {2} Please refer to the comments on measuring principles in the installation
1862 ✓ ✓ ✓
manual (37939).
DE EN
S2 voltage measuring Measurement principle: Source 2 3Ph 4W / 3Ph 3W / 1Ph 2W / 1Ph 3W
S2 Spannungsmessung
CL2 {0} {1} {2} Please refer to the comments on measuring principles in the installation
1861 ✓ ✓ ✓
manual (37939).
Ph – Ph / Phase - N
EN
DE EN
S1 Load current measuring Measurement principle: S1 Load current L1 L2 L3 / Phase L1 / Phase L2 / Phase L3
S1 Last Strommessung
CL2 {0} {1} {2} Please refer to the comments on measuring principles in the installation
1863 ✓ ✓ ✓
manual (37939).
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.
DE EN
S2 Load current measuring Measurement principle: S2 Load current L1 L2 L3 / Phase L1 / Phase L2 / Phase L3
S2 Last Strommessung
CL2 {0} {1} {2} Please refer to the comments on measuring principles in the installation
1860 ✓ ✓ ✓
manual (37939).
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.
DE EN
Nennstrom
CL2 {0} {1} {2} This value specifies the rated current.
1754 ✓ ✓ ✓
Measuring: Transformers
Voltage Transformer
EN
DE S1 voltage transf. primary Voltage transformer, source 1, primary 50 to 650,000 V
S1 Spannungswandler primär
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.
EN
S1 Spannungswandler sekund.
CL2 {0} {1} {2} Some applications may require the use of potential transformers to facilitate
1818 ✓ ✓ ✓
measuring the source voltages. The rating of the secondary 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.
DE EN
S2 Spannungswandler sekund.
CL2 {0} {1} {2} Some applications may require the use of potential transformers to facilitate
1815 ✓ ✓ ✓
measuring the source voltages. The rating of the secondary side of the potential
transformer on source 2 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.
Current Transformer
NOTE
This controller is only available with 5A [../5] current transformer inputs.
DE EN
Application
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Application: Application Mode
EN
Betriebsmodus
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.
Source 1 Source 2
G
Source 1 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 37942 for details.
NOTE
Please refer to “Transfer delay timer S1->S2” (parameter 4496) and “Transfer delay timer S2->S1”
(parameter 4497) for details.
DE EN
Transfer commit Transfer commit YES / NO
Transfer zustimmen
CL2 {0} {1} {2} This function is only effective if a transfer from the preferred source to the non-
4146 --- ✓ ---
preferred source is requested.
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.
DE EN
Transfer delay timer S2->S1 Transfer delay timer S2->S1 0 to 6500 s
Transfer Verzögerung S2->S1
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 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.
S1 Startverzögerung
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.
EN
S2 Startverzögerung
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.
DE EN
S1 Source Stable time Source 1 source stable time 1 to 6500 s
S1 Stabilisierzeit
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-200A 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.
EN
S2 Stabilisierzeit
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-200A is powered up while
the system is in neutral position.
DE EN
S1 outage delay Source 1 outage delay 0.1 to 99.9 s
S1 Ausfallverzögerung
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.
DE EN
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
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.
EN
S1 Nachlaufzeit
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.
DE EN
If this timer is running, the "S2 cooldown" message and the Bypass softkey are
displayed.
DE EN
Start S1 even if inhibited Start S1 even if inhibited Yes/No
Start S1 auch wenn gesperrt
CL2 {0} {1} {2} This parameter determines if the S1 source (usually engine) shall be started even
2586 --- ✓ ✓
the load transfer is inhibited.
For example it could make sense to start the engine(s) because there must be
several engines started and ready for load before the transfer is executed.
EN
For example it could make sense to start the engine(s) because there must be
several engines started and ready for load before the transfer is executed.
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.
EN
Blockiere ATS
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 125 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!
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.
DE EN
This function has the same behavior as the "Inhibit XFR to source 1" function, except that a transfer to source 2
will be prevented.
DE EN
Spitzenlast Modus
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 125 in Appendix
12630 ✓ ✓ ✓
A: "LogicsManager".
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.
EN
Anforder. Netzbetr.
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 125 in Appendix
12660 ✓ ✓ ✓
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
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.
• 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.
EN
Gen-Gen Aktivieren
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 125 in Appendix
12830 --- --- ✓
A: "LogicsManager".
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.
EN
Aufzugswarnsignal
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.
EN
Warnsignal Dauer
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.
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.
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.
EN
Lastabwurf
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.
EN
Lastabwurfszeit S1
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
EN
Lastabwurfszeit S2
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
DE EN
Skip load disconnect Skip load disconnect Yes/No
Verkürze Lastabwurfzeit
CL2 {0} {1} {2} This parameter determines whether the motor load disconnect timer shall be
2588 ✓ ✓ ✓
bypassed if the prioritized source has an outage.
EN
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:
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.
If the LogicsManager function "Source Priority S1" becomes TRUE, source 1 will be considered as preferred.
EN
S1 Priorität
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 125 in Appendix
12680 ✓ ✓ ✓
A: "LogicsManager".
If the LogicsManager function "Source Priority S2" becomes TRUE, source 2 will be considered as preferred.
EN
S2 Priorität
Page 46/166 © Woodward
Released
NOTE
If no source is preferred (both LogicsManager functions are FALSE or both LogicsManager functions
are TRUE), source 1 will be the preferred source.
Transfer direction
upon loss of S1
S1 S2
preferred source non-preferred source
(emergency source)
Load
Figure 3-7: Source priority selection - S1 preferred
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.
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.
DE EN
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 65) is disabled
• a remote peak shave request (parameter 12630 on page 40) is disabled
• an interruptible power rate request (parameter 12660 on page 41) 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
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.
EN
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).
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).
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.
EN
LS nach Neutral
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 125 in Appendix
12890 ✓ ✓ ✓
A: "LogicsManager".
The DTSC-200A provides up to 4 free configurable text on the main display screen. With these texts a operator
can be informed about special programmed procedures.
Four LogicsManagers are offered to fade in the prepared texts.
NOTE
The 4 LogicsManager are prioritized under each other. The free message text 1 has the highest priority
and the free message text 4 has the lowest priority.
An enabled configurable text overwrites the original text on the main display screen.
If the LogicsManager function "Free message text x" becomes TRUE, the text will be indicated on the main
screen on display until this function becomes FALSE again.
EN
Breaker
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Breaker: Transfer Switch Type
EN
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!
Load
Figure 3-11: Open transition switch - connected to source 1
Load
Figure 3-12: Open transition switch - connected to source 2
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
• Discrete input 2 (ATS breaker in Source 2 position) = signal designation: S2
In this mode Use Limit Switch Open Replies (3434) is disabled (setting “NO”).
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
Load
Figure 3-15: Delayed 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”:
• Discrete input 1 (ATS breaker in Source 1 position) = signal designation: S1
• Discrete input 2 (ATS breaker in Source 2 position) = signal designation: S2
• Discrete input 3 (ATS breaker in Source 1 OPEN position) = signal designation: S1O
• Discrete input 4 (ATS breaker in Source 2 OPEN position) = signal designation: S2O
Page 56/166 © Woodward
Released
If Use Limit Switch Open Replies (3434) is “NO” the evaluated feedback signals are reduces to S1 and S2.
Load
• 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)
Load
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”:
© Woodward Page 57/166
Released
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:
• Discrete input 1 (ATS breaker in Source 1 position) = signal designation: S1
• Discrete input 2 (ATS breaker in Source 2 position) = signal designation: S2
• Discrete input 3 (ATS breaker in Source 1 OPEN position) = signal designation: S1O
• Discrete input 4 (ATS breaker in Source 2 OPEN position) = signal designation: S2O
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.
EN
Use Limit sw. OPEN replies Use limit switch open replies YES / NO
DE
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.
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.
EN
Transition Timers
The "Neutral Time S2 -> S1" parameter is only enabled, if "Delayed" or "Closed" is configured as "Transfer
switch type" (parameter 3424).
EN
The "Neutral Time S2 <- S1" parameter is only enabled, if "Delayed" or "Closed" is configured as "Transfer
switch type" (parameter 3424).
EN
Limit switch reply timeout Limit switch reply timeout 0.1 to 99.9 s
DE
Zeitüberschreitung Rückmeld.
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 61). 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
attempt
This parameter configures the interval between an unsuccessful transfer attempt
DE
Wartezeit vor neuem Transfer
{0} {1} {2}
CL2
✓ ✓ ✓
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
Note: If this parameter is configured to “0”, the DTSC-200A 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.
EN
NO ............... In the moment being parallel with the other source, the breaker
feedbacks, the voltage, frequency and phase angle are still
monitored. The device finish the transfer if all parameters are
matched.
YES.............. In the moment being parallel with the other source the breaker
feedback signals only determines the closed transition time. With
successful closure of the intended source the other source is
opened.
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.
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.
If the reply from the ATS controller is detected while the "Limit switch reply timeout" timer is still counting, the
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
attempts (parameter 3427) is reached. The failure will be issued after the last failed transfer attempt.
NOTE
If a closure failure occurs, the system always tries to close the second breaker to a good source.
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.
If the reply from the ATS controller is detected while the "Limit switch reply timeout" timer is still counting, the
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
attempts (parameter 3427) is reached. The failure will be issued after the last failed transfer attempt.
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.
If the reply from the ATS controller is detected while the "Limit switch reply timeout" timer is still counting, the
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
attempts (parameter 3427) is reached. The failure will be issued after the last failed transfer attempt.
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.
EN
Lastprobe
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 125 in Appendix
12640 ✓ ✓ ✓
A: "LogicsManager".
If the LogicsManager function "No Load Test" becomes TRUE (by energizing a DI for example), a no load test
will be performed.
DE EN
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:
DE EN
Exerciser Type Exerciser type Off / Daily / Weekly / 14-Day / 28-Day / 365-Day / One Event
Testzyklus Art
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
configured time starting with a configured date
365-Day ....... A yearly (every 365 days) exercise will be performed at the
configured time starting with a configured date
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).
EN
Exerciser start time hour Exerciser start: hour 0 to 23 h
DE
Start Zeit
CL2 {0} {1} {2} The hour of the exercise start time is configured here.
6491 ✓ ✓ ✓
EN
Start Zeit
CL2 {0} {1} {2} The hour of the exercise start time is configured here.
6492 ✓ ✓ ✓
DE EN
Start Tag
CL2 {0} {1} {2} The date of an exerciser start is configured here.
6494 ✓ ✓ ✓
EN
Start Monat
CL2 {0} {1} {2} The month of an exerciser start is configured here.
6495
EN
Start Jahr
CL2 {0} {1} {2} The year of an exerciser start is configured here (08 corresponds with 2008).
6499
EN
Testdauer in Stunden
CL2 {0} {1} {2} The exerciser duration in hours is configured here.
6496
EN
Testdauer in Minuten
CL2 {0} {1} {2} The exerciser duration in minutes is configured here.
6497
EN
Test Typ
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
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
ID Parameter Setting
6503 Exerciser Type Weekly
6504 Exerciser start time hour 12 h
6505 Exerciser start time minute 00 min
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 *
6509 Exerciser duration hours 0h
6510 Exerciser duration minutes 30 min
6511 Exerciser test type Load
Figure 3-25: Test modes - configuring exerciser 2 for a weekly exercise
ID Parameter Setting
6516 Exerciser Type 14-Day
6517 Exerciser start time hour 18 h
6518 Exerciser start time minute 45 min
6519 Exerciser start day of week N/A *
6520 Exerciser start day 12
6521 Exerciser start month 10
6525 Exerciser start year 08
6522 Exerciser duration hours 2h
6523 Exerciser duration minutes 45 min
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
ID Parameter Setting
6529 Exerciser Type One Event
6530 Exerciser start time hour 08 h
6531 Exerciser start time minute 00 min
6532 Exerciser start day of week N/A *
6533 Exerciser start day 11
6534 Exerciser start month 11
6538 Exerciser start year 08
6535 Exerciser duration hours 0h
6536 Exerciser duration minutes 15 min
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.
Monitoring
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Monitoring: Alarm Acknowledgement
DE EN
Time until horn reset Self acknowledgment of the centralized alarm (horn) 0 to 1,000 s
Zeit Hupenreset
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.
EN
Ext. Quittierung
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.
Rückmeldungswächter
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
37941.
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).
EN
Limit switch failure delay time Limit switch failure delay time 0.00 to 10.00 s
Rückmeldungswächter
DE
Verzög. Depending on application switching process has an impact on the limit switch
{0} {1} {2}
CL2 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.
EN
Reset limit switch failure External acknowledgment of Limit switch failure LogicsManager
Rückmeldungswächter
DE
rücksetzen. It is possible to acknowledge Limit Switch Failure from remote (alternatively to the
{0} {1} {2}
CL2 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 125 in Appendix
A: "LogicsManager".
Spg.-Überwachung S1
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.
S1 Unterspannung auslösen
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1 (parameter 1774 on
4451 ✓ ✓ ✓
page 25).
This parameter configures the threshold, which must be fallen below to consider
source 1 as "not OK".
S1 Unterfrequenz Wächter
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.
DE EN
S1 Unterfrequenz auslösen
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4454 ✓ ✓ ✓
page 25)
This parameter configures the threshold, which must be fallen below to consider
source 1 as "not OK".
S1 Überspannung Wächter
CL2 {0} {1} {2} This parameter configures, whether overvoltage monitoring for source 1 is
4455 ✓ ✓ ✓
performed.
OFF.............. No overvoltage monitoring is performed for source 1.
ON................ Overvoltage monitoring is performed for source 1.
DE EN
This parameter configures the threshold, which must be fallen below to consider
source 1 as "OK" again.
EN
S1 Überspannung auslösen
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1 (parameter 1774 on
4457 ✓ ✓ ✓
page 25).
EN
DE S1 overfrequency monitoring Source 1 overfrequency monitoring ON / OFF
S1 Überfrequenz Wächter
CL2 {0} {1} {2} This parameter configures, whether overfrequency monitoring for source 1 is
4458 ✓ ✓ ✓
performed.
OFF.............. No overfrequency monitoring is performed for source 1.
ON................ Overfrequency monitoring is performed for source 1.
DE EN
This parameter configures the threshold, which must be fallen below to consider
source 1 as "OK" again..
EN
S1 Überfrequenz auslösen
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4460 ✓ ✓ ✓
page 25).
S1 Asymmetrie Wächter
CL2 {0} {1} {2} This parameter configures, whether voltage imbalance monitoring for source 1 is
4461 ✓ ✓ ✓
performed.
OFF.............. No voltage imbalance monitoring is performed for source 1.
ON................ Voltage imbalance monitoring is performed for source 1.
EN
S1 Asymmetrie rücksetzen
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1 (parameter 1774 on
4462 ✓ ✓ ✓
page 25).
This parameter configures the threshold, which must be fallen below to consider
source 1 as "OK" again.
EN
S1 Asymmetrie auslösen
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1 (parameter 1774 on
4463 ✓ ✓ ✓
page 25).
Verzögerung
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.
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 counterclockwise
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.
DE EN
S1 Drehfeld
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.
! WARNING:
This parameter influences the protective functions.
S2 Unterspannung rücksetzen
CL2 {0} {1} {2} This value refers to the Rated voltage Source 2 (parameter 1772 on
4465 ✓ ✓ ✓
page 25).
This parameter configures the threshold, which must be fallen below to consider
source 2 as "not OK".
EN
DES2 underfrequency monitoring Source 2 underfrequency monitoring ON / OFF
S2 Unterfrequenz Wächter
CL2 {0} {1} {2} This parameter configures, whether underfrequency monitoring for source 2 is
4467 ✓ ✓ ✓
performed.
OFF .............. No underfrequency monitoring is performed for source 2.
ON ................ Underfrequency monitoring is performed for source 2.
DE EN
S2 Unterfrequenz auslösen
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4469 ✓ ✓ ✓
page 25)
This parameter configures the threshold, which must be fallen below to consider
source 2 as "not OK".
S2 Überspannung Wächter
CL2 {0} {1} {2} This parameter configures, whether overvoltage monitoring for source 2 is
4470 ✓ ✓ ✓
performed.
OFF .............. No overvoltage monitoring is performed for source 2.
ON ................ Overvoltage monitoring is performed for source 2.
DE EN
This parameter configures the threshold, which must be fallen below to consider
source 2 as "OK" again.
EN
S2 Überspannung auslösen
CL2 {0} {1} {2} This value refers to the Rated voltage Source 2 (parameter 1772 on
4472 ✓ ✓ ✓
page 25).
S2 Überfrequenz Wächter
CL2 {0} {1} {2} This parameter configures, whether overfrequency monitoring for source 2 is
4473 ✓ ✓ ✓
performed.
OFF ..............No overfrequency monitoring is performed for source 2.
ON ................Overfrequency monitoring is performed for source 2.
DE EN
This parameter configures the threshold, which must be fallen below to consider
source 2 as "OK" again..
EN
S2 Überfrequenz auslösen
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4475 ✓ ✓ ✓
page 25).
S2 Asymmetrie Wächter
CL2 {0} {1} {2} This parameter configures, whether voltage imbalance monitoring for source 1 is
4476 ✓ ✓ ✓
performed.
OFF ..............No voltage imbalance monitoring is performed for source 1.
ON ................Voltage imbalance monitoring is performed for source 1.
EN
S2 Asymmetrie rücksetzen
CL2 {0} {1} {2} This value refers to the Rated voltage Source 2 (parameter 1772 on
4477 ✓ ✓ ✓
page 25).
This parameter configures the threshold, which must be fallen below to consider
source 2 as "OK" again..
EN
S2 Asymmetrie auslösen
CL2 {0} {1} {2} This value refers to the Rated voltage Source 2 (parameter 1772 on
4478 ✓ ✓ ✓
page 25).
Verzögerung
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.
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 counterclockwise
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.
DE EN
S2 Drehfeld
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.
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.
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.
Source 1 power
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
configured as "1Ph 2W".
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.
Max. Phasenwinkel
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°.
DE EN
In-phase check for DLY trans. Inphase check for DLY trans ON / OFF
Sync bei verzögertem Transfer
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:
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-200A 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.
DE EN
Voltage window Voltage window for synchronization 0.50 to 20.00 %
Spannungsdifferenz
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1/2 (parameters 1774/1772 on
4571 ✓ ✓ ✓
page 25).
Positive frequency window Positive frequency window for synchronization 0.02 to 0.49 Hz
DE
Maximaler Schlupf
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.
EN
Negative frequency window Negative frequency window for synchronization -0.02 to -0.49 Hz
DE
Maximaler Schlupf
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.
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.
EN
Max. Synchronzeit
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.
Final situation:
S1 S2 Load is supplied by source 2.
Open trans. Switch reac. Time Open transition switch reaction time 15 to 300 ms
DE
Closed trans. Switch reac. Time Closed transition switch reaction time 15 to 300 ms
DE
t Transfer
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!
DE EN
Vector group angle adjustment Vector group angle adjustment -180° to 180°
Schaltgruppe Winkel Anpassung
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.
DE EN
In-phase timeout after Inphase timeout after 0 to 6,500 s
Synchr. Zeitüberschr.
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.
EN
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.
DE EN
Ext. permit for cld. trans. Ext. permit for cld. trans. ON / OFF
Ext. Freigabe für LS überlapp.
CL2 {0} {1} {2} This value refers to in-phase monitoring (parameter 4570). This parameter
✓ ✓ ✓
4584
must be configured to “On”.
Freig. LS Überlappung
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 125 in Appendix
12880 ✓ ✓ ✓
A: "LogicsManager".
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]
DE EN
Monitoring Load overcurrent, TOC: Monitoring (Level 1/Level 2/Level 3) ON / OFF
Überwachung
CL2 {0} {1} {2} ON................ Overcurrent monitoring is carried out according to the following
2200 ✓ ✓ ✓
2206
parameters. Monitoring is performed at three levels. All three values
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.
EN
Limit Load overcurrent, TOC: Threshold value (Level 1/Level 2/Level 3) 50.0 to 300.0 %
DE
Limit
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.
DE EN
Delay Load overcurrent, TOC: Delay (Level 1/Level 2/Level 3) 0.02 to 99.99 s
Verzögerung
CL2 {0} {1} {2} If the monitored load current exceeds the threshold value for the delay time
2205 ✓ ✓ ✓
2211
configured here, an alarm will be issued. If the monitored load current falls below
2217 the threshold (minus the hysteresis) before the delay expires the time will be reset.
EN
Self acknowledge Load overcurrent, TOC: Self acknowledgment (Level 1/Level 2/Level 3) ON / OFF
DE
Selbstquittierend
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".
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)
DE EN
Monitoring Overload: Monitoring (Level 1/Level 2) ON / OFF
Überwachung
CL2 {0} {1} {2} ON................ Overload monitoring is carried out according to the following
2300 ✓ ✓ ✓
2306
parameters. Monitoring is performed at two levels. Both values may
be configured independent from each other (prerequisite: limit 1
< limit 2).
OFF.............. Monitoring is disabled for level 1 and/or level 2.
EN
Limit
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
interruption, an alarm is issued.
DE EN
Selbstquittierend
CL2 {0} {1} {2} YES .............. The control automatically clears the alarm if it is no longer valid.
2302 ✓ ✓ ✓
2308
NO................ An automatic reset of the alarm does not occur. The reset occurs
manually by pressing the appropriate buttons, by activating the
LogicsManager output "External acknowledgement" via an discrete
input, or via an interface.
S1 start fail delay time Source 1 start fail: delay time 1 to 6500 s
DE
S1 Startfehler Zeit
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.
S2 start fail delay time Source 2 start fail: delay time 1 to 6500 s
DE
S2 Startfehler Zeit
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.
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)
DE EN
Monitoring Battery overvoltage: Monitoring (Level 1/Level 2) ON / OFF
Überwachung
CL2 {0} {1} {2} ON ................Overvoltage monitoring of the battery voltage is carried out
3450 ✓ ✓ ✓
3456
according to the following parameters.
OFF ..............Monitoring is disabled for level 1 and/or level 2.
EN
Limit
CL2 {0} {1} {2} The threshold values that are to be monitored are defined here. If the monitored
3454 ✓ ✓ ✓
3460
battery voltage reaches or exceeds this value for at least the delay time without
interruption, an alarm is issued.
EN
Verzögerung
CL2 {0} {1} {2} If the monitored battery voltage exceeds the threshold value for the delay time
3455 ✓ ✓ ✓
3461
configured here, an alarm will be issued. If the monitored battery voltage falls
below the threshold (minus the hysteresis) before the delay expires the time will be
reset.
EN
Selbstquittierend
CL2 {0} {1} {2} YES ..............The control automatically clears the alarm if it is no longer valid.
3452 ✓ ✓ ✓
3458
NO ................An automatic reset of the alarm does not occur. The reset occurs
manually by pressing the appropriate buttons, by activating the
LogicsManager output "External acknowledgement" via an discrete
input, or via an interface.
[%]
Rated value
[100 %]
Alarm level 1
(Alarm limit 1)
Alarm level 2
(Alarm limit 2)
DE EN
Monitoring Battery undervoltage: Monitoring (Level 1/Level 2) ON / OFF
Überwachung
CL2 {0} {1} {2} ON ................Undervoltage monitoring of the battery voltage is carried out
3500 ✓ ✓ ✓
3506
according to the following parameters.
OFF ..............Monitoring is disabled for level 1 and/or level 2.
EN
Limit
CL2 {0} {1} {2} The threshold values that are to be monitored are defined here. If the monitored
3504 ✓ ✓ ✓
3510
battery voltage reaches or falls below this value for at least the delay time without
interruption, an alarm is issued.
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).
DE EN
Selbstquittierend
CL2 {0} {1} {2} YES ..............The control automatically clears the alarm if it is no longer valid.
3502 ✓ ✓ ✓
3508
NO ................An automatic reset of the alarm does not occur. The reset occurs
manually by pressing the appropriate buttons, by activating the
LogicsManager output "External acknowledgement" via an discrete
input, or via an interface.
Überwachung
CL2 {0} {1} {2} ON................ Monitoring of the CANopen interface is carried out according to the
3150 ✓ ✓ ✓
following parameters.
OFF.............. Monitoring is disabled.
EN
Verzögerung
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.
EN
Selbstquittierend
CL2 {0} {1} {2} YES .............. The control automatically clears the alarm if it is no longer valid.
3152 ✓ ✓ ✓
NO................ An automatic reset of the alarm does not occur. The reset occurs
manually by pressing the appropriate buttons, by activating the
LogicsManager output "External acknowledgement" via an discrete
input, or via an interface.
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] 10 Reply from ATS limit switch: Breaker in source 1 position [S1]
[DI 2] 11 Reply from ATS limit switch: Breaker in source 2 position [S2]
[DI 3] 12 Reply from ATS limit switch: Breaker in source 1 open position [S1O] #1
[DI 4] 13 Reply from ATS limit switch: Breaker in source 2 open position [S2O] #1
[DI 5] 14 Control input (LogicsManager), pre-assigned with Inhibit ATS
[DI 6] 15 Control input (LogicsManager)
[DI 7] 19 Control input (LogicsManager)
[DI 8] 56 Control input (LogicsManager)
[DI 9] 57 Control input (LogicsManager)
[DI 10] 58 Control input (LogicsManager)
[DI 11] 59 Control input (LogicsManager)
[DI 12] 60 Control input (LogicsManager)
External discrete inputs (via CANopen; not included in DTSC delivery; can be e.g. IKD1, etc.)
[Dex01] --- Control input (LogicsManager)
[Dex02] --- Control input (LogicsManager)
[Dex03] --- Control input (LogicsManager)
[Dex04] --- Control input (LogicsManager)
[Dex05] --- Control input (LogicsManager)
[Dex06] --- Control input (LogicsManager)
[Dex07] --- Control input (LogicsManager)
[Dex08] --- Control input (LogicsManager)
[Dex09] --- Control input (LogicsManager)
[Dex10] --- Control input (LogicsManager)
[Dex11] --- Control input (LogicsManager)
[Dex12] --- Control input (LogicsManager)
[Dex13] --- Control input (LogicsManager)
[Dex14] --- Control input (LogicsManager)
[Dex15] --- Control input (LogicsManager)
[Dex16] --- 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.
GND - 8 to 35 Vdc
1
GND - 8 to 35 Vdc
1
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.
DE EN
DI {x} operation Discrete input: Operation N.O. / N.C.
DI {x} Funktion
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).
EN
DI {x} Verzögerung
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 147 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
Some outputs are assigned a function according to the application mode (see following table).
Relay Function
Number Term.
Internal relay outputs
[R 2] 2/6 LogicsManager
[R 3] 2/7 LogicsManager
[R 4] 2/8 LogicsManager
[R 5] 20/21/22 LogicsManager (pre-defined with engine 2 start)
[R 6] 3/4 LogicsManager (pre-defined with command: close to source 1 position) [C1]
[R 7] 3/5 LogicsManager (pre-defined with command: close to source 2 position) [C2]
[R 8] 36/37/38 LogicsManager (pre-defined with command: open from source 1 to neutral position) [C1O]
[R 9] 39/40 LogicsManager (pre-defined with command: open from source 2 to neutral position) [C2O]
External relay output (via CANopen; not included in DTSC-200A delivery; can be an expansion card like IKD1)
[Rex01] --- LogicsManager
[Rex02] --- LogicsManager
[Rex03] --- LogicsManager
[Rex04] --- LogicsManager
[Rex05] --- LogicsManager
[Rex06] --- LogicsManager
[Rex07] --- LogicsManager
[Rex08] --- LogicsManager
[Rex09] --- LogicsManager
[Rex10] --- LogicsManager
[Rex11] --- LogicsManager
[Rex12] --- LogicsManager
[Rex13] --- LogicsManager
[Rex14] --- LogicsManager
[Rex15] --- LogicsManager
[Rex16] --- LogicsManager
Table 3-10: Relay outputs - Assignment
DE EN
Relay {x} Discrete outputs: LogicsManager for relay {x} LogicsManager
Relais {x}
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 125 in
Appendix A: "LogicsManager".
Above parameter IDs refers to R 2. Refer to Table 3-11 for the parameter IDs of the parameters for R 3 to R 9.
R2 R3 R4 R5 R6 R7 R8 R9
Parameter ID 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
EN
Counter value preset Counter: Set point value for counters 0 to 99,999,999
DE
Zähler-Setzwert
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.
DE EN
S1 Blindarbeit [0,00Mvarh]
CL2 {0} {1} {2} YES.............. The current value of this counter is overwritten with the value
2516 ✓ ✓ ✓
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.
DE EN
The counter for “Transfers to S1” counts, how often the ATS switch has been
closed to the Source 1 position.
EN
S2 Wirkarbeit [0,00MWh]
CL2 {0} {1} {2} YES.............. The current value of this counter is overwritten with the value
2510 ✓ ✓ ✓
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.
DE EN
DE EN
Transfers to S2 Counter: Transfers to S2 0 to 65535
Transfers nach S2
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 104) 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 125 in chapter "LogicsManager").
EN
Merker {x]
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.
NOTE
Flag 1 is also used as placeholder in other logical combinations. Flag 8 is preset with a timer start.
LogicsManager: Timer
Setpoint {x}: Hour Timer: Daily time set point {x} [x = 1/2]: hour 0 to 23 h
Setpoint {x}: Stunde
CL2 {0} {1} {2} Enter the hour of the daily time set point here. Example:
✓ ✓ ✓
1652
1657
0.................... 0th hour of the day (midnight).
23.................. 23rd hour of the day (11pm).
EN
Setpoint {x}: Minute Timer: Daily time set point {x} [x = 1/2]: minute 0 to 59 min
DE
Setpoint {x}: Second Timer: Daily time set point {x} [x = 1/2]: second 0 to 59 s
DE
Aktiver Tag
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.
EN
Aktive Stunde
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.
EN
Aktive Minute
CL2 {0} {1} {2} Enter the minute of the active switch point here. Example:
✓ ✓ ✓
1661
0.................... 0th minute of the hour.
59.................. 59th minute of the hour.
The active time set point is enabled every hour during the indicated minute from
second 0 to second 59.
DE EN
Active second Timer: Active time set point: second 0 to 59 s
Aktive Sekunde
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.
Monday active Timer: Weekly time set points Monday: days YES / NO
Montag aktiv
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
EN
Tuesday active Timer: Weekly time set points Tuesday: days YES / NO
DE
Dienstag aktiv
CL2 {0} {1} {2} Please enter the days of the weekly workdays.
1671 ✓ ✓ ✓
Tuesday............YES - The switch point is enabled every Tuesday
NO - The switch point is disabled every Tuesday
EN
Wednesday active Timer: Weekly time set points Wednesday: days YES / NO
DE
Mittwoch aktiv
CL2 {0} {1} {2} Please enter the days of the weekly workdays.
1672 ✓ ✓ ✓
Wednesday ......YES - The switch point is enabled every Wednesday
NO - The switch point is disabled every Wednesday
EN
Thursday active Timer: Weekly time set points Thursday: days YES / NO
DE
Donnerstag aktiv
CL2 {0} {1} {2} Please enter the days of the weekly workdays.
1673 ✓ ✓ ✓
Thursday .........YES - The switch point is enabled every Thursday
NO - The switch point is disabled every Thursday
EN
Friday active Timer: Weekly time set points Friday: days YES / NO
DE
Freitag aktiv
CL2 {0} {1} {2} Please enter the days of the weekly workdays.
1674 ✓ ✓ ✓
Friday...............YES - The switch point is enabled every Friday
NO - The switch point is disabled every Friday
DE EN
Saturday active Timer: Weekly time set points Saturday: days YES / NO
Samstag aktiv
CL2 {0} {1} {2} Please enter the days of the weekly workdays.
1675 ✓ ✓ ✓
Saturday ..........YES - The switch point is enabled every Saturday
NO - The switch point is disabled every Saturday
EN
Sunday active Timer: Weekly time set points Sunday: days YES / NO
DE
Sonntag aktiv
CL2 {0} {1} {2} Please enter the days of the weekly workdays.
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 37943 for a detailed description of the interface parameters.
EN
Gerätenummer
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.
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.
EN
Baudrate CAN bus: Baud rate 20 / 50 / 100 / 125 / 250 / 500 / 800 / 1,000 kBaud
DE
Baudrate
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.
NOTE
The CAN bus in the DTSC-200A is not able to support the Baud rate 800kBaud. Additionally, the Baud
rate 20kB could be as well critical because the amount of transferred data are maybe not fast enough
refreshed.
CAN-open Master
CL2 {0} {1} {2} YES ..............The DTSC-200A 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-200A is a CANopen Slave.
DE EN
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.
EN
2nd Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
DE
2. Client->Server COB-ID (rx)
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.
EN
2nd Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
DE
3rd Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
DE
3rd Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
DE
4th Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
DE
4th Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
DE
5th Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
DE
5th Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
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)
Object Dictionary
xxxxh Application Object 1
PDO Mapping
0 3
1 yyyyh 1
2 zzzzh 1 yyyyh Application Object 2
3 xxxxh 1
DE EN
COB-ID Receive PDO 1/2 - COB-ID 1 to FFFFFFFF
COB-ID
CL2 {0} {1} {2} This parameter contains the communication parameters for the PDOs, the device is
9300 ✓ ✓ ✓
9310
able to receive.
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:
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.".
Funktion
CL2 {0} {1} {2} The unit provides pre-configured CAN bus settings for the connection of different
9050 ✓ ✓ ✓
9051
units. The unit to be connected must be selected here.
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.
Read: If PDO1 is configured as 1. IKD, then PDO2 can only be configured as either 2. IKD or "no func.".
EN
DE EN
RPDO-COP-ID ext. device {x} RPDO-COB-ID ext. device 1 1 to FFFFFFFF
RPDO-COP-ID ext. Gerät {x}
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
380h + Node-ID = 896 + Node-ID Object 1802h Subindex 1
480h + Node-ID = 1152 + Node-ID Object 1803h Subindex 1
The receiving COB-IDs are preallocated:
300h + Node-ID = 768 + Node-ID Object 1401h Subindex 1
400h + Node-ID = 1024 + Node-ID Object 1402h Subindex 1
500h + Node-ID = 1280 + Node-ID Object 1403h Subindex 1.
Problems may be encountered if a COB-ID is assigned multiple times.
COB-ID
CL2 {0} {1} {2} This parameter contains the communication parameters for the PDOs the unit is
9600 ✓ ✓ ✓
9610 able to transmit. The unit transmits data (i.e. visualization data) on the CAN ID
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:
PDO valid / not valid allows selecting, which PDOs are used in the operational state.
DE EN
Transmission type CAN bus 1: Transmit PDO 1 - Transmission type 0 to 255
Transmission type
CL2 {0} {1} {2} This parameter contains the communication parameters for the PDOs the unit is
9602 ✓ ✓ ✓
9612
able to transmit. It defines whether the unit broadcasts all data automatically (value
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:
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 0 to 65000 ms
DE
Event-timer
CL2 {0} {1} {2} This parameter contains the communication parameters for the PDOs the unit is
9604 ✓ ✓ ✓
9614
able to transmit. The broadcast cycle for the transmitted data is configured here.
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
EN
Number of Mapped Objects CAN bus 1: Transmit PDO 1 - Number of mapped objects 0 to 4
DE
Complies with CANopen specification: object 1A00 (for TPDO 1, 1A01 for TPDO 2, 1A02 for TPDO 3,
and 1A03 for TPDO 4), subindex 0
DE EN
Complies with CANopen specification: object 1A00 (for TPDO 1, 1A01 for TPDO 2, 1A02 for TPDO 3,
and 1A03 for TPDO 4), subindex 1
EN
2. Mapped Objekt
CL2 {0} {1} {2} This parameter contains the information about the mapped application variables.
9606 ✓ ✓ ✓
9616 These entries describe the PDO contents by their index. The sub-index is always 1.
9626 The length is determined automatically.
9636
Complies with CANopen specification: object 1A00 (for TPDO 1, 1A01 for TPDO 2, 1A02 for TPDO 3,
and 1A03 for TPDO 4), subindex 2
DE EN
3. Mapped Object CAN bus 1: Transmit PDO 1 - 3. Mapped object 0 to 65535
3. Mapped Objekt
CL2 {0} {1} {2} This parameter contains the information about the mapped application variables.
9607 ✓ ✓ ✓
9617
These entries describe the PDO contents by their index. The sub-index is always 1.
9627 The length is determined automatically.
9637
Complies with CANopen specification: object 1A00 (for TPDO 1, 1A01 for TPDO 2, 1A02 for TPDO 3,
and 1A03 for TPDO 4), subindex 3
EN
4. Mapped Objekt
CL2 {0} {1} {2} This parameter contains the information about the mapped application variables.
9608 ✓ ✓ ✓ These entries describe the PDO contents by their index. The sub-index is always 1.
9618
9628 The length is determined automatically.
9638
Complies with CANopen specification: object 1A00 (for TPDO 1, 1A01 for TPDO 2, 1A02 for TPDO 3,
and 1A03 for TPDO 4), subindex 4
NOTE
CANopen allows sending 8 bytes 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 37943):
• 1,2 UNSIGNED16 or SIGNED16
• 3,4 UNSIGNED16 or SIGNED16
• 5,6 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: USB
NOTE
There is no special setting in the device needed. Please go sure that you have installed the correct USB
Windows driver on your PC on which your ToolKit is running.
Baudrate Serial interface 2: Baud rate 2.4 / 4.8 / 9.6 / 14.4 / 19.2 / 38.4 / 56 / 115 kBaud
Baudrate
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.
EN
Parity
CL2 {0} {1} {2} The used parity of the service interface is set here.
3171 ✓ ✓ ✓
EN
Stop Bits
CL2 {0} {1} {2} The number of stop bits is set here.
3172 ✓ ✓ ✓
NOTE
In comparison to the device DTSC-200 the DTSC-200A does not support Fullduplex mode.
EN
ModBus Slave ID
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.
EN
Modbus Reply delay time Serial interface: Reply delay time 0.00 to 0.20 s
Modbus Zeitverzöger. Der
DE
Antwort This is the minimum delay time between a request from the Modbus master and
{0} {1} {2}
CL2
✓ ✓ ✓
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
EN
If no softkey has been pressed for the time configured here, the display backlight
will be disabled.
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.
ID Parameter Setting
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
Sommer-Winterzeit Erkennung
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.
DE EN
Sommerzeitbeginn Wochentag
CL2 {0} {1o} {1oc} {2oc} The weekday for the DST begin date is configured here
4598 ✓ ✓ ✓ ✓
DE EN
DST begin nth. weekday Daylight saving time begin nth weekday weekday order no.
Sommerzeitbeginn x. Wochentag
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.
DE EN
Sommerzeitende Uhrzeit
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).
EN
Sommerzeitende Wochentag
CL2 {0} {1o} {1oc} {2oc} The weekday for the DST end date is configured here
4599 ✓ ✓ ✓ ✓
Sommerzeitende x. Wochentag
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.
EN
Sommerzeitende Monat
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.
DE EN
Code level display Password system: Code level via display Info
Codeebene Display
CL2 {0} {1} {2} This value displays the code level, which is currently enabled for access via the
10405 ✓ ✓ ✓
front panel display.
EN
Code level CAN port Password system: Code level via CAN-Bus Info
DE
Code level serial port/DPC Password system: Code level via USB interface Info
DE
Codeebene RS232/DPC
CL2 {0} {1} {2} This value displays the code level, which is currently enabled for access via USB
10406 ✓ ✓ ✓
interface #1.
EN
Supercommissioning level code Password system: Password "Supercommissioning" (CL5) 0001 to 9999
DE
Temp. supercomm. Level code Password system: Password "Temporary Supercommissioning" (CL4) 00001to 9999
DE
Commissioning level code Password system: Password "Commission" (CL3) 0001 to 9999
DE
Temp. commissioning level code Password system: Password "Temporary Commission" (CL2) 0001 to 9999
DE
Basic level code Password system: Password "Service Level" (CL1) 0001 to 9999
DE
Code Serviceebene
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.
EN
Passwort
CL0 {0} {1} {2} To configure the control via the front panel bus enter the password.
10416 ✓ ✓ ✓
EN
Password CAN Password system: Entry via CAN bus 0000 to 9999
DE
Passwort CAN
CL0 {0} {1} {2} To configure the control via CAN bus enter "password CAN".
10402 ✓ ✓ ✓
EN
Password DPC Password system: Entry via USB interface 0000 to 9999
DE
DE EN
Factory Settings Factory settings: Factory settings CAN YES / NO
Werkseinstellung
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.
Werkseinstellung DPC/RS232
CL2 {0} {1} {2} YES ..............The resetting of the factory settings via USB will be enabled.
1704 ✓ ✓ ✓
NO ................The resetting of the factory settings via USB will not be enabled.
EN
Werkseinstellung CAN
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.
Standardwerte
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.
XX:YY:ZZ............. hour:minute:second.
AAAA-BBB-CC...... Year-month-day.
Stunden
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.
EN
Minuten
CL2 {0} {1} {2} The current minute of the clock time is set here. Example:
1709 ✓ ✓ ✓
0.................... 0th minute of the hour.
59.................. 59th minute of the hour.
DE EN
Tag
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.
EN
Monat
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.
DE EN
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 37939.
Boot item number Version: Part number of the firmware (P/N) info
DE
Boot Artikelnummer
{0} {1} {2} The part number (P/N) is the firmware in the control unit.
950 ✓ ✓ ✓
EN
Boot revision Version: Revision of the item number of the firmware (REV) info
DE
Boot Revision
{0} {1} {2} The revision number (REV) is the revision of the control unit firmware.
960 ✓ ✓ ✓
EN
Boot Version
{0} {1} {2} This number ([Link]) represents the version of the control unit firmware.
965 ✓ ✓ ✓
EN
Program item number Version: Item number of the application software (P/N) info
DE
Programm Artikelnummer
{0} {1} {2} The part number (P/N) is the application software running the control unit.
930 ✓ ✓ ✓
DE EN
Program revision Version: Revision of the item number of the software (REV) info
Programm Revision
{0} {1} {2} The revision number (REV) is the revision of the application software running the
940 ✓ ✓ ✓
control unit.
EN
Programm Version
{0} {1} {2} This number ([Link]) 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 102 shows the assignment of different functions to various discrete outputs.
• 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 130 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
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.
[Ax] = ( ( [C1] & [S1] ) & [O1] & ( [C2] & [S2] ) ) & [O2] & ( [C3] & [S3] )
Logical Symbols
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The following symbols are used for the graphical programming of the LogicsManager.
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:
NOTE
The numbers of the logical outputs in the third column may again be used as input variable for other
outputs in the LogicsManager.
Factory Setting
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The inputs, outputs, and internal flags, which may be programmed via the LogicsManager, have the following
factory default settings when delivered:
Inhibit ATS
(parameter 12600 on page 39)
{0} ✓ If TRUE, the unit is blocked against
{1} ✓ automatic transfers.
{2} ✓
TRUE, if DI 5 is NOT energized
dependent
on DI 5
Gen-Gen enable
(parameter 12830 on page 42)
{0} --- If TRUE, the gen-gen mode will be
{1} --- enabled.
{2} ✓
Prepared for: -
Deactivated by default FALSE
Source 1 priority
(parameter 12680 on page 46)
{0} ✓ If TRUE, source 1 is preferred.
{1} ✓
{2} ✓ Prepared for: -
Activated by default
TRUE
Source 2 priority
(parameter 12810 on page 47)
{0} ✓ If TRUE, source 2 is preferred.
{1} ✓
{2} ✓ Prepared for: -
Deactivated by default
FALSE
Load shed
(parameter 12870 on page 51)
{0} ✓ If TRUE, a load shed from the non-
{1} --- preferred source will be performed.
{2} ✓
Prepared for: -
Deactivated by default FALSE
Load test
(parameter 12640 on page 65)
{0} ✓ If TRUE, a load test will be
{1} ✓ performed.
{2} ✓
Prepared for: -
Deactivated by default FALSE
No load test
(parameter 12650 on page 65)
{0} ✓ If TRUE, a no-load test will be
{1} ✓ performed.
{2} ✓
Prepared for: -
Deactivated by default FALSE
External acknowledge
(parameter 12490 on page 70)
{0} ✓ If TRUE, alarms are acknowledged
{1} ✓ from an external source.
{2} ✓
Prepared for: -
Remote acknowledgement FALSE
FALSE
Relay 5 [R05]
(parameter 12130 on page 103)
{0} ✓ If TRUE, relay 5 will be energized.
{1} ✓
{2} ✓ True, if the Source 2 start signal is dependent
issued on Logics
Command
Variable
[20.06]
Relay 6 [R06]
(parameter 12140 on page 103)
{0} ✓ If TRUE, relay 6 will be energized.
{1} ✓
{2} ✓ True, if the command: Close to dependent
Source 1 is issued on Logics
Command
Variable
[20.07]
Relay 7 [R07]
(parameter 12150 on page 103)
{0} ✓ If TRUE, relay 7 will be energized.
{1} ✓
{2} ✓ True, if the command: Close to dependent
Source 2 is issued on Logics
Command
Variable
[20.09]
Relay 8 [R08]
(parameter 12160 on page 103)
{0} ✓ If TRUE, relay 8 will be energized.
{1} ✓
{2} ✓ True, if the command: Open from dependent
Source 1 is issued on Logics
Command
Variable
[20.08]
Relay 9 [R09]
(parameter 12170 on page 103)
{0} ✓ If TRUE, relay 9 will be energized.
{1} ✓
{2} ✓ True, if the command: Open from dependent
Source 2 is issued on Logics
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 103 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: -
Deactivated by default FALSE
Note:
Internal flag 1 is used as default
setting in all logical outputs.
Internal flag 8
(parameter 12300 on page 106)
{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}
{1} freely configurable discrete input (unassigned)
{2}
[D8] {0}
{1} freely configurable discrete input (unassigned)
{2}
[D9] {0}
{1} freely configurable discrete input (unassigned)
{2}
[D10] {0}
{1} freely configurable discrete input (unassigned)
{2}
[D11] {0}
{1} freely configurable discrete input (unassigned)
{2}
[D12] {0}
{1} freely configurable discrete input (unassigned)
{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
Version DTSC-________________________________________________________________
Project _____________________________________________________________________
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
Par.
Parameter Setting range Default value Customer setting Data type
ID.
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
3Ph 3W 3Ph3W 3Ph3W
1862 S1 voltage measuring 3Ph 4W UNSIGNED 16
1Ph 2W 1Ph2W 1Ph2W
1Ph 3W 1Ph3W 1Ph3W
3Ph 4W 3Ph4W 3Ph4W
3Ph 3W 3Ph3W 3Ph3W
1861 S2 voltage measuring 3Ph 4W UNSIGNED 16
1Ph 2W 1Ph2W 1Ph2W
1Ph 3W 1Ph3W 1Ph3W
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
Phase L2 Ph.L2 Ph.L2
Phase L3 Ph.L3 Ph.L3
L1 L2 L3 L123 L123
Phase L1 Ph.L1 Ph.L1
1860 S2 Load current measuring L1 L2 L3 UNSIGNED 16
Phase L2 Ph.L2 Ph.L2
Phase L3 Ph.L3 Ph.L3
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
Fehler! UNSIGNED 16
Verwe
isquell
e
konnt
e
Load current transformer 1 to 32000/1 A 500/1 A
nicht
gefun
den
werde
n.
Par.
Parameter Setting range Default value Customer setting Data type
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 99.9 s 1.0 s UNSIGNED 16
2803 S2 outage delay 0.1 to 99.9 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
2586 Start S1 even if inhibited YES / NO No Y N Y N UNSIGNED 16
2587 Start S2 even if inhibited YES / NO No Y N Y N 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. 138; default: (!09.05 & 1) & 1 Logman
12610 Inhib. XFR to S1 see descr. in LogicsManager chap. starting page 138; default: (0 & 1) & 1 Logman
12620 Inhib. XFR to S2 see descr. in LogicsManager chap. starting page 138; default: (0 & 1) & 1 Logman
12630 Remote peak shave see descr. in LogicsManager chap. starting page 138; default: (0 & 1) & 1 Logman
12660 Int. pow. rates see descr. in LogicsManager chap. starting page 138; default: (0 & 1) & 1 Logman
12820 Ext. bypass see descr. in LogicsManager chap. starting page 138; default: (0 & 1) & 1 Logman
12830 Gen-Gen enable see descr. in LogicsManager chap. starting page 138; 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
2588 Skip load disconnect YES / NO No Y N Y N UNSIGNED 16
2590 Bypass MLD possible YES / NO No Y N Y N UNSIGNED 16
Source Priority
12680 S1 Priority see descr. in LogicsManager chap. starting page 138; default: (1 & 1) & 1 Logman
12810 S2 Priority see descr. in LogicsManager chap. starting page 138; default: (0 & 1) & 1 Logman
12860 Ext. [Link] see descr. in LogicsManager chap. starting page 138; default: (0 & 1) & 1 Logman
12870 Load shed see descr. in LogicsManager chap. starting page 138; default: (0 & 1) & 1 Logman
12890 Service Disconnect see descr. in LogicsManager chap. starting page 138; 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 138; 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
2649 Monitor Unintended Open ON/OFF OFF Y N Y N UNSIGNED 16
2589 Force Finalize parallel ON/OFF OFF UNSIGNED 16
Par.
Parameter Setting range Default value Customer setting Data type
ID.
DISPLAY OPTION
16626 Free message 1 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
16627 Free message 2 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
16628 Free message 3 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
16629 Free message 4 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
Message Texts
16622 Free message text 1 Free message 1 Charcaters
16623 Free message text 2 Free message 2 Charcaters
16624 Free message text 3 Free message 3 Charcaters
16625 Free message text 4 Free message 4 Charcaters
TESTMODES
12640 Load Test see descr. in LogicsManager chap. starting page 138; default: (0 & 1) & 1 Logman
12650 No Load Test see descr. in LogicsManager chap. starting page 138; default: (0 & 1) & 1 Logman
Par.
Parameter Setting range Default value Customer setting Data type
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 138; 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
3904 Delay 0.02 to 99.99 s 5.00 s 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 85)
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.
Parameter Setting range Default value Customer setting Data type
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
2205 Delay 0.02 to 99.99 s 30.00 s UNSIGNED 16
2202 Self acknowledge YES / NO NO Y N Y N UNSIGNED 16
Overcurrent Monitoring level 2
2206 Monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
2210 Limit 50.0 to 300.0 % 150.0 % UNSIGNED 16
2211 Delay 0.02 to 99.99 s 1.00 s UNSIGNED 16
2208 Self acknowledge YES / NO NO Y N Y N UNSIGNED 16
Overcurrent Monitoring level 3
2212 Monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
2216 Limit 50.0 to 300.0 % 250.0 % UNSIGNED 16
2217 Delay 0.02 to 99.99 s 0.40 s UNSIGNED 16
2214 Self acknowledge YES / NO NO Y N Y N UNSIGNED 16
Overload Monitoring level 1
2300 Monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
2304 Limit 50.0 to 300.0 % 110.0 % UNSIGNED 16
2305 Delay 0.02 to 99.99 s 11.00 s UNSIGNED 16
2302 Self acknowledge YES / NO NO Y N Y N UNSIGNED 16
Overload Monitoring level 2
2306 Monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
2310 Limit 50.0 to 300.0 % 120.0 % UNSIGNED 16
2311 Delay 0.02 to 99.99 s 0.10 s UNSIGNED 16
2308 Self acknowledge YES / NO NO Y N Y N UNSIGNED 16
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
3450 Monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
3454 Limit 8.0 to 42.0 V 32.0 V UNSIGNED 16
3455 Delay 0.02 to 99.99 s 5.00 s 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
3460 Limit 8.0 to 42.0 V 35.0 V UNSIGNED 16
3461 Delay 0.02 to 99.99 s 1.00 s UNSIGNED 16
3458 Self acknowledge YES / NO NO Y N Y N UNSIGNED 16
Undervoltage Monitoring level 1
3500 Monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
3504 Limit 8.0 to 42.0 V 24.0 V UNSIGNED 16
3505 Delay 0.02 to 99.99 s 60.00 s UNSIGNED 16
3502 Self acknowledge YES / NO NO Y N Y N UNSIGNED 16
Undervoltage Monitoring level 2
3506 Monitoring ON / OFF ON 1 0 1 0 UNSIGNED 16
3510 Limit 8.0 to 42.0 V 20.0 V UNSIGNED 16
3511 Delay 0.02 to 99.99 s 10.00 s UNSIGNED 16
3508 Self acknowledge YES / NO NO Y N Y N UNSIGNED 16
CANopen Interface Monitoring
3150 Monitoring ON / OFF OFF 1 0 1 0 UNSIGNED 16
3154 Delay 0.1 to 650.0 s 2.0 s UNSIGNED 16
3152 Self acknowledge YES / NO NO Y N Y N UNSIGNED 16
Par.
Parameter Setting range Default value Customer setting Data type
ID.
DISCRETE INPUTS
Discrete Input 1
DI 1 operation N.C.
DI 1 delay 0.008 s
Discrete Input 2
DI 2 operation N.C.
DI 2 delay 0.008 s
Discrete Input 3
DI 3 operation N.C.
DI 3 delay 0.08 s
Discrete Input 4
DI 4 operation N.C.
DI 4 delay 0.08 s
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.
1301 DI 6 operation N.O. UNSIGNED 16
N.C. N.C. N.C.
1300 DI 6 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Discrete Input 7
N.O. N.O. N.O.
1321 DI 7 operation N.O. UNSIGNED 16
N.C. N.C. N.C.
1320 DI 7 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Discrete Input 8
N.O. N.O. N.O.
1341 DI 8 operation N.O. UNSIGNED 16
N.C. N.C. N.C.
1340 DI 8 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Discrete Input 9
N.O. N.O. N.O.
1361 DI 9 operation N.O. UNSIGNED 16
N.C. N.C. N.C.
1360 DI 9 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Discrete Input 10
N.O. N.O. N.O.
1381 DI 10 operation N.O. UNSIGNED 16
N.C. N.C. N.C.
1380 DI 10 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Discrete Input 11
N.O. N.O. N.O.
1206 DI 11 operation N.O. UNSIGNED 16
N.C. N.C. N.C.
1205 DI 11 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Discrete Input 12
N.O. N.O. N.O.
1226 DI 12 operation N.O. UNSIGNED 16
N.C. N.C. N.C.
1225 DI 12 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
External Discrete Input 1
N.O. N.O. N.O.
16001 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16000 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 2
N.O. N.O. N.O.
16011 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16010 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
Par.
Parameter Setting range Default value Customer setting Data type
ID.
DISCRETE INPUTS
External Discrete Input 3
N.O. N.O. N.O.
16021 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16020 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 4
N.O. N.O. N.O.
16031 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16030 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 5
N.O. N.O. N.O.
16041 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16040 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 6
N.O. N.O. N.O.
16051 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16050 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 7
N.O. N.O. N.O.
16061 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16060 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 8
N.O. N.O. N.O.
16071 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16070 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 9
N.O. N.O. N.O.
16081 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16080 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 10
N.O. N.O. N.O.
16091 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16090 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 11
N.O. N.O. N.O.
16101 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16100 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 12
N.O. N.O. N.O.
16111 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16110 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 13
N.O. N.O. N.O.
16121 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16120 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 14
N.O. N.O. N.O.
16131 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16130 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 15
N.O. N.O. N.O.
16141 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16140 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
External Discrete Input 16
N.O. N.O. N.O.
16151 Operation N.O. UNSIGNED 16
N.C. N.C. N.C.
16150 Delay 0.05 to 650.00 s 0.20 s UNSIGNED 16
Par.
Parameter Setting range Default value Customer setting Data type
ID.
DISCRETE OUTPUTS
Relay 1 Does not exist !
12110 Relay 2 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12310 Relay 3 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12320 Relay 4 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12130 Relay 5 see descr. in LogicsManager chap. starting p. 143; default: (!20.06 & 1) & 1 Logman
12140 Relay 6 see descr. in LogicsManager chap. starting page 143; default: (20.07 & 1) & 1 Logman
12150 Relay 7 see descr. in LogicsManager chap. starting page 143; default: (20.09 & 1) & 1 Logman
12160 Relay 8 see descr. in LogicsManager chap. starting page 143; default: (20.08 & 1) & 1 Logman
12170 Relay 9 see descr. in LogicsManager chap. starting page 143; default: (20.10 & 1) & 1 Logman
12330 External DO 1 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12340 External DO 2 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12350 External DO 3 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12360 External DO 4 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12370 External DO 5 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12380 External DO 6 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12390 External DO 7 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12400 External DO 8 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12410 External DO 9 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12420 External DO 10 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12430 External DO 11 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12440 External DO 12 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12450 External DO 13 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12460 External DO 14 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12470 External DO 15 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12480 External DO 16 see descr. in LogicsManager chap. starting page 143; 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 143; default: (0 & 1) & 1 Logman
12240 Flag 2 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12250 Flag 3 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12260 Flag 4 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12270 Flag 5 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12280 Flag 6 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12290 Flag 7 see descr. in LogicsManager chap. starting page 143; default: (0 & 1) & 1 Logman
12300 Flag 8 see descr. in LogicsManager ch. start. p. 143; def.: (11.01 & !11.02) & 11.03 Logman
Set Timers
1652 Setpoint 1: Hour 0 to 23 h 8h UNSIGNED8
1651 Setpoint 1: Minute 0 to 59 min 0 min UNSIGNED8
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.
Parameter Setting range Default value Customer setting Data type
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
9310 COB-ID 1 to FFFFFFFF 202 UNSIGNED 32
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
9600 COB-ID 1 to FFFFFFFF 181 UNSIGNED 32
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 [Link] Object 0 to 65535 8001 UNSIGNED 16
9606 [Link] Object 0 to 65535 8000 UNSIGNED 16
9607 [Link] Object 0 to 65535 8000 UNSIGNED 16
9608 [Link] Object 0 to 65535 8000 UNSIGNED 16
Transmit PDO 2
9610 COB-ID 1 to FFFFFFFF 182 UNSIGNED 32
9612 Transmission type 0 to 255 255 UNSIGNED 8
9614 Event-timer 20 to 65000 ms 20 ms UNSIGNED 16
9619 Number of mapped objects 0 to 4 4 UNSIGNED 8
9615 [Link] Object 0 to 65535 8002 UNSIGNED 16
9616 [Link] Object 0 to 65535 8000 UNSIGNED 16
9617 [Link] Object 0 to 65535 8000 UNSIGNED 16
9618 [Link] Object 0 to 65535 8000 UNSIGNED 16
Par.
Parameter Setting range Default value Customer setting Data type
ID.
COMMUNICATION INTERFACES
Transmit PDO 3
9620 COB-ID 1 to FFFFFFFF 381 UNSIGNED 32
9622 Transmission type 0 to 255 255 UNSIGNED8
9624 Event-timer 20 to 65000 ms 20 ms UNSIGNED 16
9629 Number of mapped objects 0 to 4 1 UNSIGNED 8
9625 [Link] Object 0 to 65535 3196 UNSIGNED 16
9626 [Link] Object 0 to 65535 0 UNSIGNED 16
9627 [Link] Object 0 to 65535 0 UNSIGNED 16
9628 [Link] Object 0 to 65535 0 UNSIGNED 16
Transmit PDO 4
9630 COB-ID 1 to FFFFFFFF 481 UNSIGNED 32
9632 Transmission type 0 to 255 255 UNSIGNED8
9634 Event-timer 20 to 65000 ms 20 ms UNSIGNED 16
9639 Number of mapped objects 0 to 4 1 UNSIGNED 8
9635 [Link] Object 0 to 65535 3190 UNSIGNED 16
9636 [Link] Object 0 to 65535 0 UNSIGNED 16
9637 [Link] Object 0 to 65535 0 UNSIGNED 16
9638 [Link] Object 0 to 65535 0 UNSIGNED 16
Serial Interface 2 (RS485)
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
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.
Parameter Setting range Default value Customer setting Data type
ID.
Par.
Parameter Setting range Default value Customer setting Data type
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
Fehler!
Verwe
isquell
e
konnte Start Bootloader 00000 to 99999 --- UNSIGNED 16
nicht
gefund
en
werde
n.
Clock Set
1710 Hour 0 to 23 h --- UNSIGNED8
1709 Minute 0 to 59 min --- UNSIGNED8
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
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:
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.
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@[Link]
stgt-info@[Link]
For assistance outside Germany, please consult our worldwide directory on Woodward’s website
([Link]) for the name of your nearest Woodward distributor or service facility.
[For worldwide directory information, go to [Link]/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 __________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
______________________________________________________________
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.
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@[Link]
Homepage
[Link]
2022/04/Stuttgart