DTSC-200 Configuration Manual - 37386 PDF
DTSC-200 Configuration Manual - 37386 PDF
DTSC-200
ATS Controller
Configuration
Software Version 1.0008
Manual 37386D
Manual 37386D DTSC-200 - ATS Controller
WARNING
Read this entire manual and all other publications pertaining to the work to be performed before
installing, operating, or servicing this equipment. Practice all plant and safety instructions and
precautions. Failure to follow instructions can cause personal injury and/or property damage.
The engine, turbine, or other type of prime mover should be equipped with an overspeed
(overtemperature, or overpressure, where applicable) shutdown device(s), that operates totally
independently of the prime mover control device(s) to protect against runaway or damage to the
engine, turbine, or other type of prime mover with possible personal injury or loss of life should the
mechanical-hydraulic governor(s) or electric control(s), the actuator(s), fuel control(s), the driving
mechanism(s), the linkage(s), or the controlled device(s) fail.
Any unauthorized modifications to or use of this equipment outside its specified mechanical, electrical,
or other operating limits may cause personal injury and/or property damage, including damage to the
equipment. Any such unauthorized modifications: (i) constitute "misuse" and/or "negligence" within
the meaning of the product warranty thereby excluding warranty coverage for any resulting damage,
and (ii) invalidate product certifications or listings.
CAUTION
To prevent damage to a control system that uses an alternator or battery-charging device, make sure
the charging device is turned off before disconnecting the battery from the system.
Electronic controls contain static-sensitive parts. Observe the following precautions to prevent
damage to these parts.
• Discharge body static before handling the control (with power to the control turned off, contact a
grounded surface and maintain contact while handling the control).
• Avoid all plastic, vinyl, and Styrofoam (except antistatic versions) around printed circuit boards.
• Do not touch the components or conductors on a printed circuit board with your hands or with
conductive devices.
OUT-OF-DATE PUBLICATION
This publication may have been revised or updated since this copy was produced. To verify that you
have the latest revision, be sure to check the Woodward website:
http://www.woodward.com/pubs/current.pdf
The revision level is shown at the bottom of the front cover after the publication number. The latest
version of most publications is available at:
http://www.woodward.com/publications
If your publication is not there, please contact your customer service representative to get the latest
copy.
Important definitions
WARNING
Indicates a potentially hazardous situation that, if not avoided, could result in death or serious injury.
CAUTION
Indicates a potentially hazardous situation that, if not avoided, could result in damage to equipment.
NOTE
Provides other helpful information that does not fall under the warning or caution categories.
Woodward reserves the right to update any portion of this publication at any time. Information provided by Woodward is believed to be
correct and reliable. However, Woodward assumes no responsibility unless otherwise expressly undertaken.
© Woodward
All Rights Reserved.
Revision History
Content
Monitoring .............................................................................................................................................. 51
Monitoring: Alarm Acknowledgement .......................................................................................... 51
Monitoring: Limit Switch Monitoring............................................................................................. 51
Monitoring: Source 1 Monitoring ................................................................................................. 52
Monitoring: Source 2 Monitoring ................................................................................................. 57
Monitoring: In-Phase Monitoring (Synch Check)......................................................................... 62
Monitoring: Overcurrent ............................................................................................................... 68
Monitoring: Overload ................................................................................................................... 70
Monitoring: Engine, Start Failure Source 1 ................................................................................. 72
Monitoring: Engine, Start Failure Source 2 ................................................................................. 72
Monitoring: Battery, Overvoltage ................................................................................................. 73
Monitoring: Battery, Undervoltage ............................................................................................... 75
Monitoring: CANopen Interface ................................................................................................... 77
Discrete Inputs ....................................................................................................................................... 78
Discrete Outputs (LogicsManager) ........................................................................................................ 80
Counters ................................................................................................................................................ 82
Configure Counters: Operation Hours, kWh, and kvarh.............................................................. 82
LogicsManager ...................................................................................................................................... 83
LogicsManager: Internal Flags .................................................................................................... 83
LogicsManager: Timer ................................................................................................................. 84
Interfaces ............................................................................................................................................... 86
Interfaces: CAN Bus (FlexCAN) .................................................................................................. 86
Interfaces: Serial Interface 1 (RS-232) ........................................................................................ 94
Interfaces: Serial Interface 2 (RS-485) ........................................................................................ 94
System ................................................................................................................................................... 95
System: Configure Display Backlight .......................................................................................... 95
System: Configure Daylight Saving Time .................................................................................... 96
System: Password System .......................................................................................................... 97
System: Real-Time Clock Set ..................................................................................................... 99
System: Versions....................................................................................................................... 100
Illustrations
Figure 3-1: Event history- display............................................................................................................................................. 17
Figure 3-2: Source stable and outage timers ............................................................................................................................. 28
Figure 3-3: External timer bypass - push button ....................................................................................................................... 31
Figure 3-4: Elevator pre-signal - example 1 .............................................................................................................................. 34
Figure 3-5: Elevator pre-signal - example 2 .............................................................................................................................. 34
Figure 3-6: Elevator pre-signal - example 3 .............................................................................................................................. 34
Figure 3-7: Source priority selection - S1 preferred .................................................................................................................. 37
Figure 3-8: Source priority selection - S2 preferred .................................................................................................................. 37
Figure 3-9: Load shed relay wiring - standard transition switch ............................................................................................... 41
Figure 3-10: Load shed relay wiring - delayed or closed transition switch ............................................................................... 41
Figure 3-11: Open transition switch - connected to source 1 .................................................................................................... 42
Figure 3-12: Open transition switch - connected to source 2 .................................................................................................... 42
Figure 3-13: Delayed transition switch - connected to source 1 ............................................................................................... 43
Figure 3-14: Delayed transition switch - neutral position ......................................................................................................... 43
Figure 3-15: Delayed transition switch - connected to source 2 ............................................................................................... 43
Figure 3-16: Closed transition switch - connected to source 1 .................................................................................................. 44
Figure 3-17: Closed transition switch - neutral position ........................................................................................................... 44
Figure 3-18: Closed transition switch - connected to source 1 and 2 (overlap position) ........................................................... 44
Figure 3-19: Closed transition switch - connected to source 2 .................................................................................................. 44
Figure 3-20: Breaker - transition pulse ..................................................................................................................................... 47
Figure 3-21: Inphase monitoring............................................................................................................................................... 62
Figure 3-22: Switch reaction time ............................................................................................................................................. 65
Figure 3-23: Monitoring - load time-overcurrent ...................................................................................................................... 68
Figure 3-24: Monitoring - overload .......................................................................................................................................... 70
Figure 3-25: Monitoring - battery overvoltage.......................................................................................................................... 73
Figure 3-26: Monitoring - battery undervoltage........................................................................................................................ 75
Figure 3-27: Discrete inputs - control inputs - operation logic ................................................................................................. 78
Figure 3-28: Interfaces - Principle of PDO mapping ................................................................................................................ 89
Figure 3-29: LogicsManager - function overview .................................................................................................................. 102
Figure 3-30: LogicsManager - display in LeoPC .................................................................................................................... 103
Figure 3-31: LogicsManager - display in LCD ....................................................................................................................... 103
Figure 3-32: GetEventLog - interface configuration ............................................................................................................... 123
Figure 3-33: GetEventLog - event logger content................................................................................................................... 124
Figure 3-34: GetEventLog - event logger content in Excel..................................................................................................... 124
Tables
Table 1-1: Manual - overview ..................................................................................................................................................... 8
Table 3-1: Application - load shed with standard transition switch .......................................................................................... 40
Table 3-2: Application - load shed with delayed or closed transition switch ............................................................................ 41
Table 3-3: Calculation of the phase angle deviation ................................................................................................................. 66
Table 3-4: Monitoring - standard values - load time-overcurrent.............................................................................................. 68
Table 3-5: Monitoring - standard values - overload .................................................................................................................. 70
Table 3-6: Monitoring - standard values - battery overvoltage ................................................................................................. 73
Table 3-7: Monitoring - standard values - battery undervoltage ............................................................................................... 75
Table 3-8: Discrete inputs - assignment .................................................................................................................................... 78
Table 3-9: Discrete inputs - parameter IDs ............................................................................................................................... 79
Table 3-10: External discrete inputs - parameter IDs ................................................................................................................ 79
Table 3-11: Relay outputs - Assignment ................................................................................................................................... 80
Table 3-12: Discrete outputs - parameter IDs ........................................................................................................................... 81
Table 3-13: External discrete outputs - parameter IDs .............................................................................................................. 81
Table 3-14: Internal flags - parameter IDs ................................................................................................................................ 83
Table 3-15: Daylight saving time - configuration example ....................................................................................................... 96
Table 3-16: LogicsManager - command overview ................................................................................................................. 102
Table 3-17: LogicsManager - logical symbols ........................................................................................................................ 103
Table 3-18: Event logger - event texts and numbers ............................................................................................................... 125
Chapter 1.
General Information
DTSC-200 Series
DTSC-200 - Installation 37385 -
DTSC-200 - Configuration this manual 37386 -
DTSC-200 - Operation 37387 -
DTSC-200 - Application 37388 -
DTSC-200 - Interfaces 37389 -
Additional Manuals
IKD 1 - Manual 37135 GR37135
Discrete expansion board with 8 discrete inputs and 8 relay outputs that can be coupled via the CAN bus to the control unit.
Evaluation of the discrete inputs as well as control of the relay outputs is done via the control unit.
LeoPC1 - User Manual 37146 GR37146
PC program for visualization, configuration, remote control, data logging, language upload, alarm and user management, and
management of the event recorder. This manual describes the set up of the program and interfacing with the control unit.
LeoPC1 - Engineering Manual 37164 GR37164
PC program for visualization, configuration, remote control, data logging, language upload, alarm and user management, and
management of the event recorder. This manual describes the configuration and customization of the program.
Table 1-1: Manual - overview
Intended Use The unit must only be operated for the uses described in this manual. The prerequisite for a proper
and safe operation of the product is correct transportation, storage, and installation as well as careful operation
and maintenance.
NOTE
This manual has been developed for a unit fitted with all available options. Inputs/outputs, functions,
configuration screens and other details described, which do not exist on your unit may be ignored.
The present manual has been prepared to enable the installation and commissioning of the unit. On
account of the large variety of parameter settings, it is not possible to cover every possible
combination. The manual is therefore only a guide. In case of incorrect entries or a total loss of
functions, the default settings can be taken from the enclosed list of parameters at the rear of this
manual.
Chapter 2.
Configuration
NOTE
Please note that configuration using the direct configuration cable DPC (product number 5417-557) is
possible starting with revision B of the DPC (first delivered July 2003). If you have an older model
please contact our sales department.
NOTE
The connection cables delivered with the DPC must be used to connect to the DTSC to ensure that the
controller functions properly. An extension or utilization of different cable types for the connection
between DTSC and DPC may result a malfunction of the DTSC. This may possibly result in damage to
components of the system. If an extension of the data connection line is required, only the serial cable
between DPC and laptop/PC may be extended.
NOTE
If the laptop/PC fails to communicate with the control unit being configured, refer to LeoPC1 manual
37146.
NOTE
Depending on the used computer and the installed operation system, problems with the
communication via an infrared connection may occur.
NOTE
If you want to read or write parameters using a [LeoPC1 Gateway-RS-232 via GW4] connection, you
must configure the parameter "Visualization" to "not active" in LeoPC1. The parameter "Visualization"
may be configured back to "active" after reading and/or writing.
General Information
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The DTSC-200 has been developed to control ATS (Automatic Transfer Switch) units.
The main purpose of the ATS controller is to control and monitor the transfer switch as well as issuing an engine
start signal to a connected genset control. The controller is continuously monitoring the presence of a source. If
the preferred source fails, it attempts to transfer to a second source (emergency power supply, etc.).
It is NOT the task of an ATS controller to monitor a start/stop sequence. Start and stop failures will be displayed,
but have no effect on the functionality of the controller. Only switch failures or problems with connected position
limit switches, which signal the actual position of the ATS (connected with utility or connected with emergency
power supply, etc.) to the controller, block the ATS controller for further automatic functions.
Important Designations
• Source 1 Usually the preferred power source, e.g. utility supply (depends on application)
• Source 2 Usually the emergency power source, e.g. genset (depends on application)
• Transfer Change from one source to the other
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 failure
NOTE
If one of these monitoring functions is triggered, the 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 may be 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-8 on page 78.
Reply from ATS limit switch: Breaker in source 1 position fixed to discrete input [DI 1], terminal 51/50
Note: Normally closed (break) contact!
This discrete input indicates to the control that the breaker is closed to source 1 position if it is de-
energized (logic "0").
Reply from ATS limit switch: Breaker in source 2 position fixed to discrete input [DI 2], terminal 52/50
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 53/50
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 with standard transfer switch type.
Reply from ATS limit switch: Breaker in source 2 open position fixed to discrete input [DI 4], terminal 54/50
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 with standard transfer switch type.
Disconnect switch: Inhibit ATS programmable to discrete input [DI 5], terminal 55/50
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.
Control Inputs programmable to discrete inputs [DI 6] through [DI 12], terminals 56 through 62 / 50
These discrete inputs may be used as control signals for functions, like priority selection, remote peak
shave, inhibit transfer, etc. The control inputs can be configured freely. Please refer to Discrete Inputs
on page 68.
Relay Outputs
The discrete outputs can be 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-11 on page 80.
LogicsManager Relay {all} programmable to relay [R1] through [R3], terminals 32 through 34 / 31
Note: Normally open (make) contact!
All relays not assigned a defined function, may be configured via the LogicsManager.
All relays not assigned 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 42/43
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-definedto relay [R7], terminals 44/45
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 46/47
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 48/49
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 thereby
described as follows.
Caption
Brief description of the parameter.
Setting range
Setting limits, valid for these parameter.
Text German
DE
Explanations
Exact description of the parameter, its settings as well
as their effects.
Validity
{0}: Valid for Util-Util application mode (0 gens)
{1}: Valid for Util-Gen application mode (1 gens)
{2}: Valid for Gen-Gen application mode (2 gens)
Parameter Display
[CSx] = Visible in code level x
[p] = Parameter number
[L] = Only displayed in LeoPC1 for configuration
Language
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The following parameter is used to set the unit display language.
Language
DE
CS0 {0} {1} {2} The desired language for the unit display text is configured here.
1700
Password
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The DTSC-200 utilizes a password protected multi-level configuration access hierarchy. This permits varying
degrees of access to the parameters being granted by assigning unique passwords to designated personnel. A
distinction is made between the access levels as follows:
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
LeoPC 1.
Passwort
DE
CS0 {0} {1} {2} The password for configuring the control via the front panel must be entered here.
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:
Operation of manual 37387. The operation states, which are stored in the event history, are listed in the table
below.
The event history display is password-protected.
Refer to Appendix B: GetEventLog starting at page 123 for a description about reading out the event logger using
a software tool.
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 "-".
Ereignisspeicher anzeigen
DE
CL2 {0} {1} {2} Individual entries can be selected with the or keys and deleted from the event
history with the key.
NOTE
Refer to Table 3-18 on page 125 for a complete list of all entries, which may appear in the event history.
Ereignisspeicher löschen
DE
CL2 {0} {1} {2} YES .............. The complete event history will be deleted. After the event history
1706 has been deleted, this parameter changes back to "NO" automatically.
NO................ The event history will not be deleted.
Measuring
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
NOTE
This controller is available in two different hardware version with either 1A [../1] or 5A [../5] current
transformer inputs. Both versions are discussed in this manual. The set points for specific parameters
will differ depending upon the hardware version.
NOTE
It is absolutely necessary for correct rated voltage values to be entered, as many measurement and
monitoring functions refer to these values.
Nennfrequenz im System
DE
CL2 {0} {1} {2} The rated frequency of the system is used as a reference figure for all frequency
1750
related functions, which use a percentage value, like frequency monitoring or
breaker operation windows.
Nennspannung S1
DE
CL2 {0} {1} {2} This value refers to the rated voltage of source 1 and is the voltage
1774 measured on the potential transformer primary.
The source 1 potential transformer primary voltage is entered in this parameter. The
source 1 rated voltage is used as a reference figure for all source 1 voltage related
functions, which use a percentage value, like utility voltage monitoring or breaker
operation windows.
Nennspannung S2
DE
CL2 {0} {1} {2} This value refers to the rated voltage of source 2 and is the voltage
1772 measured on the potential transformer primary.
The source 2 potential transformer primary voltage is entered in this parameter. The
source 2 rated voltage is used as a reference figure for all source 2 voltage related
functions, which use a percentage value, like utility voltage monitoring or breaker
operation windows.
EN
S1 Spannungsmessung
DE
CL2 {0} {1} {2} Please refer to the comments on measuring principles in the installation
1862 manual (37385).
EN
S2 voltage measuring Measurement principle: Source 2 3Ph 4W / 3Ph 3W / 1Ph 2W / 1Ph 3W
S2 Spannungsmessung
DE
CL2 {0} {1} {2} Please refer to the comments on measuring principles in the installation
1861 manual (37385).
CL2 {0} {1} {2} Please refer to the comments on measuring principles in the installation
1858 manual (37385).
CL2 {0} {1} {2} Please refer to the comments on measuring principles in the installation
1859 manual (37385).
S1 Load current measuring Measurement principle: S1 Load current L1 L2 L3 / Phase L1 / Phase L2 / Phase L3
EN
S1 Last Strommessung
DE
CL2 {0} {1} {2} Please refer to the comments on measuring principles in the installation
1863 manual (37385).
L1 L2 L3 ...... All three phases are monitored. The measurement, display and
protection are adjusted according to the rules for 3-phase
measurement. Monitoring refers to the following currents:
• IL1, IL2, IL3.
Phase L{1/2/3} Only one phase is monitored. The measurement, display and
protection are adjusted according to the rules for single-phase
measurement. Monitoring refers to the selected phase.
Current and power from source 1 to the load are only measured, if the transfer
switch is closed to source 1 position (S1).
The parameters 1860 and 1863 must be configured identical because they share one
common CT set at the load connection.
S2 Load current measuring Measurement principle: S2 Load current L1 L2 L3 / Phase L1 / Phase L2 / Phase L3
EN
S2 Last Strommessung
DE
CL2 {0} {1} {2} Please refer to the comments on measuring principles in the installation
1860 manual (37385).
L1 L2 L3 ...... All three phases are monitored. The measurement, display and
protection are adjusted according to the rules for 3-phase
measurement. Monitoring refers to the following currents:
• IL1, IL2, IL3.
Phase L{1/2/3} Only one phase is monitored. The measurement, display and
protection are adjusted according to the rules for single-phase
measurement. Monitoring refers to the selected phase.
Current and power from source 2 to the load are only measured, if the transfer
switch is closed to source 2 position (S2).
The parameters 1860 and 1863 must be configured identical because they share one
common CT set at the load connection.
NOTE
It is absolutely necessary for correct rated power and current values to be entered, as many
measurement and monitoring functions refer to these values.
Nennwirkleistung [kW]
DE
CL2 {0} {1} {2} This value specifies the rated power.
1752
Nennstrom
DE
CL2 {0} {1} {2} This value specifies the rated current.
1754
Measuring: Transformers
Voltage Transformer
S1 Spannungswandler primär
DE
CL2 {0} {1} {2} Some applications may require the use of potential transformers to facilitate
1819
measuring the source voltages. The rating of the primary side of the potential
transformer on source 1 must be entered into this parameter.
If the application does not require potential transformers (i.e. the generated voltage
is 480 V or less), then the source volt. will be entered into this parameter.
S1 Spannungswandler sekund.
DE
CL2 {0} {1} {2} The control is equipped with dual voltage measuring inputs. The voltage
1818 range of these measurement inputs is dependent upon input terminals are
used (see below). This value refers to the secondary voltages of the
potential transformers, which are directly connected to the control.
• Rated voltage: 100 Vac (this parameter configured between 50 and 130 V)
- Source 1 voltage: Terminals 15/17/19/21
• Rated voltage: 400 Vac (this parameter configured between 131 and 480 V)
- Source 1 voltage: Terminals 16/18/20/22
S2 Spannungswandler primär
DE
CL2 {0} {1} {2} Some applications may require the use of potential transformers to facilitate
1816 measuring the source voltages. The rating of the primary side of the potential
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.
S2 Spannungswandler sekund.
DE
CL2 {0} {1} {2} The control is equipped with dual voltage measuring inputs. The voltage
1815 range of these measurement inputs is dependent upon input terminals are
used (see below). This value refers to the secondary voltages of the
potential transformers, which are directly connected to the control.
• Rated voltage: 100 Vac (this parameter configured between 50 and 130 V)
- Source 2 voltage: Terminals 23/25/27/29
• Rated voltage: 400 Vac (this parameter configured between 131 and 480 V)
- Source 2 voltage: Terminals 24/26/28/30
Current Transformer
NOTE
This controller is available in two different hardware version with either 1A [../1] or 5A [../5] current
transformer inputs. Both versions are discussed in this manual. The set points for specific parameters
will differ depending upon the hardware version, indicated on the data plate.
• [1] DTSC-200-1 = Current transformer with ../1 A rated current
• [5] DTSC-200-5 = Current transformer with ../5 A rated current
Last Stromwandler
DE
CL2 {0} {1} {2} This screen only applies to controls equipped with 5 A CT inputs. This
1821
will not be displayed in the controller screen of a unit equipped with 1 A
CT inputs.
The input of the current transformer ratio is necessary for the indication and
control of the actual monitored value. The current transformers ratio should be
selected so that at least 60% of the secondary current rating can be measured
when the monitored system is at 100% of operating capacity (i.e. at 100% of
system capacity a 5 A CT should output 3 A). If the current transformers are sized
so that the percentage of the output is lower, the loss of resolution may cause
inaccuracies in the monitoring and control functions and affect the functionality
of the control.
Last Stromwandler
DE
CL2 {0} {1} {2} This screen only applies to controls equipped with 1 A CT inputs. This
1822 will not be displayed in the controller screen of a unit equipped with 5 A
CT inputs.
The input of the current transformer ratio is necessary for the indication and
control of the actual monitored value. The current transformers ratio should be
selected so that at least 60% of the secondary current rating can be measured
when the monitored system is at 100% of operating capacity (i.e. at 100% of
system capacity a 5 A CT should output 3 A). If the current transformers are sized
so that the percentage of the output is lower, the loss of resolution may cause
inaccuracies in the monitoring and control functions and affect the functionality
of the control.
Application
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Application: Application Mode
Betriebsmodus
DE
CL2 {0} {1} {2} This parameter selects the basic function of the unit. If the unit is used to transfer
4148 the load between two utility sources (setting "Util-Util"), no engine start signals are
issued.
Source 1 Source 2
Util-Gen .......Standard application "utility-generator" {1}
Engine start signals will be issued for source 2 only.
G
Source 1 Source 2
Gen-Gen .......Application "generator-generator" {2}
Engine start signals will be issued for source 1 and source 2.
G G
Source 1 Source 2
NOTE
In Util-Gen application, source S2 is considered as the generator.
EN
Transfer zustimmen
DE
CL2 {0} {1} {2} This function is only effective if a transfer from the preferred source to the non-
4146 --- --- preferred source is requested.
S1 Startverzögerung
DE
CL2 {0} {1} {2} This parameter delays the de-energizing of the start relay (and thus the 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 de-energized, the engine will be started, and flag 20.05 "S1 Start
Signal" will be enabled.
If this timer is running, the "S1 start delay" message and the Bypass softkey are
displayed.
S2 Startverzögerung
DE
CL2 {0} {1} {2} This parameter delays the de-energizing of the start relay (and thus the 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 be de-energized, 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.
EN
S1 Source Stable time Source 1 source stable time 1 to 6500 s
S1 Stabilisierzeit
DE
CL2 {0} {1} {2} This parameter configures the delay before source 1 is considered as OK. This
3333 timer starts after the last monitored value has returned within the restore limits
following a source 1 outage. Source 1 will be considered as OK again after this
timer has expired. If the voltage and/or frequency exceeds the restore limits again
before the timer expires, the timer will be reset (refer to Figure 3-2).
The source 1 stable timer is automatically bypassed if source 1 is the preferred
source and the outage delay of source 2 (non-preferred) has expired.
If source 1 fails unexpectedly before this timer has expired, it will be terminated
and the load will still be supplied by source 2.
This timer is intended to delay the transfer to ensure that source 1 voltage and
frequency are definitely stable before the ATS switch is operated to perform a
transfer to source 1.
If this timer is running, the "S1 stable timer" message and the Bypass softkey are
displayed.
NOTE
In case a "load test" is being performed (i.e. the load is supplied by source 2, but source 1 is present as
well and OK) and source 2 fails, the "S1 source stable timer" will be bypassed completely to be able to
change back (OK) to source 1 immediately. This is intended to ensure that the load is not de-energized
if a genset failure takes place during a load test.
S2 Stabilisierzeit
DE
CL2 {0} {1} {2} This parameter configures the delay before source 2 is considered as OK. This
3332 timer starts after the last monitored value has returned within the restore limits
following a source 2 outage. Source 2 will be considered as OK again after this
timer has expired. If the voltage and/or frequency exceeds the restore limits again
before the timer expires, the timer will be reset (refer to Figure 3-2).
The source 2 stable timer is automatically bypassed if source 2 is the preferred
source and the outage delay of source 1 (non-preferred) has expired.
If source 2 fails unexpectedly before this timer has expired, it will be terminated
and the load will still be supplied by source 1.
This timer is intended to delay the transfer to ensure that source 2 voltage and
frequency are definitely stable before the ATS switch is operated to perform a
transfer to source 2.
If this timer is running, the "S2 stable timer" message and the Bypass softkey are
displayed.
EN
S1 Ausfallverzögerung
DE
CL2 {0} {1} {2} This timer defines the maximum time before source 1 (voltage, frequency and
2804 --- --- phase rotation) is considered as "not OK" to initiate a transfer to source 2. This
timer starts if one of the monitored source 1 values exceeds the fail limits. Source 1
will be considered as "not OK", after this timer has expired. If the voltage and/or
frequency returns within the fail limits before the timer expires, the timer will be
reset (refer to Figure 3-2).
This timer is intended to prevent an immediate transfer to source 2 in case of a
temporary voltage or frequency drop during a load test due to a short temporary
failure of source 1 (i.e. ignition miss of a genset, etc.).
If this timer has expired, the alarm "Unint. stop S1" is issued.
Note: If source 2 is the "preferred source" and the "S1 outage delay" timer has
expired (i.e. source 1 is considered as "not OK"), the "S2 source stable timer" will
be bypassed.
S2 Ausfallverzögerung
DE
CL2 {0} {1} {2} This timer defines the maximum time before source 2 (voltage, frequency and
2803 --- phase rotation) is considered as "not OK" to initiate a transfer to source 1. This
timer starts if one of the monitored source 2 values exceeds the fail limits. Source 2
will be considered as "not OK", after this timer has expired. If the voltage and/or
frequency returns within the fail limits before the timer expires, the timer will be
reset (refer to Figure 3-2).
This timer is intended to prevent an immediate transfer to source 1 in case of a
temporary voltage or frequency drop during a load test due to a short temporary
failure of source 2 (i.e. ignition miss of a genset, etc.).
If this timer has expired, the alarm "Unint. stop S2" is issued.
Note: If source 1 is the "preferred source" and the "S2 outage delay" timer has
expired (i.e. source 2 is considered as "not OK"), the "S1 source stable timer" will
be bypassed.
[V], [f]
rated
value source stable timer source stable timer
restore
value
source source OK
not OK
outage outage
delay delay
timer timer
fail
value
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 case, a threshold needs to be fallen below to consider the source as "OK" (like overfrequency,
voltage imbalance or overvoltage), the restore value is lower than the fail value.
S1 Nachlaufzeit
DE
CL2 {0} {1} {2} This parameter configures the duration of the cool down phase of engine 1 after the
3343 --- --- load has been disconnected.
If this timer is running, the "S1 cooldown" message and the Bypass softkey are
displayed.
S2 Nachlaufzeit
DE
CL2 {0} {1} {2} This parameter configures the duration of the cool down phase of engine 2 after the
3344 --- load has been disconnected.
If this timer is running, the "S2 cooldown" message and the Bypass softkey are
displayed.
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 via the LogicsManager by configuration.
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.
Blockiere ATS
DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 in Appendix
12600
A: "LogicsManager".
NOTE
The disconnect switch is ALWAYS inside the ATS cabinet. If the ATS shall be operated manually, the
disconnect switch will be switched to the "Inhibit ATS" position. This blocks the ATS controller against
the automatic initiation of a transfer and the switch may easily be operated manually.
WARNING
If the ATS controller performs a transfer during a service technician switches the ATS with a manual
handle, this may cause serious injuries.
Always inhibit automatic ATS transfers before performing a manual transfer!
Application example:
Supposed, there is a failure of source 1 (preferred source) in a hospital. Then, source 2 will be started and a
transfer to source 2 will be performed. Now, the load is supplied by source 2.
If source 1 would return, a transfer back to source 1 would be initiated. This may be prevented by making this
LogicsManager function TRUE (by energizing a DI for example) because a transfer back to source 1 may cause
some risks if a difficult surgery is in progress for example. A mechanical failure of the transfer switch during
transferring back would be a serious risk for the patient.
Trans S1 sperren
DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 in Appendix
12610 A: "LogicsManager".
This function has the same behavior as the "Inhibit XFR to source 1" function, except that a transfer to source 2
will be prevented.
Trans S2 sperren
DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 in Appendix
12620
A: "LogicsManager".
Spitzenlast Modus
DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 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.
Anforder. Netzbetr.
DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 in Appendix
12660 A: "LogicsManager".
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 in Appendix
12820
A: "LogicsManager".
NOTE
If another timer becomes active immediately after the previous timer has been bypassed, the discrete
input must be de-energized before it may be energized again to bypass the next timer. We recommend
to use 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.
Gen-Gen Aktivieren
DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 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.
Aufzugswarnsignal
DE
CL2 {0} {1} {2} OFF.............. No elevator pre-signal is issued, no elevator pre-signal timer starts
4490 and the LogicsManager flag 20.01 is not enabled.
ON................ The elevator pre-signal will be issued before any transfer and the
LogicsManager flag 20.01 will be enabled. The remaining elevator
pre-signal time is displayed.
Warnsignal Dauer
DE
CL2 {0} {1} {2} The time configured here determines how long the elevator pre-signal is enabled
4491 before the transfer process will be continued. The signal will be disabled again if
the transfer process has been completed.
If this timer is running, the "Pre signal timer" message is displayed.
The following examples show the behavior of the elevator pre-signal for different applications.
Transfer to non-preferred
source is requested &
non-preferred source non-preferred source
has been started stable timer Transfer initiated
This example assumes that the non-preferred source stable timer is configured higher than the EPS timer. If the
EPS timer would be configured higher, it would start together with the stable timer and the transfer is initiated if
all timers have expired.
EPS timer
This example assumes that the non-preferred source stable timer is configured higher than the EPS and the MLD
timer. If the EPS or the MLD timer would be configured higher, they would start together with the stable timer
and the transfer is initiated if all timers have expired.
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.
Lastabwurf
DE
CL2 {0} {1} {2} OFF .............. No motor load disconnect signal is issued, no motor load disconnect
4550 signal timer starts and the LogicsManager flag 20.02 is not enabled.
It will be proceeded with the operation of the transfer switch.
ON ................ The motor load disconnect signal will be issued before any transfer
and the LogicsManager flag 20.02 will be enabled. The remaining
motor load disconnect signal time is displayed with the "Motor Load
Disc." message. After the motor load disconnect timer expires, the
transfer switch will be operated. The signal will be disabled again if
the transfer process has been completed.
CL2 {0} {1} {2} This parameter configures the transfer direction into which the motor load
4553 disconnect signal is enabled.
S1->S2 ......... The motor load disconnect signal is only enabled in this transfer
direction. The LogicsManager flag 20.02 will not be enabled when
transferring from source 2 to source 1.
S1<-S2 ......... The motor load disconnect signal is only enabled in this transfer
direction. The LogicsManager flag 20.02 will not be enabled when
transferring from source 1 to source 2.
Both ............. The motor load disconnect signal is always enabled in both transfer
directions.
Lastabwurfszeit S1
DE
CL2 {0} {1} {2} This parameter configures the maximum duration of the motor disconnect signal
4551 in source 1 to source 2 transfer direction. After the timer has expired, the transfer
to source 2 will be performed
Lastabwurfszeit S2
DE
CL2 {0} {1} {2} This parameter configures the maximum duration of the motor disconnect signal
4552 in source 2 to source 1 transfer direction. After the timer has expired, the transfer
to source 1 will be performed
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.
NOTE
Changing the priority during 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.
S1 Priorität
DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 in Appendix
12680 A: "LogicsManager".
If the LogicsManager function "Source Priority S2" becomes TRUE, source 2 will be considered as preferred.
S2 Priorität
DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 in Appendix
12810 A: "LogicsManager".
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 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 will be declared as the preferred
source, the load remains connected to this source.
If the load is connected to the preferred source and this preferred source will be declared 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 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.
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 in Appendix
12860 A: "LogicsManager".
NOTE
As long as this function is TRUE, parameter 4577 (Max. overlap time) is not effective.
Exception: If parameter 4577 (Max. overlap time) is configured to 0.1 s, an extended parallel time is not
possible regardless of the state of this function.
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 50) is disabled
• a remote peak shave request (parameter 12630 on page 30) is disabled
• an interruptible power rate request (parameter 12660 on page 31) 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 1
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.
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 in Appendix
12870 A: "LogicsManager".
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 must not be changed since this would
lead to a malfunction of the load shed function.
Breaker
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Breaker: Transfer Switch Type
CL2 {0} {1} {2} This parameter configures the type of ATS switch, which is connected to the
3424 controller. The switch logic behavior depends on the setting configured here.
Standard ......An "open transition" switch is selected.
Delayed ........A "delayed transition" switch is selected.
Closed...........A "closed transition" switch is selected.
Load
Figure 3-11: Open transition switch - connected to source 1
Load
Figure 3-12: Open transition switch - connected to source 2
Load
Figure 3-13: Delayed transition switch - connected to source 1
• Position 2: Neutral
Transfer Switch
Source 1 Source 2
Load
Figure 3-14: Delayed transition switch - neutral position
Load
Figure 3-15: Delayed transition switch - connected to source 2
Load
Figure 3-16: Closed transition switch - connected to source 1
• Position 2: Neutral
Transfer Switch
Source 1 Source 2
Load
Figure 3-17: Closed transition switch - neutral position
• Position 3: Synchronized
Transfer Switch
Source 1 Source 2
Load
Figure 3-18: Closed transition switch - connected to source 1 and 2 (overlap position)
Load
Figure 3-19: Closed transition switch - connected to source 2
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.
Use Limit sw. OPEN replies Use limit switch open replies YES / NO
EN
CL2 {0} {1} {2} This parameter may only be enabled (setting "YES") if parameter 3424 on
3434 page 42 is configured to "Delayed" or "Closed". If it is configured to
"Standard", this parameter is always disabled (setting "NO").
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"
temporarily.
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 in
12850 Appendix A: "LogicsManager".
Transition Timers
The "Neutral Time S2 -> S1" parameter is only enabled, if "Delayed" or "Closed" is configured as "Transfer
switch type" (parameter 3424) and inphase monitoring is disabled (parameter 4570).
CL2 {0} {1} {2} This parameter configures the residence time in neutral position when transferring
3426 the load in this transfer direction.
After this timer has expired, the transfer to source 1 will be performed.
The "Neutral Time S2 <- S1" parameter is only enabled, if "Delayed" or "Closed" is configured as "Transfer
switch type" (parameter 3424) and inphase monitoring is disabled (parameter 4570).
CL2 {0} {1} {2} This parameter configures the residence time in neutral position when transferring
3425 the load in this transfer direction.
After this timer has expired, the transfer to source 2 will be performed.
Limit switch reply timeout Limit switch reply timeout 0.1 to 99.9 s
EN
Zeitüberschreitung Rückmeld.
DE
CL2 {0} {1} {2} This parameter configures the maximum waiting time for a feedback signal from
3428
the ATS switch. If no reply is detected within the configured time, a new transition
attempt will be performed after the "Wait time until next XFR attempt"
(parameter 3429) has expired (refer to Figure 3-20 on page 47). 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.
Wait time until next XFR Waiting time until next transition attempt 0.1 to 99.9 s
EN
attempt
Wartezeit vor neuem Transfer This parameter configures the interval following an unsuccessful transition
DE
CL2 {0} {1} {2}
attempt before a new transition attempt is being performed.
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
CL2 {0} {1} {2} This parameter configures the maximum number of unsuccessful transition
3427 attempts before a switch failure will be issued. The counter for the number of
unsuccessful transition attempts will be increased with the start of each waiting
time period (parameter 3429)
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 re-started. If the timer expires again without detecting the S1 reply, the "Fail to close S1" failure is
issued. 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 be 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 re-started. If the timer expires again without detecting the S2 reply, the "Fail to close S2" failure is
issued. 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 be 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. The message is not be displayed
anymore and the 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. The message is not be displayed
anymore and the 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.
Lastprobe
DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 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.
Motor Test
DE
CL2 {0} {1} {2} The LogicsManager and its default settings are explained on page 101 in Appendix
12650 --- A: "LogicsManager".
Monitoring
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Monitoring: Alarm Acknowledgement
Time until horn reset Self acknowledgment of the centralized alarm (horn) 0 to 1,000 s
EN
Zeit Hupenreset
DE
CL2 {0} {1} {2} After each alarm occurs, the alarm LED flashes and the command variable 03.05
1756 (horn) is issued. After the delay time 'time until horn reset' has expired, the flashing
LED changes into a steady light and the command variable 03.05 (horn) is reset.
The alarm LED is illuminated continuously until the alarm has been acknowledged.
Note: If this parameter is configured to 0, the horn will remain active until it will be
acknowledged.
Ext. Quittierung
DE
CL2 {0} {1} {2} It is possible to acknowledge all alarms simultaneously from remote, e.g. with a
12490 discrete input. The command variables of the LogicsManager have to become
TRUE twice.
The first high signal into the discrete input acknowledges the command
variable 03.05 (horn). The second high signal acknowledges all inactive
alarm messages.
The ON-delay time is the minimum time the input signals have to be "1". The OFF-
delay time is the time how long the input conditions have to be "0" before the next
high signal is accepted.
The LogicsManager and its default settings are explained on page 101 in Appendix
A: "LogicsManager".
Rückmeldungswächter
DE
CL2 {0} {1} {2} Limit switch monitoring evaluates the ATS limit switch replies and checks them for
3430 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
37387.
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 LeoPC1.
Spg.-Überwachung S1
DE
CL2 {0} {1} {2} The unit can either monitor the wye voltages (phase-neutral: 3ph-4w, 1ph-3w and
1787 1ph-2w) or the delta voltages (phase-phase: 3ph-3w and 3ph-4w).
! WARNING:
This parameter influences the protective functions.
S1 Unterspannung rücksetzen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1 (parameter 1774 on
4450
page 18).
S1 Unterspannung auslösen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1 (parameter 1774 on
4451 page 18).
This parameter configures the threshold, which must be fallen below to consider
source 1 as "not OK".
S1 Unterfrequenz Wächter
DE
CL2 {0} {1} {2} This parameter configures, whether underfrequency monitoring for source 1 is
4452 performed.
OFF ..............No underfrequency monitoring is performed for source 1.
ON ................Underfrequency monitoring is performed for source 1.
S1 Unterfrequenz rücksetzen
DE
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4453 page 18).
S1 Unterfrequenz auslösen
DE
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4454 page 18)
This parameter configures the threshold, which must be fallen below to consider
source 1 as "not OK".
S1 Überspannung Wächter
DE
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.
S1 Überspannung rücksetzen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1 (parameter 1774 on
4456 page 18).
This parameter configures the threshold, which must be fallen below to consider
source 1 as "OK" again..
S1 Überspannung auslösen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1 (parameter 1774 on
4457 page 18).
S1 Überfrequenz Wächter
DE
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.
S1 Überfrequenz rücksetzen
DE
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4459 page 18).
This parameter configures the threshold, which must be fallen below to consider
source 1 as "OK" again..
S1 Überfrequenz auslösen
DE
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4460 page 18).
S1 Asymmetrie Wächter
DE
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.
S1 Asymmetrie rücksetzen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1 (parameter 1774 on
4462 page 18).
This parameter configures the threshold, which must be fallen below to consider
source 1 as "OK" again..
S1 Asymmetrie auslösen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1 (parameter 1774 on
4463 page 18).
Verzögerung
DE
CL2 {0} {1} {2} If the monitored voltage imbalance of source 1 exceeds the threshold value for the
3914 delay time configured here, an alarm will be issued.
CAUTION
Please ensure during installation that all voltages applied to this unit are wired correctly to both sides
of the circuit breaker. Failure to do so may result in damage to the control unit and/or generation
equipment due to closing the breaker asynchronous or with mismatched phase rotations and phase
rotation monitoring enabled at all connected components (engine, generator, breakers, cable, busbars,
etc.).
This function may block a connection of systems with mismatched phases systems only under the
following conditions:
• The voltages being measured are wired correctly with respect to the phase rotation at the
measuring points (i.e. the voltage transformer in front and behind the circuit breaker)
• The measuring voltages are wired without angular phase shift or interruption from the measuring
point to the control unit
• The measuring voltages are wired to the correct terminals of the control unit (i.e. L1 of the
generator is connected with the terminal of the control unit which is intended for the L1 of the
generator)
Correct phase rotation of the phase voltages ensures that damage will not occur during a transfer to either source
1 or source 2. The voltage phase rotation monitoring checks the phase rotation of the voltages and the configured
phase rotation to ensure they are identical. The directions of rotation are differentiated as "clockwise" and
"counter-clockwise". With a clockwise field the direction of rotation is "L1-L2-L3"; with a counter clockwise
field the direction of rotation is "L1-L3-L2". If the control is configured for a clockwise rotation and the voltages
into the unit are calculated as counterclockwise the alarm will be initiated.
A connection to certain source is only possible if this source has the correct phase sequence. If a source has a
wrong phase sequence, a connection to this source is not possible.
S1 Drehfeldüberwachung
DE
CL2 {0} {1} {2} This parameter configures, whether phase rotation monitoring for source 1 is
4562 performed.
S1 Drehfeld
DE
CL2 {0} {1} {2} This parameter configures the phase rotation of the system. If a different phase
4563 rotation is detected at source 1, source 1 is considered as "not OK" and a transfer to
source 2 is initiated.
EN
Spg.-Überwachung S2
DE
CL2 {0} {1} {2} The unit can either monitor the wye voltages (phase-neutral: 3ph-4w, 1ph-3w and
1786 1ph-2w) or the delta voltages (phase-phase: 3ph-3w and 3ph-4w).
! WARNING:
This parameter influences the protective functions.
S2 Unterspannung rücksetzen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 2 (parameter 1772 on
4465
page 18).
S2 Unterspannung auslösen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 2 (parameter 1772 on
4466 page 18).
This parameter configures the threshold, which must be fallen below to consider
source 2 as "not OK".
S2 Unterfrequenz Wächter
DE
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.
S2 Unterfrequenz rücksetzen
DE
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4468 page 18).
S2 Unterfrequenz auslösen
DE
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4469 page 18)
This parameter configures the threshold, which must be fallen below to consider
source 2 as "not OK".
S2 Überspannung Wächter
DE
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.
S2 Überspannung rücksetzen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 2 (parameter 1772 on
4471 page 18).
This parameter configures the threshold, which must be fallen below to consider
source 2 as "OK" again.
S2 Überspannung auslösen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 2 (parameter 1772 on
4472 page 18).
S2 Überfrequenz Wächter
DE
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.
S2 Überfrequenz rücksetzen
DE
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4474 page 18).
This parameter configures the threshold, which must be fallen below to consider
source 2 as "OK" again..
S2 Überfrequenz auslösen
DE
CL2 {0} {1} {2} This value refers to the Rated system frequency (parameter 1750 on
4475 page 18).
S2 Asymmetrie Wächter
DE
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.
S2 Asymmetrie rücksetzen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 2 (parameter 1772 on
4477 page 18).
This parameter configures the threshold, which must be fallen below to consider
source 2 as "OK" again..
S2 Asymmetrie auslösen
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 2 (parameter 1772 on
4478 page 18).
Verzögerung
DE
CL2 {0} {1} {2} If the monitored voltage imbalance of source 2 exceeds the threshold value for the
3904 delay time configured here, an alarm will be issued.
CAUTION
Please ensure during installation that all voltages applied to this unit are wired correctly to both sides
of the circuit breaker. Failure to do so may result in damage to the control unit and/or generation
equipment due to closing the breaker asynchronous or with mismatched phase rotations and phase
rotation monitoring enabled at all connected components (engine, generator, breakers, cable, busbars,
etc.).
This function may block a connection of systems with mismatched phases systems only under the
following conditions:
• The voltages being measured are wired correctly with respect to the phase rotation at the
measuring points (i.e. the voltage transformer in front and behind the circuit breaker)
• The measuring voltages are wired without angular phase shift or interruption from the measuring
point to the control unit
• The measuring voltages are wired to the correct terminals of the control unit (i.e. L1 of the
generator is connected with the terminal of the control unit which is intended for the L1 of the
generator)
Correct phase rotation of the phase voltages ensures that damage will not occur during a transfer to either source
1 or source 2. The voltage phase rotation monitoring checks the phase rotation of the voltages and the configured
phase rotation to ensure they are identical. The directions of rotation are differentiated as "clockwise" and
"counter-clockwise". With a clockwise field the direction of rotation is "L1-L2-L3"; with a counter clockwise
field the direction of rotation is "L1-L3-L2". If the control is configured for a clockwise rotation and the voltages
into the unit are calculated as counterclockwise the alarm will be initiated.
A connection to certain source is only possible if this source has the correct phase sequence. If a source has a
wrong phase sequence, a connection to this source is not possible.
S2 Drehfeldüberwachung
DE
CL2 {0} {1} {2} This parameter configures, whether phase rotation monitoring for source 2 is
4566 performed.
S2 Drehfeld
DE
CL2 {0} {1} {2} This parameter configures the phase rotation of the system. If a different phase
4567 rotation is detected at source 2, source 2 is considered as "not OK" and a transfer to
source 1 is initiated.
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 effected 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 may lead to damages of the equipment or data loss in the worst case. 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.
EN
Synchrocheck
DE
CL2 {0} {1} {2} This parameter configures, whether inphase monitoring is performed.
4570
OFF.............. No inphase monitoring is performed prior to a transfer.
ON................ Inphase monitoring is performed prior to a transfer. If the phase angle
between both systems is within the permissible limits, the transfer
will be performed.
NOTE
The following voltages are monitored by the inphase monitoring function depending on the
configuration of the measurement principle (parameter 1862 or 1861):
• 4Ph 3W : VL12
• 3Ph 3W : VL12
• 4Ph 3W : VL12 or VL1N depending on the configuration of parameter 1858
• 1Ph 3W : VL1N
If inphase monitoring 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".
Spannungsdifferenz
DE
CL2 {0} {1} {2} This value refers to the Rated voltage Source 1/2 (parameters 1774/1772 on
4571 page 18).
Positive frequency window Positive frequency window for synchronization 0.02 to 0.49 Hz
EN
Maximaler 63escry63e
DE
Schlupf This parameter configures the maximum permissible positive frequency difference
CL2 {0} {1} {2}
between source 2 and source 1 (Δf = S2-S1).
4572
If the frequency difference is not within the limits configured here, the
synchronization will not be enabled because the frequency difference of the source
to be connected to is too high.
Negative frequency window Negative frequency window for synchronization -0.02 to -0.49 Hz
EN
Maximaler 63escry63e
DE
Schlupf This parameter configures the minimum permissible negative frequency difference
CL2 {0} {1} {2}
between source 2 and source 1 (Δf = S2-S1).
4573
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.
Exception: If the maximum overlap time is configured to 0.1 s, an extended parallel time is not possible
regardless of the state of this function.
If a closed transition is performed, the overlap time of the make-before-break process, in which both sources are
parallel, is less than 100 ms. If this time is to be extended, an overlap timer is available to keep the transition
switch in overlap position for a configured time. The timer starts as soon as the transition switch is in overlap
position. The source, from which the transfer has been initiated, will be disconnected and the load will be
supplied by the new source as soon as this timer has expired.
Max. Synchronzeit
DE
CL2 {0} {1} {2} 0.10 ...............If the maximum overlap time is configured to 0.10 s, an overlap time
4577
below 100 ms, which depends on the used transfer switch, will be
effective and "Extended parallel time" (parameter 12860) is disabled.
0.11 - 9.99 .....The time for which the transfer switch shall remain in overlap
position is configured here.
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
EN
Schaltzeit bei nicht Überlapp.
DE
CL2 {0} {1} {2} The time, which is required by the switch in open transition mode to open from
4578
one source and close to the other source, is configured here.
This time is required for calculating the lead angle for inphase transfers.
Closed trans. Switch reac. Time Closed transition switch reaction time 15 to 300 ms
EN
CL2 {0} {1} {2} The time, which is required by the switch in closed transition mode to close to the
4583 other source to get parallel, is configured here.
This time is required for calculating the lead angle for inphase transfers.
t Transfer
WARNING
Ensure the following parameters are configured correctly to prevent wrong synchronization settings.
Incorrect wiring of the system cannot be compensated with this parameter!
Vector group angle adjustment Vector group angle adjustment -180° to 180°
EN
CL2 {0} {1} {2} This parameter compensates for phase angle deviations, which can be caused by
4581
transformers (i.e. a delta to wye transformer) located within the electrical system.
Ensure the following parameters are configured correctly to prevent wrong
synchronization settings. Incorrect wiring of the system cannot be compensated
for with this parameter!
Please act as follows: If a transformer is not located between systems [A] and [B]
or if the transformer has a vector group without a phase angle deviation, then a
phase angle deviation of 0° should be configured in this parameter.
CAUTION
The correct setting must be validated in every control unit with a differential voltage measurement!
2. Interconnection of the mains voltage not possible but the vector group of the transformer is known
The vector group of the transformer is known and states the phase angle deviation in multiplies of 30°. Out of the
vector group the phase angle deviation α can be calculated as an angle from 0° to 360°. For this value the
voltage of the low voltage side is behind the voltage of the high voltage side phase angle deviation α!
When calculating the resulting value, the low voltage side of the transformer always lags behind the high
voltage side (phase angle deviation α).
High voltage side = System [A] High voltage side = System [B]
α < 180 ° α -α
α > 180 ° -360 ° + α 360 ° - α
Table 3-3: Calculation of the phase angle deviation
Source 1 Example 1
System [B] is connected to source 2. Source 2 voltage is connected to the low voltage
side of a transformer with the vector group Dyn5. The source 1 breaker is connected to
[A] the high voltage side, which connects the transformer to the mains. System [A] is
connected to source 1. Because of the transformer the phase angles at the breaker differ
on/off
DTSC-200
between the measuring voltages of system [A] and system [B]. A phase angle deviation
CB
[B]
High voltage side exists which can be compensated with the DTSC-200.
Dyn5 Using the vector group 5 (Dyn5) it counts α = 5 × 30 ° = 150 °. Because 150 ° < 180 °
∆:Y and system [A] is connected to the high voltage side this results into α to be used as
phase difference. Enter 150 ° into as parameter for the phase difference.
Low voltage side
Source 1 Example 2
Data identical with example 1, but the vector group is Yd11.
DTSC-200
360 ° + α) to be used as phase difference. Enter -30 ° into as parameter for the phase
CB
[B]
High voltage side difference.
Source 2
CAUTION
The correct setting must be validated in every control unit with a differential voltage measurement!
EN
Synchr. Zeitüberschr.
DE
CL2 {0} {1} {2} This parameter configures the maximum time for attempting to detect
4576
synchronicity. 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.
CL2 {0} {1} {2} This parameter determines the behavior of the unit following an unsuccessful
4582 synchronicity detection using the following options:
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 a synchronicity between the two sources. If
no synchronicity 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.
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]
EN
Überwachung
DE
CL2 {0} {1} {2} ON................ Overcurrent monitoring is carried out according to the following
2200 parameters. Monitoring is performed at three levels. All three values
2206
2212 may be configured independent from each other (prerequisite:
Level 1 < Level 2 < Level 3).
OFF.............. Monitoring is disabled for level 1, level 2, and/or level 3.
Limit Load overcurrent, TOC: Threshold value (Level 1/Level 2/Level 3) 50.0 to 300.0 %
EN
Limit
DE
CL2 {0} {1} {2} This value refers to the Rated current (parameter 1754, see page 18).
2204
2210
2216 The percentage values that are to be monitored for each threshold limit are defined
here. If this value is reached or exceeded for at least the delay time without
interruption, an alarm is issued.
Delay Load overcurrent, TOC: Delay (Level 1/Level 2/Level 3) 0.02 to 99.99 s
EN
Verzögerung
DE
CL2 {0} {1} {2} If the monitored load current exceeds the threshold value for the delay time
2205 configured here, an alarm will be issued. If the monitored load current falls below
2211
2217 the threshold (minus the hysteresis) before the delay expires the time will be reset.
Self acknowledge Load overcurrent, TOC: Self acknowledgment (Level 1/Level 2/Level 3) ON / OFF
EN
Selbstquittierend
DE
CL2 {0} {1} {2} YES .............. The control automatically clears the alarm if it is no longer valid.
2202
2208
NO................ An automatic reset of the alarm does not occur. The reset occurs
2214 manually by pressing the appropriate buttons, by activating the
LogicsManager output "External acknowledgement" via an discrete
input, or via an interface.
Monitoring: Overload
Power is monitored depending on the parameters 1861 "S2 voltage measuring", 1862 "S1 voltage measuring",
1860 "S2 Load current measuring" and 1863 "S1 Load current measuring". Only the power of the source, which
is connected to the load, is measured, because the CT is located at the load connection. If the real power is above
the configured limit an alarm will be issued.
If this protective function is triggered, the alarm list indicates "Overload 1" or "Overload 2".
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)
EN
Überwachung
DE
CL2 {0} {1} {2} ON................ Overload monitoring is carried out according to the following
2300 parameters. Monitoring is performed at two levels. Both values may
2306
be configured independent from each other (prerequisite: limit 1
< limit 2).
OFF.............. Monitoring is disabled for level 1 and/or level 2.
Limit
DE
CL2 {0} {1} {2} This value refers to the Rated active power (parameter 1752, see page 18).
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.
Verzögerung
DE
CL2 {0} {1} {2} If the monitored load exceeds the threshold value for the delay time configured
2305 here, an alarm will be issued. If the monitored load falls below the threshold (minus
2311
the hysteresis) before the delay expires the time will be reset.
Selbstquittierend
DE
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
EN
S1 Startfehler Zeit
DE
CL2 {0} {1} {2} If the "S1 start delay" timer has expired, the engine start signal will be issued. If the
3341 --- ---
"engine start" relay de-energizes, "Source 1 start fail delay" timer starts to count.
Now, the controller expects the engine to start within the time configured here. If
this time will be exceeded, a "Start Fail" alarm will be issued.
S2 start fail delay time Source 2 start fail: delay time 1 to 6500 s
EN
S2 Startfehler Zeit
DE
CL2 {0} {1} {2} If the "S2 start delay" timer has expired, the engine start signal will be issued. If the
3331 "engine start" relay de-energizes, "Source 2 start fail delay" timer starts to count.
Now, the controller expects the engine to start within the time configured here. If
this time will be exceeded, a "Start Fail" 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)
EN
Monitoring Battery overvoltage: Monitoring (Level 1/Level 2) ON / OFF
Überwachung
DE
CL2 {0} {1} {2} ON ................Overvoltage monitoring of the battery voltage is carried out
3450 according to the following parameters.
3456
OFF ..............Monitoring is disabled for level 1 and/or level 2.
Limit
DE
CL2 {0} {1} {2} The threshold values that are to be monitored are defined here. If the monitored
3454 battery voltage reaches or exceeds this value for at least the delay time without
3460
interruption, an alarm is issued.
Verzögerung
DE
CL2 {0} {1} {2} If the monitored battery voltage exceeds the threshold value for the delay time
3455 configured here, an alarm will be issued. If the monitored battery voltage falls
3461
below the threshold (minus the hysteresis) before the delay expires the time will be
reset.
Selbstquittierend
DE
CL2 {0} {1} {2} YES ..............The control automatically clears the alarm if it is no longer valid.
3452 NO ................An automatic reset of the alarm does not occur. The reset occurs
3458
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)
EN
Monitoring Battery undervoltage: Monitoring (Level 1/Level 2) ON / OFF
Überwachung
DE
CL2 {0} {1} {2} ON ................Undervoltage monitoring of the battery voltage is carried out
3500 according to the following parameters.
3506
OFF ..............Monitoring is disabled for level 1 and/or level 2.
Limit
DE
CL2 {0} {1} {2} The threshold values that are to be monitored are defined here. If the monitored
3504 battery voltage reaches or falls below this value for at least the delay time without
3510
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).
Verzögerung
DE
CL2 {0} {1} {2} If the battery voltage falls below the threshold value for the delay time configured
3505 here, an alarm will be issued. If the battery voltage exceeds the threshold (plus the
3511
hysteresis) again before the delay expires the time will be reset.
Selbstquittierend
DE
CL2 {0} {1} {2} YES ..............The control automatically clears the alarm if it is no longer valid.
3502 NO ................An automatic reset of the alarm does not occur. The reset occurs
3508
manually by pressing the appropriate buttons, by activating the
LogicsManager output "External acknowledgement" via an discrete
input, or via an interface.
Überwachung
DE
CL2 {0} {1} {2} ON................ Monitoring of the CANopen interface is carried out according to the
3150 following parameters.
OFF.............. Monitoring is disabled.
Verzögerung
DE
CL2 {0} {1} {2} The delay is configured with this parameter. If the interface does not receive a
3154 CANopen protocol message before the delay expires, an alarm is issued. The delay
timer is re-initialized after every message is received.
Selbstquittierend
DE
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] 51 Reply from ATS limit switch: Breaker in source 1 position [S1]
[DI 2] 52 Reply from ATS limit switch: Breaker in source 2 position [S2]
[DI 3] 53 Reply from ATS limit switch: Breaker in source 1 open position [S1O] #1
[DI 4] 54 Reply from ATS limit switch: Breaker in source 2 open position [S2O] #1
[DI 5] 55 Control input (LogicsManager), pre-assigned with Inhibit ATS
[DI 6] 56 Control input (LogicsManager)
[DI 7] 57 Control input (LogicsManager)
[DI 8] 58 Control input (LogicsManager)
[DI 9] 59 Control input (LogicsManager)
[DI 10] 60 Control input (LogicsManager)
[DI 11] 61 Control input (LogicsManager)
[DI 12] 62 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-8: Discrete inputs - assignment
Discrete inputs may be configured to normally open (N.O.) or normally closed (N.C.) states. In the state N.O., no
potential is present during normal operation; if a control operation is performed, the input is energized. In the
state N.C., a potential is continuously present during normal operation; if a control operation is performed, the
input is de-energized.
Vdc (GND)
Discrete input (N.O.)
GND (Vdc)
Vdc (GND)
Discrete input (N.C.)
GND (Vdc)
Figure 3-27: Discrete inputs - control inputs - operation logic
NOTE
The discrete inputs for the breaker position reply messages (DIs 1 through 4) are fixed to N.C. and are
evaluated as N.C., i.e. the breaker is considered as "in position" if the respective DI is de-energized.
EN
DI {x} Funktion
DE
CL2 {0} {1} {2} The discrete inputs may be operated by an normally open (N.O.) or normally closed
1281 (N.C.) contact. The idle circuit current input can be used to monitor for a wire
break. A positive or negative voltage polarity referred to the reference point of the
DI may be applied.
N.O............... The discrete input is analyzed as "enabled" by energizing the input
(normally open).
N.C. .............. The discrete input is analyzed as "enabled" by de-energizing the input
(normally closed).
DI {x} Verzögerung
DE
CL2 {0} {1} {2} A delay time in seconds can be assigned to each alarm or control input. The discrete
1280 input must be enabled without interruption for the delay time before the unit reacts.
If the discrete input is used within the LogicsManager this delay is taken into
account as well.
The preceding parameters are used to configure the discrete inputs 5 through 12. The parameter IDs refer to DI 5.
Refer to Table 3-9 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 126 and cannot be configured. However, the 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-9: Discrete inputs - parameter IDs
If a Woodward IKD 1 or other external expansion board (Phoenix BK 16DiDo/Co 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-10 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-10: 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 1] 31/32 LogicsManager
[R 2] 31/33 LogicsManager
[R 3] 31/34 LogicsManager
[R 4] 35/36/37 LogicsManager
[R 5] 39/40/41 LogicsManager (pre-defined with engine 2 start)
[R 6] 42/43 LogicsManager (pre-defined with command: close to source 1 position) [C1]
[R 7] 44/45 LogicsManager (pre-defined with command: close to source 2 position) [C2]
[R 8] 46/47 LogicsManager (pre-defined with command: open from source 1 to neutral position) [C1O]
[R 9] 48/49 LogicsManager (pre-defined with command: open from source 2 to neutral position) [C2O]
External relay output (via CANopen; not included in DTSC-200 delivery; can be an expansion card like IKD1)
[Rex01] --- LogicsManager
[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-11: Relay outputs - Assignment
EN
Relais {x}
DE
CL2 {0} {1} {2} Once the conditions of the LogicsManager have been fulfilled, the relay will be
12100 energized. The LogicsManager and its default settings are explained on page 101 in
Appendix A: "LogicsManager".
Above parameter IDs refers to R 1. Refer to Table 3-12 for the parameter IDs of the parameters for R 2 to R 9.
R1 R2 R3 R4 R5 R6 R7 R8 R9
Parameter ID 12100 12110 12310 12320 12130 12140 12150 12160 12170
Table 3-12: Discrete outputs - parameter IDs
If a Woodward IKD 1 or other external expansion board (Phoenix BK 16DiDo/Co 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-13 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-13: External discrete outputs - parameter IDs
Counters
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Configure Counters: Operation Hours, kWh, and kvarh
Counter value preset Counter: Set point value for counters 0 to 99,999,999
EN
Zähler-Setzwert
DE
CL2 {0} {1} {2} This value is utilized to set the hours in the following parameters:
2515
• kWh counter
• kvarh counter
The number entered into this parameter is the number that will be set to the
parameters listed above when they are enabled.
S1 Wirkarbeit [0,00MWh]
DE
CL2 {0} {1} {2} YES .............. The current value of this counter is overwritten with the value
2514 configured in "set point value for counters". After the counter has
been (re)set, this parameter changes back to "NO" automatically.
NO ............... The value of this counter is not changed.
S1 Blindarbeit [0,00Mvarh]
DE
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.
S2 Wirkarbeit [0,00MWh]
DE
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.
S2 Blindarbeit [0,00Mvarh]
DE
CL2 {0} {1} {2} YES .............. The current value of this counter is overwritten with the value
2511 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.
NOTE
Example: The counter value preset (parameter 2515 on page 82) 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 101 in chapter "LogicsManager").
Merker {x]
DE
CL2 {0} {1} {2} The flags may be used as auxiliary flags for complex combinations by using the
yyyyy logical output of these flags as command variable for other logical outputs.
NOTE
Flag 1 is also used as placeholder in other logical combinations. Flag 8 is preset with a timer start.
LogicsManager: Timer
LogicsManager: Daily Time Set Point
Utilizing the LogicsManager it is possible to establish specific times of the day that functions (i.e. generator
exerciser) can be enabled. The two daily time set points are activated each day at the configured time. Using the
LogicsManager these set points may be configured individually or combined to create a time range.
Setpoint {x}: Hour Timer: Daily time set point {x} [x = 1/2]: hour 0 to 23 h
EN
CL2 {0} {1} {2} Enter the hour of the daily time set point here. Example:
1652 0 ....................0th hour of the day (midnight).
1657
23 ..................23rd hour of the day (11pm).
Setpoint {x}: Minute Timer: Daily time set point {x} [x = 1/2]: minute 0 to 59 min
EN
CL2 {0} {1} {2} Enter the minute of the daily time set point here. Example:
1651 0 ....................0th minute of the hour.
1656
59 ..................59th minute of the hour.
Setpoint {x}: Second Timer: Daily time set point {x} [x = 1/2]: second 0 to 59 s
EN
CL2 {0} {1} {2} Enter the second of the daily time set point here. Example
1650 0 ....................0th second of the minute.
1655
59 ..................59th second of the minute.
Aktiver Tag
DE
CL2 {0} {1} {2} Enter the day of the active switch point here. Example:
1663 01 ..................1st day of the month.
31 ..................31st day of the month.
The active time set point is enabled during the indicated day from 0:00:00 hours to
23:59:59 hours.
Aktive Stunde
DE
CL2 {0} {1} {2} Enter the hour of the active switch point here. Example:
1662 0 ....................0th hour of the day.
23 ..................23rd hour if the day.
The active time set point is enabled every day during the indicated hour from
minute 0 to minute 59.
Aktive Minute
DE
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.
EN
Aktive Sekunde
DE
CL2 {0} {1} {2} Enter the second of the active switch point here. Example:
1660 0.................... 0th second of the minute.
59.................. 59th second the minute.
The active time set point is enabled every minute during the indicated second.
Monday active Timer: Weekly time set points Monday: days YES / NO
EN
Montag aktiv
DE
CL2 {0} {1} {2} Please enter the days of the weekly workdays.
1670 Monday ........... YES - The switch point is enabled every Monday
NO - The switch point is disabled every Monday
Tuesday active Timer: Weekly time set points Tuesday: days YES / NO
EN
Dienstag aktiv
DE
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
Wednesday active Timer: Weekly time set points Wednesday: days YES / NO
EN
Mittwoch aktiv
DE
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
Thursday active Timer: Weekly time set points Thursday: days YES / NO
EN
Donnerstag aktiv
DE
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
Friday active Timer: Weekly time set points Friday: days YES / NO
EN
Freitag aktiv
DE
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
Saturday active Timer: Weekly time set points Saturday: days YES / NO
EN
Samstag aktiv
DE
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
Sunday active Timer: Weekly time set points Sunday: days YES / NO
EN
Sonntag aktiv
DE
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 37389 for a detailed description of the interface parameters.
Gerätenummer
DE
CL2 {0} {1} {2} So that this control unit may be positively identified on the CAN bus, the unit
1702 address must be set in this parameter. The address may only be represented once on
the CAN bus. All other addresses on the CAN bus are calculated on the basis of the
address entered in this parameter.
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 to repeat a request, which is not answered within
reasonable time.
Protokoll
DE
CL2 {0} {1} {2} The CAN bus of this unit may be operated with different protocols and Baud rates.
3155 This parameter defines the protocol to be utilized. Please note, that all participants
on the CAN bus must use the same protocol.
OFF ..............The CAN bus is disconnected. Values are not sent or received.
CANopen .....The CANopen protocol is used. More information may be found in
the interface manual 37262 under CANopen.
LeoPC ..........The CAN CAL protocol is used. More information may be found in
the interface manual 37262 under CAN (CAL).
Baudrate CAN bus: Baud rate 20 / 50 / 100 / 125 / 250 / 500 / 800 / 1,000 kBaud
EN
Baudrate
DE
CL2 {0} {1} {2} This parameter defines the used Baud rate. Please note, that all participants on the
3156 CAN bus must use the same Baud rate.
EN
CAN-open Master
DE
CL2 {0} {1} {2} YES .............. The DTSC-200 is the CANopen Master.
9000
The unit automatically changes into operational mode and transmits
Remote Start messages since Broadcast
Attached external devices were configured from the unit with SDO
messages. The unit sends a SYNC message all 20ms on COB ID 80
Hex.
NO................ The DTSC-200 is a CANopen Slave.
CL2 {0} {1} {2} Independent from the CANopen Master configuration, the unit transmits a heartbeat
9120 message with this configured heartbeat cycle time. If the producer heartbeat time is
equal 0, the heartbeat will only be sent as response to a remote frame request. The
time configured here will be rounded up to the next 20 ms step.
CL2 {0} {1} {2} This parameter defines whether the unit generates the SYNC message or not.
9100
Complies with CANopen specification: object 1005, subindex 0; defines the COB ID of the
synchronization object (SYNC). The structure of this object is shown in the following tables:
Max. answer time ext. devices Max response time ext. devices 0.1 to 9.9 s
EN
CL2 {0} {1} {2} The maximum time that an attached external device has to answer an SDO
9010 message. If the external device fails to answer before this time expires, an abort
message is sent and the SDO message will be sent again. This is only effective, if
DTSC-200 CAN open master is enabled.
Time re-init. Ext. devices Time re-init (re-initialization) ext. devices 0 to 9,999 s
EN
CL2 {0} {1} {2} An external device will be configured again with SDO messages after the time set
9009
for this parameter.
If 0 is input in this parameter, the external device will not be configured again with
SDO messages
This only functions if DTSC-200 CAN open master is enabled.
2nd Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
EN
CL2 {0} {1} {2} In a multi-master application, each Master needs its own identifier (Node ID) from
9020
the unit. In order to send remote signals (i.e. acknowledge) to the unit. The
additional SDO channel will be made available by configuring this Node ID to a
value different than zero. This is the additional CAN ID for the PLC.
2nd Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
EN
CL2 {0} {1} {2} In a multi-master application, each Master needs its own identifier (Node ID) from
9022 the unit. In order 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 unit.
3rd Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
EN
CL2 {0} {1} {2} In a multi-master application, each Master needs its own identifier (Node ID) from
9024 the unit. In order to send remote signals (i.e. acknowledge) to the unit. 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.
3rd Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
EN
CL2 {0} {1} {2} In a multi-master application, each Master needs its own identifier (Node ID) from
9026 the unit. In order 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 unit.
4th Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
EN
CL2 {0} {1} {2} In a multi-master application, each Master needs its own identifier (Node ID) from
9028 the unit. In order to send remote signals (i.e. acknowledge) to the unit. 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.
4th Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
EN
CL2 {0} {1} {2} In a multi-master application, each Master needs its own identifier (Node ID) from
9030 the unit. In order 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 unit.
5th Client->Server COB-ID (rx) CAN bus: Client->Server COB-ID (rx) 1 to FFFFFFFF
EN
CL2 {0} {1} {2} In a multi-master application, each Master needs its own identifier (Node ID) from
9032 the unit. In order to send remote signals (i.e. acknowledge) to the unit. 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.
5th Server->Client COB-ID (tx) CAN bus: Server-> Client COB-ID (tx) 1 to FFFFFFFF
EN
CL2 {0} {1} {2} In a multi-master application, each Master needs its own identifier (Node ID) from
9034 the unit. In order 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 unit.
NOTE
The COB IDs must be entered in decimal numbers in LeoPC 1 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
EN
COB-ID Receive PDO 1/2 - COB-ID 1 to FFFFFFFF
COB-ID
DE
CL2 {0} {1} {2} This parameter contains the communication parameters for the PDOs, the device is
9300 able to receive.
9310
Complies with CANopen specification: object 1400 (for RPDO 1 and 1401 for RPDO 2), subindex 1.
The structure of this object is shown in the following tables:
PDO valid / not valid allows to select, 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."2.
Function Function for RPDO 1/2 no func. / 1st IKD /2nd IKD / Bk 16DIDO / Co 16DIDO
EN
Funktion
DE
CL2 {0} {1} {2} The unit provides pre-configured CAN bus settings for the connection of different
9050 units. The unit to be connected must be selected here.
9051
No func. ........No external unit is selected for connection. The CAN bus is disabled.
Values are not sent or received.
1st IKD ..........The unit is pre-configured for the connection of a Woodward IKD 1
expansion board.
2nd IKD .........The unit is pre-configured for the connection of a second Woodward
IKD 1 expansion board.
BK 16 DIDO The unit is pre-configured for the connection of a Phoenix Contact
BK 16 DIDO expansion board.
Co 16 DIDO .The unit is pre-configured for the connection of a Phoenix Contact
Co 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.".
CL2 {0} {1} {2} Node-ID of the attached device. The SDO messages were sent on the standard
9060 SDO-IDs or the answers were expected.
9061
EN
RPDO-COP-ID ext. Gerät {x}
DE
CL2 {0} {1} {2} Value to be written in the object 1800h sub index 1h of the external device.
9070
9072
CAUTION
COB-IDs already used in other PDOs should be used.
COB-IDs in a CANopen device after loading the standard values:
280h + Node-ID = 640 + Node-ID Object 1801h Subindex 1
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
DE
CL2 {0} {1} {2} This parameter contains the communication parameters for the PDOs the unit is
9600 able to transmit. The unit transmits data (i.e. visualization data) on the CAN ID
9610
9620 configured here.
9630
Complies with CANopen specification: object 1800 for (TPDO 1, 1801 for TPDO 2, 1802 for TPDO 3,
and 1803 for TPDO 4), subindex 1. The structure of this object is shown in the following tables:
PDO valid / not valid allows to select, which PDOs are used in the operational state.
EN
Transmission type CAN bus 1: Transmit PDO 1 - Transmission type 0 to 255
Transmission type
DE
CL2 {0} {1} {2} This parameter contains the communication parameters for the PDOs the unit is
9602 able to transmit. It defines whether the unit broadcasts all data automatically (value
9612
9622 254 or 255) or only upon request with the configured address of the COB ID SYNC
9632
message (parameter 9100).
Complies with CANopen specification: object 1800 (for TPDO 1, 1801 for TPDO 2, 1802 for TPDO 3,
and 1803 for TPDO 4), subindex 2. The description of the transmission type is shown in the following
table:
A value between 1 and 240 means that the PDO is transferred synchronously and cyclically. The
transmission type indicating the number of SYNC, which are 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
DE
CL2 {0} {1} {2} This parameter contains the communication parameters for the PDOs the unit is
9604 able to transmit. The broadcast cycle for the transmitted data is configured here.
9614
9624 The time configured here will be rounded up to the next 5 ms step.
9634
Complies with CANopen specification: object 1800 (for TPDO 1, 1801 for TPDO 2, 1802 for TPDO 3,
and 1803 for TPDO 4), subindex 5
Number of Mapped Objects CAN bus 1: Transmit PDO 1 - Number of mapped objects 0 to 4
EN
CL2 {0} {1} {2} This parameter contains the mapping for the PDOs the unit is able to transmit. This
9609 number is also the number of the application variables, which shall be transmitted
9619
9629 with the corresponding PDO.
9639
Complies with CANopen specification: object 1A00 (for TPDO 1, 1A01 for TPDO 2, 1A02 for TPDO 3,
and 1A03 for TPDO 4), subindex 0
1. Mapped Objekt
DE
CL2 {0} {1} {2} This parameter contains the information about the mapped application variables.
9605 These entries describe the PDO contents by their index. The sub-index is always 1.
9615
9625 The length is determined automatically.
9635
Complies with CANopen specification: object 1A00 (for TPDO 1, 1A01 for TPDO 2, 1A02 for TPDO 3,
and 1A03 for TPDO 4), subindex 1
2. Mapped Objekt
DE
CL2 {0} {1} {2} This parameter contains the information about the mapped application variables.
9606 These entries describe the PDO contents by their index. The sub-index is always 1.
9616
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
EN
3. Mapped Objekt
DE
CL2 {0} {1} {2} This parameter contains the information about the mapped application variables.
9607 These entries describe the PDO contents by their index. The sub-index is always 1.
9617
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
4. Mapped Objekt
DE
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 to send 8 byte of data with each Transmit PDO. These may be defined separately if no
pre-defined data protocol is used.
All data protocol parameters with a parameter ID may be sent as an object with a CANopen Transmit
PDO.
In this case, the data length will be taken from the data byte column (refer to the Data Protocols section
in the Interface Manual 37389):
• 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 LeoPC 1.
Baudrate Serial interface: Baud rate 2.4 / 4.8 / 9.6 / 14.4 / 19.2 / 38.4 / 65 / 115 kBaud
EN
Baudrate
DE
CL2 {0} {1} {2} A DPC (P/N 5417-557) must be used for connecting the control unit
3163 from the service interface to a PC or to another participant.
The serial interface of this unit connects to an RJ45-plug on the side of the
housing. This parameter defines the baud rate that communications will be
performed. Please note, that all participants on the service interface must use the
same Baud rate.
Parity
DE
CL2 {0} {1} {2} The used parity of the service interface is set here.
3161
Stop Bits
DE
CL2 {0} {1} {2} The number of stop bits is set here.
3162
Baudrate Serial interface 2: Baud rate 2.4 / 4.8 / 9.6 / 14.4 / 19.2 / 38.4 / 56 / 115 kBaud
EN
Baudrate
DE
CL2 {0} {1} {2} This parameter defines the baud rate for communications. Please note, that all
3170 participants on the service interface must use the same baud rate.
Parity
DE
CL2 {0} {1} {2} The used parity of the service interface is set here.
3171
Stop Bits
DE
CL2 {0} {1} {2} The number of stop bits is set here.
3172
ModBus Slave ID
DE
CL2 {0} {1} {2} The Modbus device address is entered here, which is used to identify the device
3185 via Modbus. If 0 is entered here, the Modbus Slave module is disabled.
Modbus Reply delay time Serial interface: Reply delay time 0.00 to 0.20 s
EN
Antwort This is the minimum delay time between a request from the Modbus master and
CL2 {0} {1} {2}
the sent response of the slave. This time is also required if an external interface
3186
converter to RS-485 is used for example. Please note that you also need the
DPC (refer to page 10) in this case.
System
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
System: Configure Display Backlight
CL2 {0} {1} {2} This parameter determines the behavior of the display backlight. The following
4556 options are available:
CL2 {0} {1} {2} This parameter is only visible if parameter 4556 has been configured to
4557 "Key actv.".
If no softkey has been pressed for the time configured here, the display backlight
will be disabled.
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-15 to enable an automatic change to
daylight saving time and back to standard time.
ID Parameter Setting
4591 Daylight saving time ON
4593 DST begin month 3
4592 DST begin Sunday 2
4594 DST begin time 2
4596 DST end month 11
4595 DST end Sunday 1
4597 DST end time 2
Table 3-15: Daylight saving time - configuration example
Sommer-Winterzeit Erkennung
DE
CL2 {0} {1} {2} This parameter enables or disables daylight saving time.
4591
ON ............... Daylight saving time is performed according to the following
parameters.
OFF ............. Daylight saving time is disabled.
CL2 {0} {1} {2} Daylight saving time starts in the month configured here.
4593
CL2 {0} {1} {2} Daylight saving time starts on the Sunday configured here of the month configured
4592 in parameter 4593.
CL2 {0} {1} {2} Daylight saving time starts at this time on the Sunday configured in
4594 parameter 4592.
CL2 {0} {1} {2} Daylight saving time ends in the month configured here.
4596
CL2 {0} {1} {2} Daylight saving time ends on the Sunday configured here of the month configured
4595 in parameter 4596.
CL2 {0} {1} {2} Daylight saving time ends at this time on the Sunday configured in
4597 parameter 4595.
Code level display Password system: Code level via display Info
EN
DE
Codeebene Display
CL2 {0} {1} {2} This value displays the code level, which is currently enabled for access via the
10405
front panel display.
Code level CAN port Password system: Code level via CAN-Bus Info
EN
CL2 {0} {1} {2} This value displays the code level, which is currently enabled for access via the
10407 CAN interface.
Code level serial port/DPC Password system: Code level via serial RS-232 (DPC) interface Info
EN
Codeebene RS232/DPC
DE
CL2 {0} {1} {2} This value displays the code level, which is currently enabled for access via RS-
10406 232 serial interface #1.
Supercommissioning level code Password system: Password "Supercommissioning" (CL5) 0000 to 9999
EN
CL5 {0} {1} {2} The password for the code level "Supercommissioning" is defined in this
10411 parameter. Refer to the Password section on page 16 for default values.
Temp. supercomm. Level code Password system: Password "Temporary Supercommissioning" (CL4) 0000 to 9999
EN
CL5 {0} {1} {2} The algorithm for calculating the password for the code level "Temporary
10412 Supercommissioning" is defined in this parameter.
Commissioning level code Password system: Password "Commission" (CL3) 0000 to 9999
EN
CL3 {0} {1} {2} The password for the code level "Commission" is defined in this parameter.
10413 Refer to the Password section on page 16 for default values.
Temp. commissioning level code Password system: Password "Temporary Commission" (CL2) 0000 to 9999
EN
CL3 {0} {1} {2} The algorithm for calculating the password for the code level "Temporary
10414 Commissioning" is defined in this parameter.
Basic level code Password system: Password "Service Level" (CL1) 0000 to 9999
EN
Code Serviceebene
DE
CL1 {0} {1} {2} The password for the code level "Service" is defined in this parameter. Refer to
10415 the Password section on page 16 for default values.
Passwort
DE
CS0 {0} {1} {2} To configure the control via the front panel bus enter the password.
10416
Password CAN Password system: Entry via CAN bus 0000 to 9999
EN
Passwort CAN
DE
CS0 {0} {1} {2} To configure the control via CAN bus enter "password CAN".
10402
CS0 {0} {1} {2} To configure the control via DPC please enter "password DPC".
10401
EN
Factory Settings Factory settings: Factory settings CAN YES / NO
Werkseinstellung
DE
CL2 {0} {1} {2} YES ..............The resetting of the factory settings via CAN bus will be enabled.
1703 NO ................The resetting of the factory settings via CAN bus will not be enabled.
Werkseinstellung DPC/RS232
DE
L {0} {1} {2} YES ..............The resetting of the factory settings via DPC/RS-232 will be enabled.
1704 NO ................The resetting of the factory settings via DPC/RS-232 will not be
enabled.
Werkseinstellung CAN
DE
L {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
DE
CL2 {0} {1} {2} YES ..............The default values, which have been enabled with parameter 1703,
1701 1704 or parameter 1705, will be loaded by the unit.
NO ................The factory settings will not be loaded by the unit.
Bootloader starten
DE
CL3 {0} {1} {2} This function may be used to start the Bootloader. In order to do this, the correct
10500 code must be entered here while the unit is in the code level required for this.
CAUTION
The Start Bootloader function is used to flash the software and may only be used by authorized
Woodward technicians!
NOTE
If the DTSC-200 parameters are read out via CAN / DPC and stored as standard values, all parameters
behind parameter 1701 (Set default values) will not be overwritten when writing back the standard
value file via CAN / DPC.
This prevents an unintentional start of the Bootloader or an overwriting of the time or date in the unit
with a wrong (old) value. The following version information is only for info anyway and cannot be
overwritten.
Stunden
DE
CL2 {0} {1} {2} The current hour of the clock time is set here. Example:
1762 0.................... 0th hour of the day.
23.................. 23th hour of the day.
Minuten
DE
CL2 {0} {1} {2} The current minute of the clock time is set here. Example:
1761 0.................... 0th minute of the hour.
59.................. 59th minute of the hour.
Sekunden
DE
CL2 {0} {1} {2} The current second of the clock time is set here. Example:
1760 0.................... 0th second of the minute.
59.................. 59th second of the minute.
Tag
DE
CL2 {0} {1} {2} The current day of the date is set here. Example:
1763 1.................... 1st day of the month.
31.................. 31st day of the month.
Monat
DE
CL2 {0} {1} {2} The current month of the date is set here. Example:
1764 1.................... 1st month of the year.
12.................. 12th month of the year.
Jahr
DE
CL2 {0} {1} {2} The current year of the date is set here. Example:
1765 0.................... Year 2000.
99.................. Year 2099.
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 37385.
Seriennummer
DE
{0} {1} {2} The serial number (S/N) is utilized to identify individual control units. The number
900 can also be found on the data plate (items #1 & #3).
Boot item number Version: Part number of the firmware (P/N) info
EN
Boot Artikelnummer
DE
{0} {1} {2} The part number (P/N) is the firmware in the control unit.
950
Boot revision Version: Revision of the item number of the firmware (REV) info
EN
Boot Revision
DE
{0} {1} {2} The revision number (REV) is the revision of the control unit firmware.
960
Boot Version
DE
{0} {1} {2} This number (Vx.xxxx) represents the version of the control unit firmware.
965
Program item number Version: Item number of the application software (P/N) info
EN
Programm Artikelnummer
DE
{0} {1} {2} The part number (P/N) is the application software running the control unit.
930
Program revision Version: Revision of the item number of the software (REV) info
EN
Programm Revision
DE
{0} {1} {2} The revision number (REV) is the revision of the application software running the
940 control unit.
Programm Version
DE
{0} {1} {2} This number (Vx.xxxx) represents the version of the application software running
945 the control unit.
Appendix A.
LogicsManager
The LogicsManager is used to customize the sequence of events in the control unit such as the start command of
the engine or the operation of control unit relay outputs. For example, the start routine may be programmed so
that it requires the closing of a discrete input or a preset time of day. Two independent time delays are provided
for the configured action to take place and be reset. The following table shows the function of each relay in each
of the application modes.
Starting the engine can be carried out externally via a discrete input. With it the LogicsManager is used whose
conditions and programming is defined as follows.
Table 3-11 on page 80 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 106 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 AND
Logical AND
passed 1:1.
NAND
NOT VALUE {[Cx]} Logical negated AND
The opposite of the
The description and the tables of value [Cx] is passed. OR The description and the tables of
all values, flags, and internal Logical OR all logical outputs, flags, and
functions that are able to functions that are able to
0 [always "0"]
combine via the LogicsManager NOR combine via the LogicsManager
The value [Cx] is ignored and
can be found in the Logical Logical negated OR can be found in the Logical
this logic path
Command Variables section Outputs section starting on
will always be FALSE.
starting on page 106. XOR page 104.
Exclusive OR
1 [always "1"]
The value [Cx] is ignored and NXOR
this logic path Exclusive negated OR
will always be TRUE.
(See Table 3-17 for symbols)
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] )
Figure 3-30: LogicsManager - display in LeoPC Figure 3-31: LogicsManager - display in LCD
Logical Symbols
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
The following symbols are used for the graphical programming of the LogicsManager.
1
1
1
1
1
1
1
1
1 1 1 1
1
1
1
1
1 1
1 1
1
1 1 1
1
1
1
1
1
1
1
1
1
1
1
1
1
1 1 1 1
1
1
1
1
1 1
1 1
1
1 1 1
1
1
1
1
1 1
1
1
1
1
1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
DIN 40 700
LeoPC1
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 29)
{0} If TRUE, the unit is blocked against
{1} automatic transfers.
{2}
TRUE, if DI 5 is NOT energized
dependent
on DI 5
Prepared for: -
Deactivated by default FALSE
Gen-Gen enable
(parameter 12830 on page 32)
{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 36)
{0} If TRUE, source 1 is preferred.
{1}
{2} Prepared for: -
Activated by default
TRUE
Source 2 priority
(parameter 12810 on page 36)
{0} If TRUE, source 2 is preferred.
{1}
{2} Prepared for: -
Deactivated by default
FALSE
Load shed
(parameter 12870 on page 40)
{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 50)
{0} If TRUE, a load test will be
{1} performed.
{2}
Prepared for: -
Deactivated by default
FALSE
No load test
(parameter 12650 on page 50)
{0} If TRUE, a no-load test will be
{1} performed.
{2}
Prepared for: -
Deactivated by default
FALSE
External acknowledge
(parameter 12490 on page 51)
{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 81)
{0} If TRUE, relay 5 will be energized.
{1}
{2} True, if the Source 2 start signal is
issued dependent
on Logics
Command
Variable
[20.06]
Relay 6 [R06]
(parameter 12140 on page 81)
{0} If TRUE, relay 6 will be energized.
{1}
{2} True, if the command: Close to
Source 1 is issued dependent
on Logics
Command
Variable
[20.07]
Relay 7 [R07]
(parameter 12150 on page 81)
{0} If TRUE, relay 7 will be energized.
{1}
{2} True, if the command: Close to
Source 2 is issued dependent
on Logics
Command
Variable
[20.09]
Relay 8 [R08]
(parameter 12160 on page 81)
{0} If TRUE, relay 8 will be energized.
{1}
{2} True, if the command: Open from
Source 1 is issued dependent
on Logics
Command
Variable
[20.08]
Relay 9 [R09]
(parameter 12170 on page 81)
{0} If TRUE, relay 9 will be energized.
{1}
{2} True, if the command: Open from
Source 2 is issued dependent
on Logics
Command
Variable
[20.10]
External digital output {x] [REx{x}] - free (external expansion card, if connected; {x} = 1-16)
(refer to Table 3-13 on page 81 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
Internal flag 8
(parameter 12300 on page 83)
{0} If TRUE, the internal flag 8 will be
{1} enabled.
{2} dependent
TRUE, once the configured time 1 has on Logics
been reached [11.01], and the Command
configured time 2 [11.02] has not Variables
been reached as well, if the current [11.01],
day is the configured day [11.03] [11.02], and
[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.
GetEventLog
The event logger is a 300-entry FIFO (First In/First Out) memory for logging alarm events and operation states of
the unit. Refer to the Event History section on page 17 for more info about the event logger.
It is possible to read out the event logger using the direct configuration cable DPC and the GetEventLog software
tool.
GetEventLog Software
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Installing GetEventLog
GetEventLog can either be used as a stand alone or within LeoPC1. In order to call it up from LeoPC1, it must be
installed into the LeoPC1 installation path.
To install GetEventLog, start GetEventLog_vxxxxx.exe from the GetEventLog directory on the CD delivered
with the unit.
If you want to use GetEventLog from inside LeoPC1, it must be installed into the LeoPC1 installation directory.
Starting GetEventLog
Connect the DTSC to a free COM port on your computer using the DPC as described under Configuration Using
The PC on page 10.
Start GetEventLog directly or call it up by selecting GetEventLog from the menu Tools in LeoPC1.
After starting GetEventLog for the first time, you must configure the communication settings. To do this, select
the Interface tab, configure the COM port according to the port, to which you have connected the DPC, and enter
the other settings as represented in figure Figure 3-32 since these are the default settings of the DTSC.
The 300 latest events are displayed in chronological order and each entry is composed like this:
whereas the "sign" "+" indicates the occurrence and "-" indicates the disappearance or acknowledgement of
the alarm or state
"event date and time" serves as a timestamp and indicates the date and time of the event
occurred
"event no." indicates the event number that occurred
"event text" indicates the event that occurred in clear text
The event text is read out in the language, which is selected in the DTSC, like English or French. Some languages
may not be supported by LeoPC1, like Japanese or Chinese. Then you may change the language in the unit.
The event numbers are indicated in Table 3-18 at the end of this section. Please note that some event texts may be
configured freely (like analog inputs, etc.) and may not correspond with the original text. The event numbers are
unambiguous.
Appendix C.
List Of Parameters
Project ______________________________________________________________________
Par.
Parameter Setting range Default value Customer setting Data type
ID.
MAIN MENU
1700 Language English / Deutsch English UNSIGNED 16
10416 Password 0000 to 9999 --- UNSIGNED 16
EVENT LOG
1706 Clear event log YES / NO NO Y N Y N UNSIGNED 16
MEASUREMENT
1750 Rated system frequency 50/60 Hz 50 Hz UNSIGNED 16
1774 Rated voltage S1 50 to 650000 V 400 V UNSIGNED 32
1772 Rated voltage S2 50 to 650000 V 400 V UNSIGNED 32
3Ph 4W 3Ph4W 3Ph4W
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
1822 Load current transformer 1 to 32000/1 A 500/1 A UNSIGNED 16
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 1 to 300 s 10 s UNSIGNED 16
3330 S2 start delay time 1 to 300 s 10 s UNSIGNED 16
3333 S1 source stable time 1 to 6500 s 10 s UNSIGNED 16
3332 S2 source stable time 1 to 6500 s 10 s UNSIGNED 16
2804 S1 outage delay 0.1 to 10.0 s 1.0 s UNSIGNED 16
2803 S2 outage delay 0.1 to 10.0 s 1.0 s UNSIGNED 16
3343 S1 cooldown time 1 to 6500 s 20 s UNSIGNED 16
3344 S2 cooldown time 1 to 6500 s 20 s UNSIGNED 16
12600 Inhibit ATS see descr. in LogicsManager chap. starting p. 114; default: (!09.05 & 1) & 1 Logman
12610 Inhib. XFR to S1 see descr. in LogicsManager chap. starting page 114; default: (0 & 1) & 1 Logman
12620 Inhib. XFR to S2 see descr. in LogicsManager chap. starting page 114; default: (0 & 1) & 1 Logman
12630 Remote peak shave see descr. in LogicsManager chap. starting page 114; default: (0 & 1) & 1 Logman
12660 Int. pow. rates see descr. in LogicsManager chap. starting page 114; default: (0 & 1) & 1 Logman
12820 Ext. bypass see descr. in LogicsManager chap. starting page 114; default: (0 & 1) & 1 Logman
12830 Gen-Gen enable see descr. in LogicsManager chap. starting page 114; default: (0 & 1) & 1 Logman
Elevator Pre Signal
4490 Elevator Pre signal ON / OFF OFF 1 0 1 0 UNSIGNED 16
4491 Elevator pre-signal duration 1 to 6500 s 5s UNSIGNED 16
Motor Load Disconnect
4550 Motor Load Disconnect ON / OFF OFF 1 0 1 0 UNSIGNED 16
S1->S2 S1->S2 S1->S2
4553 Active direction S2->S1 S1->S2 S2->S1 S2->S1 UNSIGNED 16
Both Both Both
4551 Disconnect time S1->S2 1 to 6500 s 5s UNSIGNED 16
4552 Disconnect time S2->S1 1 to 6500 s 5s UNSIGNED 16
Source Priority
12680 S1 Priority see descr. in LogicsManager chap. starting page 114; default: (1 & 1) & 1 Logman
12810 S2 Priority see descr. in LogicsManager chap. starting page 114; default: (0 & 1) & 1 Logman
12860 Ext. para.time see descr. in LogicsManager chap. starting page 114; default: (0 & 1) & 1 Logman
12870 Load shed see descr. in LogicsManager chap. starting page 114; default: (0 & 1) & 1 Logman
BREAKER
Standard Standard Standard
3424 Transfer switch type Delayed Standard Delayed Delayed UNSIGNED 16
Closet 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 114; default: (0 & 1) & 1 Logman
3426 Neutral time S2->S1 0 to 6500 s 3s UNSIGNED 16
3425 Neutral time S1->S2 0 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 1 to 10 2 UNSIGNED 16
TESTMODES
12640 Load Test see descr. in LogicsManager chap. starting page 114; default: (0 & 1) & 1 Logman
12650 No Load Test see descr. in LogicsManager chap. starting page 114; 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 114; default: (0 & 0)+ 0 Logman
3430 Limit switch monitoring 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 ON 1 0 1 0 UNSIGNED 16
4571 Voltage window 0.50 to 9.99 % 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
4577 Max. overlap time 0.1 to 9.99 s 0.10 s UNSIGNED 16
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
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.
DIGITAL INPUTS
Digital Input 1
N.O.
DI 1 operation N.C. UNSIGNED 16
N.C.
DI 1 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Digital Input 2
N.O.
DI 2 operation N.C. UNSIGNED 16
N.C.
DI 2 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Digital Input 3
N.O.
DI 3 operation N.C. UNSIGNED 16
N.C.
DI 3 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Digital Input 4
N.O.
DI 4 operation N.C. UNSIGNED 16
N.C.
DI 4 delay 0.08 to 650.00 s 0.08 s UNSIGNED 16
Digital 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
Digital 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
Digital 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
Digital 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
Digital 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
Digital 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
Digital 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
Digital 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 Digital 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 Digital 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.
DIGITAL INPUTS
External Digital 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 Digital 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 Digital 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 Digital 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 Digital 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 Digital 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 Digital 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 Digital 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 Digital 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 Digital 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 Digital 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 Digital 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 Digital 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 Digital 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.
DIGITAL OUTPUTS
12100 Relay 1 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12110 Relay 2 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12310 Relay 3 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12320 Relay 4 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12130 Relay 5 see descr. in LogicsManager chap. starting p. 119; default: (!20.06 & 1) & 1 Logman
12140 Relay 6 see descr. in LogicsManager chap. starting page 119; default: (20.07 & 1) & 1 Logman
12150 Relay 7 see descr. in LogicsManager chap. starting page 119; default: (20.09 & 1) & 1 Logman
12160 Relay 8 see descr. in LogicsManager chap. starting page 119; default: (20.08 & 1) & 1 Logman
12170 Relay 9 see descr. in LogicsManager chap. starting page 119; default: (20.10 & 1) & 1 Logman
12330 External DO 1 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12340 External DO 2 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12350 External DO 3 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12360 External DO 4 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12370 External DO 5 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12380 External DO 6 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12390 External DO 7 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12400 External DO 8 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12410 External DO 9 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12420 External DO 10 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12430 External DO 11 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12440 External DO 12 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12450 External DO 13 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12460 External DO 14 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12470 External DO 15 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12480 External DO 16 see descr. in LogicsManager chap. starting page 119; 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
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
LOGICSMANAGER
Internal Flags
12230 Flag 1 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12240 Flag 2 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12250 Flag 3 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12260 Flag 4 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12270 Flag 5 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12280 Flag 6 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12290 Flag 7 see descr. in LogicsManager chap. starting page 119; default: (0 & 1) & 1 Logman
12300 Flag 8 see descr. in LogicsManager ch. start. p. 119; def.: (11.01 & !11.02) & 11.03 Logman
Set Timers
1652 Setpoint 1: Hour 0 to 23 h 8h UNSIGNED 8
1651 Setpoint 1: Minute 0 to 59 min 0 min UNSIGNED 8
1650 Setpoint 1: Second 0 to 59 s 0s UNSIGNED 8
1657 Setpoint 2: Hour 0 to 23 h 17 h UNSIGNED 8
1656 Setpoint 2: Minute 0 to 59 min 0 min UNSIGNED 8
1655 Setpoint 2: Second 0 to 59 s 0s UNSIGNED 8
1663 Active day 1 to 31 1 UNSIGNED 8
1662 Active hour 0 to 23 h 12 h UNSIGNED 8
1661 Active minute 0 to 59 min 0 min UNSIGNED 8
1660 Active second 0 to 59 s 0s UNSIGNED 8
1670 Monday active YES / NO YES Y N Y N UNSIGNED 16
1671 Tuesday active YES / NO YES Y N Y N UNSIGNED 16
1672 Wednesday active YES / NO YES Y N Y N UNSIGNED 16
1673 Thursday active YES / NO YES Y N Y N UNSIGNED 16
1674 Friday active YES / NO YES Y N Y N UNSIGNED 16
1675 Saturday active YES / NO NO Y N Y N UNSIGNED 16
1676 Sunday active YES / NO NO Y N Y N UNSIGNED 16
Par.
Parameter Setting range Default value Customer setting Data type
ID.
COMMUNICATION INTERFACES
1702 Device number 1 to 127 1 UNSIGNED 16
CAN Interfaces
OFF OFF OFF
3155 Protocol CAN Open CAN Open CAN O. CAN O. UNSIGNED 16
LeoPC LeoPC LeoPC
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
9010 Max. answer time ext. devices 0.1 to 9.9 s 3.0 s UNSIGNED 16
9009 Time re-init. ext. devices 0 to 9999 s 10 s 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 2nd IKD no func. 2nd IKD 2nd IKD UNSIGNED 16
BK 16DIDO BK 16 BK 16
Co 16DIDO Co 16 Co 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 2nd IKD no func. 2nd IKD 2nd IKD UNSIGNED 16
BK 16DIDO BK 16 BK 16
Co 16DIDO Co 16 Co 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 1.Mapped Object 0 to 65535 8001 UNSIGNED 16
9606 2.Mapped Object 0 to 65535 8000 UNSIGNED 16
9607 3.Mapped Object 0 to 65535 8000 UNSIGNED 16
9608 4.Mapped 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 1.Mapped Object 0 to 65535 8002 UNSIGNED 16
9616 2.Mapped Object 0 to 65535 8000 UNSIGNED 16
9617 3.Mapped Object 0 to 65535 8000 UNSIGNED 16
9618 4.Mapped 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 UNSIGNED 8
9624 Event-timer 20 to 65000 ms 20 ms UNSIGNED 16
9629 Number of mapped objects 0 to 4 1 UNSIGNED 8
9625 1.Mapped Object 0 to 65535 3196 UNSIGNED 16
9626 2.Mapped Object 0 to 65535 0 UNSIGNED 16
9627 3.Mapped Object 0 to 65535 0 UNSIGNED 16
9628 4.Mapped 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 UNSIGNED 8
9634 Event-timer 20 to 65000 ms 20 ms UNSIGNED 16
9639 Number of mapped objects 0 to 4 1 UNSIGNED 8
9635 1.Mapped Object 0 to 65535 3190 UNSIGNED 16
9636 2.Mapped Object 0 to 65535 0 UNSIGNED 16
9637 3.Mapped Object 0 to 65535 0 UNSIGNED 16
9638 4.Mapped Object 0 to 65535 0 UNSIGNED 16
Serial Interface 1
2400 Bd 2400 Bd 2400 Bd
4800 Bd 4800 Bd 4800 Bd
9600 Bd 9600 Bd 9600 Bd
14.4 kBd 14.4 kBd 14.4 kBd
3163 Baudrate 9600 Bd UNSIGNED 16
19.2 kBd 19.2 kBd 19.2 kBd
38.4 kBd 38.4 kBd 38.4 kBd
56 kBd 56 kBd 56 kBd
115 kBd 115 kBd 115 kBd
No No No
3161 Parity Even No Even Even UNSIGNED 16
Odd Odd Odd
One One One
3162 Stop Bits One UNSIGNED 16
Two Two Two
Serial Interface 2
2400 Bd
4800 Bd 9600 Bd 9600 Bd
9600 Bd 14.4 kBd 14.4 kBd
14.4 kBd 19.2 kBd 19.2 kBd
3170 Baudrate 19200 Bd UNSIGNED 16
19.2 kBd 38.4 kBd 38.4 kBd
38.4 kBd 56 kBd 56 kBd
56 kBd 115 kBd 115 kBd
115 kBd
No No No
3171 Parity Even No Even Even UNSIGNED 16
Odd Odd Odd
One One One
3172 Stop Bits One UNSIGNED 16
Two Two Two
Fullduplex Full Full
3173 Full-, halfduplex mode Fullduplex UNSIGNED 16
Halfduplex Half Half
3185 ModBus Slave ID 0 to 255 1 UNSIGNED 16
3186 Modbus Reply delay time 0.00 to 0.20 s 0.00 s UNSIGNED 16
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
4593 DST begin month 1 to 12 1 UNSIGNED 8
4592 DST begin sunday 1 to 4 1 UNSIGNED 8
4594 DST begin time 1 to 23 h 0h UNSIGNED 8
4596 DST end month 1 to 12 1 UNSIGNED 8
4595 DST end sunday 1 to 4 1 UNSIGNED 8
4597 DST end time 1 to 23 h 0h 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 0000 to 9999 --- UNSIGNED 16
10412 Temp. supercomm. level code 0000 to 9999 --- UNSIGNED 16
10413 Commissioning level code 0000 to 9999 --- UNSIGNED 16
10414 Temp. commissioning level code 0000 to 9999 --- UNSIGNED 16
10415 Basic level code 0000 to 9999 --- UNSIGNED 16
1703 Factory settings YES / NO NO Y N Y N UNSIGNED 16
1704 Factory settings DPC/RS232 YES / NO NO Y N Y N UNSIGNED 16
1705 Factory settings CAN YES / NO NO Y N Y N UNSIGNED 16
1701 Set default values YES / NO NO Y N Y N UNSIGNED 16
10500 Start Bootloader 00000 to 99999 --- UNSIGNED 16
Clock Set
1762 Hour 0 to 23 h --- UNSIGNED 8
1761 Minute 0 to 59 min --- UNSIGNED 8
1760 Second 0 to 59 s --- UNSIGNED 8
1763 Day 1 to 31 --- UNSIGNED 8
1764 Month 1 to 12 --- UNSIGNED 8
1765 Year 0 to 99 --- UNSIGNED 8
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 D.
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-0 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-0 (8.00 - 16.30 German time)
Fax: +49 (0) 711 789 54-100
e-mail: [email protected]
For assistance outside Germany, call one of the following international Woodward facilities to obtain the address
and phone number of the facility nearest your location where you will be able to get information and service.
You can also contact the Woodward Customer Service Department or consult our worldwide directory on
Woodward’s website (www.woodward.com) for the name of your nearest Woodward distributor or service
facility. [For worldwide directory information, go to www.woodward.com/ic/locations.]
Engineering Services
≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡
Woodward Industrial Controls Engineering Services offers the following after-sales support for Woodward
products. For these services, you can contact us by telephone, by e-mail, or through the Woodward website.
• Technical support
• Product training
• Field service during commissioning
Technical Support is available through our many worldwide locations, through our authorized distributors, or
through GE Global Controls Services, depending on the product. This service can assist you with technical
questions or problem solving during normal business hours. Emergency assistance is also available during non-
business hours by phoning our toll-free number and stating the urgency of your problem. For technical
engineering support, please contact us via our toll-free or 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, at your location, or from GE
Global Controls Services, 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 toll-free or 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 our facility in
Colorado, or 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 toll-free or 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 LeoPC1 Additionally you can
save the complete set of parameters (standard values) and send them to our Service department via e-mail.
Woodward GmbH
Handwerkstrasse 29 - 70565 Stuttgart - Germany
Phone +49 (0) 711 789 54-0 • Fax +49 (0) 711 789 54-100
[email protected]
Homepage
http://www.woodward.com/power
2011/06/Stuttgart