DST 4400
DST 4400
DST 4400
technical
handbook
DOCUMENT N° EAAM0105 rev. 04
FILE: EAAM010504I.doc
Date: 21/12/05
This document is owned by SICES s.r.l.. All rights reserved.SICES s.r.l. reserves the right to modify this
document without prior notice
The disclosure by any means of this document to third parties is not allowed
EAAM010504I.doc
Revisions
CONTENTS
REVISIONS ...................................................................................................................................................................... 2
CONTENTS .................................................................................................................................................................. 3
PARAMETERS USAGE INDEX.................................................................................................................................. 6
1. FRONT PANEL ...................................................................................................................................................... 2
1.1 COMMANDS ...................................................................................................................................................... 2
1.1.1 Key-lock selector......................................................................................................................................... 2
1.1.2 Pushbuttons ................................................................................................................................................ 3
1.2 SIGNALS ........................................................................................................................................................... 3
1.2.1 LEDs ........................................................................................................................................................... 3
1.2.2 Multifunctional display ............................................................................................................................... 5
2. PROGRAMMING ................................................................................................................................................ 15
2.1 GENERAL STRUCTURE .................................................................................................................................... 15
2.1.1 Organization ............................................................................................................................................. 15
2.1.2 Protection ................................................................................................................................................. 15
2.2 OPERATING PROCEDURE ................................................................................................................................. 16
2.2.1 Enter in the programming mode............................................................................................................... 16
2.2.2 Menu selection .......................................................................................................................................... 16
2.2.3 Parameters selection................................................................................................................................. 17
2.2.4 Parameters modifying............................................................................................................................... 17
2.2.5 Modifying a string/hexadecimal parameter.............................................................................................. 17
2.2.6 Set up limits............................................................................................................................................... 18
2.2.7 Exit from programming ............................................................................................................................ 18
2.2.8 Loading default values.............................................................................................................................. 18
2.3 ADDITIONAL NOTES ........................................................................................................................................ 18
3. SPECIAL PROCEDURES................................................................................................................................... 19
3.1 ACTIVATION OF SPECIAL PROCEDURES ........................................................................................................... 19
3.2 “LANGUAGE”: LANGUAGE SELECTION ........................................................................................................ 20
3.3 “FUEL LEV.”: FUEL LEVEL SENSOR CALIBRATION. ....................................................................................... 20
3.4 “COUNTERS”: COUNTERS RESET. ................................................................................................................ 22
4. WORKING SEQUENCE ..................................................................................................................................... 23
4.1 BOARD MODES ............................................................................................................................................... 23
4.2 MAINS VOLTAGE ............................................................................................................................................ 24
4.3 GENERATOR ................................................................................................................................................... 26
4.3.1 Frequency ................................................................................................................................................. 26
4.3.2 Generator voltages ................................................................................................................................... 27
4.3.3 Overview ................................................................................................................................................... 28
4.4 INHIBITION ..................................................................................................................................................... 28
4.4.1 Inhibition from digital input ..................................................................................................................... 28
4.4.2 Inhibition by internal clock....................................................................................................................... 29
4.5 ENGINE ........................................................................................................................................................... 29
4.5.1 Engine running/stopped status acknowledgement .................................................................................... 29
4.5.2 Engine commands..................................................................................................................................... 30
4.5.3 Manual control sequence.......................................................................................................................... 32
4.5.4 Automatic command sequence.................................................................................................................. 35
4.6 LOADS CHANGE-OVER .................................................................................................................................... 37
4.6.1 Change-over logic .................................................................................................................................... 38
5. ANOMALIES ........................................................................................................................................................ 41
01 – MINIMUM GENERATOR VOLTAGE .......................................................................................................................... 42
02 – MAXIMUM GENERATOR VOLTAGE ......................................................................................................................... 42
03 – MINIMUM GENERATOR FREQUENCY ...................................................................................................................... 43
04 – MAXIMUM GENERATOR FREQUENCY ..................................................................................................................... 43
05 – BELT BREAK (ENGINE BATTERY CHARGER FAULT) ................................................................................................ 43
1. Front Panel
The front panel contains a multifunction display, nine signal LEDs, a key-lock switch and five
command keys (pushbuttons)
1.1 Commands
1.1.1 Key-lock selector
Key position Function
OFF/RESET Gen-set is disabled. All the alarms are reset. It is possible to gain access to
programming function.
PROGRAM
MAN Gen-set is in manual mode. START key allows cranking the engine; STOP
key allows to stop the engine and KR/KG key allows to LOAD or UNLOAD
the gen-set.
AUTO/TEST Gen-set is in automatic mode. Pressing START button change the mode to
TEST, STOP button ends the test (if activated) or makes an emergency
shutdown, and KR/KG button allows the load changeover (only in TEST
mode).
1.1.2 Pushbuttons
Button Function
MODE / ACK It is used to acknowledge any kind of alarm and to silence the horn. If there
isn’t any alarm to acknowledge it can be used to select the paged shown on
PROGRAM the display. In program it selects a menu entry or enables/disables the
changing mode of a variable; confirm a new value. Used together with the
ENTER VIEW key it allows to modify the display contrast.
VIEW It is used to scroll the pages shown on the display or to temporarily hide the
anomalies on the second row of the display. It is also used to enter/exit from
EXIT/SHIFT program mode, to exit from menus and to cancel the operation while setting a
parameter value. Used together with the MODE key it allows to modify the
display contrast. When setting a parameter value, used with START or STOP
allows to increase the speed of the increment/decrement
STOP It’ is used to stop the engine, in manual or automatic mode too (if the TEST
mode is enabled, it disable it). In program mode, it is used to scroll down
DEC menus (to the lower submenus and parameters index) and also to decrease
a parameter value during its modify.
KR/KG In manual mode (or in TEST) it allows to changeover the loads from gen-set
and mains (the changeover to mains is always possible, towards the gen-set
it is possible only if the relative measurements are in their tolerance
windows). During the setting of a string-type parameter, it allows to move the
cursor between the string’s characters.
1.2 Signals
1.2.1 LEDs
With the key-lock switch in OFF/RESET, pressing the STOP key will light all the signal LEDs
(LAMP TEST).
• “Mains live”:
o OFF: the mains voltage, on all the phases, is lower than the acknowledgement
threshold
o ON: the voltages, on all the phases, are in their tolerance window consecutively
from the configured watching time
o Flashing (50% on and 50% off): the voltage on at least one phase is higher
than the acknowledgement threshold but not in the tolerance window on all the
three phases from the configured watching time.
o Flashing (25% on and 75% off): the voltage on all the phases of the mains is
lower than the acknowledgment threshold and it is present the inhibit command
by contact or by the internal clock
o Flashing (75% on and 25% off): the voltage on at least one phase is higher
than the acknowledgment threshold and it is present the inhibit command by
contact or by the internal clock.
• “Generator live”:
o OFF: the voltage on all the generator phases and the frequency are lower than
their acknowledgment thresholds
o ON: the genset voltages on all the phases and the frequency are inside their
tolerance windows.
o Flashing: the generator has been recognized to be live (by voltages and/or
frequency) but not all the phases or the frequency are in their operating
windows, or they’re but not from enough time (see the description of genset
working status).
• “Engine running”:
NOTE: if the board is in TEST MODE the loads are normally changed over on mains; in
this phase the KR and KG LEDs flash 50% on and 50% off, to signal the TEST. Manual
changeover is possible, but in this case there isn’t the load status indication.
• “MODE 1”:
o ON: the multifunctional display is showing the principal page (voltages, currents,
frequency, oil pressure, coolant temperature, engine speed and the engine
status in the cranking/stopping phases.
• “MODE 2 / WARNING”:
This LED is used in two ways: to show that the display is showing one page of the
MODE 2 modality and/or at least one warning is pending. The following table shows all
the possible MODE 2 LED command ways and, for each, states if the MODE 2 modality
is active and if a warning is pending.
OFF No No
ON Yes No
• “MODE3 / ALARM”:
This LED is used in two ways: to show that the display is showing one page of the
MODE 3 modality and/or at least one alarm (block) o a deactivation is pending. The
following table shows all the possible MODE 3 LED command ways and, for each,
states if the MODE 3 modality is active and if a block or a deactivation is pending.
OFF No No
ON Yes No
• “MODE4 / DIAGNOSTIC”:
This LED is used in two ways: to show that the display is visualizing one page of the
MODE 4 modality and/or it is present at least a diagnostic code (typically acquired from
the engine by CanBus). The following table shows all the possible MODE 4 LED
command ways and, for each, states if the MODE 4 modality is active and at least a
diagnostic code is present.
OFF No No
ON Yes No
The internal backlight lamp is managed by the internal logic and is switched off (with engine
at rest) if P.492 time is elapsed before any key is pressed. To light on again the lamp, press
any keys (NOTE: if to light on again MODE or VIEW keys are used, they must be pressed
again to execute their normal associated function). It is possible to disable the automatic
lamp turn-off by setting to zero the parameter P.492. During the crank phase, the backlight is
temporarily switched off to increase the board immunity to heavy voltage drop of poor
charged battery; from release 00.03, with the engine running the lamp is always switched on.
To leave the lamp always on, also with the engine stopped, set P.492=0. The default value
of P.492 is 999 seconds.
The contrast ratio can be changed by pressing at the same time the keys MODE and VIEW.
Press and keep pressed first the MODE key and then VIEW to increase the contrast ratio.
Press and keep pressed first the VIEW key and then MODE to decrease the contrast ratio.
While changing the ratio, on second row it is shown:
CONTRAST: xx
The xx value is the present contrast ratio in percentage. The contrast compensation with the
temperature change is automatically executed. Boards with firmware release 00.03 or earlier
loose this function if updated to a more recent release: to keep this function, also a hardware
update is needed.
The information visualized change with the position of the key-lock switch, as described by
the followings paragraph.
dd/mm/yyyy ff
hh:nn:ss ±tt.t°C
Pressing the MODE/ENTER key allows to visualize the archives. For full details about
archives, see par. 6.17. To exit from the visualization of the archives, press the VIEW/EXIT
key.
Instead, to enter in the programming mode, press the VIEW key. See the related chapter for
the description of the information visualized on the display while in programming mode.
1.2.2.2 key-lock in MAN or AUTO
There are four different display management modes, named MODE1..MODE4 and signalled
each one by the related LED lamp. Use the MODE key to select one mode (in a cyclical
way). In brief, the information visualized in each mode are:
• MODE3: visualization of some counters and, only for board equipped with the CAN
option, engine measurements from CANBUS.
• MODE4: visualization of some counters, all the board status information and
eventual engine diagnostic codes acquired by CANBUS (only for board equipped
with the CAN option).
In MODE2..MODE4 modes the VIEW key is used to cyclically show all the available
information. It is always shown a string identifying the information, besides its numerical
value.
• MODE1
Lx vvv aaaa ff.f
bb.b ±ttt rrrr
If any anomaly is present, it is shown on second row. Anomalies are shown with a string
“* Xnnn-sssssssss”, where “X” identify the typology: “W” for warnings, “D” for
deactivations and “A” (“alarm”) for blocks. “nnn” is the numerical code related to the
anomaly and “sss…” is the description of the anomaly in the selected language. This
string can be longer than 16 characters; in this case the string scrolls on the second row
of the display, stopping itself for a second at the beginning of the rotation (when “X” is on
the first character of the second row). If there are many anomalies at the same time, by
keeping pressed the VIEW key it is forced the visualization of the engine parameter as
seen before.
o Generator window
V 400 400 400
A 125 125 125
There are visualized the three generator phase-to-phase voltages and its currents
• MODE2
In this mode there are available four pages; they are visualized cyclically with the VIEW
key.
o Total powers
T aaaakVA ±p.ppt
±wwwkW ±qqqkvar
T: means that shown values are the system total power measurements
aaaa: apparent power of the total system (kVA)
p.pp: system total power factor (negative in case of power reverse)
t: system total load type: (i) inductive or (c) capacitive
www: system total active power (kW) (negative in case of power reverse)
qqq: system total reactive power (kvar).
If the total active power is greater than 1MW, the free space at the beginning of
the second row is used to expand to four the available digits. In the same way, if
the reactive power is greater 1 Mvar, the separator space between active and
reactive is used to expand to four the available digits (but this is really a very
rare situation).
o Phase powers
f aaaakVA ±p.ppt
±wwwkW ±qqqkvar
f: shows the phase (1,2 or 3) related to the visualized powers. The phase
visualized changes every two seconds.
aaaa: f phase apparent power (KVA).
p.pp: phase f power factor (negative in case of power reverse).
t: type of the load (of the phase f): inductive (i) or capacitive (c).
www: phase f active power (kW) (negative in case of power reverse).
qqq: phase f reactive power (kvar).
If the total active power is greater than 1MW, the free space at the beginning of
the second row is used to expand to four the available digits. In the same way, if
the reactive power is greater 1 Mvar, the separator space between active and
reactive is used to expand to four the available digits (but this is really a very
rare situation). NOTE: this page is not visualized for single-phase generator
(P.101= 1) (phase measurements coincide with those total, visualized with the
previous page).
o Energy counters
kWh: wwwwwwwwwww
kvarh: qqqqqqqqq
Both these counters can be reset by executing the special function described in
par. 3.4
o Mains
MAINS R S T
rrr sss ttt
For single-phase mains (parameter P.119 = 1) the fields “sss” and “ttt” are
replaced with dashes.
• MODE3
In this mode there are available eight pages; they are visualized cyclically with the VIEW
key.
o Counters 1
START NUM:ssssss
FUEL LEVEL lll%
ssssss: engine starts number (resettable with the special function described in
par.3.4).
lll: fuel level in the tank aboard the genset. If this measurement is not
available (parameter P.114= 0), the value is replaced with dashes.
o Counters 2
ENG. HOURS:ppppp
KG HOURS: kkkkk
kkkkk: engine running with load applied hours counter measured by the
board, with KG closed or (if one input was set to do this function) the
KG closing status input active. This counter can be reset with the
special function described in par. 3.4.
o Counters 3
ABS HOURS:aaaaaa
MAINT.HOUR:mmmmm
mmmm: hours remaining to next service (countdown), active only if the service
planning is set (P.424 <> 0), otherwise it will be replaced with dashes.
o Battery voltage
BATTERY: nn.nVdc
It is the battery voltage measured at the board supply inputs (J203 connector).
o CANBUS 1
BOOST P. p.ppBar
INTK. TEMP ±ttt°C
NOTE: this page is shown only if the board is equipped with the CANBUS and it
is enabled (P.700<>0).
o CANBUS 2
OIL TEMP. ±ttt°C
COOL.LEV. lll.l%
ttt: engine oil temperature (ref. SAE-J1939, spn175). If the engine doesn’t
manage this information, it is replaced with dashes.
lll.l: engine coolant level, expressed in percentage in respect to the
maximum level (ref. SAE-J1939, spn111). If the engine doesn’t
manage this information, it is replaced with dashes.
NOTE: this page is shown only if the board is equipped with the CANBUS and it
is enabled (P.700<>0).
o CANBUS 3
TORQ.@SPD.sss.s%
ACT.TORQ ±ttt.t%
sss.s: it’s the percentage ratio between the present torque and the maximum
torque indicated by the engine for the present engine speed (ref. SAE-
J1939, spn92). If the engine doesn’t manage this information, it is
replaced with dashes.
NOTE: this page is shown only if the board is equipped with the CANBUS and it
is enabled (P.700<>0).
NOTE: this page is shown only if the board is equipped with the CANBUS and it
is enabled (P.700<>0).
o CANBUS 4
F.RATE ffff.fL/h
H.TOT. hhhhhhhhh
NOTE: this page is shown only if the board is equipped with the CANBUS and it
is enabled (P.700<>0).
• MODE4
In this mode there are available six pages; they are visualized cyclically with the VIEW
key.
o Status
STATUS INFO:
This page shows some additional information about the system status; on second
row, if some particular commands are active, it appears a string. The available
messages are:
STATUS INFO:
Inhib. from I/O
STATUS INFO:
Inhib. from clock
If it has been configured a time during which the engine must not start
and this time period now is active
STATUS INFO:
Fuel pump On
If one output has been configured as fuel pump output and this output
is active (pump on)
STATUS INFO:
Fuel pump Off
If one output has been configured as fuel pump output but this output
is not active (pump off)
STATUS INFO:
Rem start on
If one input has been configured as remote start input and this input is
active or it is active the remote start command from serial
communication
STATUS INFO:
Rem start on
STATUS INFO:
Rem start xx s
STATUS INFO:
Rem start xx m
STATUS INFO:
C.Over inhibited
If more than one status is active, the second row slides to show all the
messages.
This page shows the diagnostic codes (DTC, Diagnostic Trouble Code) obtained
by CANBUS. It’s active only with CANBUS option installed and configured
(P.700<>0).
NO ACTIVE DTC
This is the message shown if there are no signalling. If there is a code the
window will be as follows:
ssss-ff(oc) ddd
* text
where:
For the diagnostic, the board uses the standard defined with the specification
SAE-J1939 (supported by many engines). The specification states that when an
anomaly in the engine occurs, the engine notifies it showing the object on which
the anomaly has been activated by means of a SPN (example, for a fault of the
oil temperature sensor, the SPN will be 175, identifying the oil temperature).
Moreover the specification states the typology of the fault with a standard code
FMI: as example, a higher than normal value of the measurement of interest (oil
temperature) will be notified with the value 0, where an interruption of the
connection to the sensor will be notified with the code 2 (see the SAE-1939
specifications for the values list).
Engines usually use also unambiguous numerical codes, which simplify the
acknowledgement of the anomaly by the operator (sometimes these codes are
signalled with the flashing of a diagnostic lamp); the board acquires and
visualizes also this code (ddd field). Finally, the board in any case shows an
explicit message for the operator, showing the origin and the typology of the
fault.
o CANBUS status
Can: xxxxxxxx
Er rx: 0 tx: 0
On second row there are the counters of the transmission and reception errors,
managed directly by the can-controller. It is possible to force the exit from the
bus-off status by keeping pressed the VIEW key for five seconds when this
window is visualized (only if the origin of the malfunctioning has been removed).
NOTE: this page is visualized only with the CANBUS option installed and
configured (P.700<>0).
o Board info
BOARD HOUR:xxxxx
BOARD T. ±tt.t°C
o Internal clock
CLOCK . hh:nn:ss
dd/mm/yyyy
hh: hours
nn: minutes
ss: seconds
dd: day of the month
mm: month
yyyy: year
All DST4400 manage an internal real time date/clock. It resets itself when
removing the power supply from the board; as option the board can be provided
with an internal capacitor or battery (even rechargeable), in such a way the time
settings are not subject to reset when the board supply is removed (the clock
stays synchronized for about three days with the capacitor and up to six month
with the battery). NOTE: even with the capacitor or the battery, when not
supplied the board is in off status and the clock is not available, until the supply
is newly given.
NOTE: if the board stays without power supply for enough time (immediately if
without internal capacitor/battery option, or after they are fully discharged) date
and hour will flash to signal that they aren’t acknowledged as valid,
o Serial communication
rrrrr: sssssssss
xxxxxxxxxxxxxxxx
rrrrr: here there is visualized a string, which shows what is the device,
connected to the RS232 port:
2. Programming
The board manages a high number of parameters that allow the manufacturer, the installer
or the final user to configure it in order to adapt it to the specific requirements of the system.
This document does not contain the list of the parameters (even if many of they are
mentioned in the description of the board several functions), but it is referred to the
document "EAAM0102xx, where they’re described in detail. Here is described the
programming general structure and the operating procedure to read and/or modify the
parameters.
• A numerical code, with three digits (it permits the identification independently of the
selected language)
The parameters are grouped in menu, which are organized with a tree structure (a menu can
contain others menu). Mixed menu do not exist: a menu cannot contain both parameters and
others menu.
• A one digit numerical code. In case of secondary menu, the code is composed by
the one of the main menu, followed by a dot and by its own code.
2.1.2 Protection
The access to the programming can be conditioned by means of three various levels of
PASSWORDS, listed in priority order:
1. Manufacturer password
2. Installer password
In this menu there is also the parameter P.000 that works as “login”: it allows to insert a code
in order to gain access to programming. It will enable the modifying of the parameters that
have the protection level associated to the password inserted by means of parameter P.000.
P.000=10: only parameters related to “manufacturer” levels and lower are modifiable
P.000=66: only parameters related to ”installer” levels and lower are modifiable
If in the previous example P.001 was set to zero, to access to all the parameters related to
“manufacturer” level, the “installer” password (66) would be necessary. If also P.002 was set
to zero, to access to all parameters related to “manufacturer” and “installer” levels the “end
user password” (98) would be necessary. If also P.003 were zero, all parameters would be
modifiable, without having to write nothing in P.000.
NOTE: each parameter value is always visible, but the modification is possible only if P.000
contains a password with superior or equal level to that one required by the parameter.
P.001, P.002 and P.002 are exceptions: they aren’t even visualized if P.000 doesn’t contain
a password of level upper or equal than that one requested (in the previous example, if
P.000 contains 66 the menu will show P.002 and P.003 but not P.001).
NOTE: while accessing to programming and setting the password (P.000), it is possible that
parameters P.001, P.002 and P.003 will not be immediately visualized. To enable the
visualization, go back to previous menu and subsequently come back
The access code settings stays memorized for about 10 minutes since the end of
programming. When this time is elapsed the code is automatically reset to zero and must be
reinserted to access again to programming.
In case the password code has been forgotten, only knowing the password with higher level
it is possible recover the access right. In the contrary case (or in the case the manufacturer
password was loosen), it is necessary to send the board in factory in order to unlock the
programming associate functions.
For this reason, it is not advisable do not set up at least the “manufacturer” password
(P.001): if in fact someone else sets up this password or a lower password (even just for
distraction) without communicate it, it will not be possible to modify any parameter. Instead,
knowing the “manufacturer” password, it will be in any case possible to cancel or modify the
other passwords.
.
[1 SYSTEM ]
2 SEQUENCE
Use STOP and START keys to slide the menu respectively towards the items with inferior
and advanced index, in cyclical way (pressing STOP from the first voice it passes to the last
one and vice versa)
Press the MODE/ENTER key to get in the selected sub-menu (that one contained by square
brackets), press the VIEW/EXIT key to get out from menu (returning back to the previous
menu or exiting from programming if already in the main menu).
2.2.3 Parameters selection
When entered in a menu containing parameters, all the display is used to visualize each
parameter. First row shows the numerical code and the string associated to the parameter
(parameter name). Second row shows in its right side the parameter value (enclosed in
square brackets) and can show in its left side the continuation of the parameter name.
Use the STOP key to visualize the previous parameter (of lower index) inside the menu, use
the START key to visualize the next (of higher index). The sliding is cyclical: from last voice it
passes to the last one and vice versa.
Press the MODE key to active the procedure to modify the parameter value (see next
paragraph), press the VIEW key to exit from menu (getting back to previous menu).
2.2.4 Parameters modifying
Once visualized a parameter, to start the modifying it is necessary to press the MODE key.
The board shows an error message (for two seconds) if the request password is not set out.
Otherwise, the square brackets including the value start to flash, indicating that the modify
phase is in progress. To modify the value use the STOP and START keys, to decrease or
increase its value respectively. Each time a key is pressed the value is increased/decreased
of one unit. To increase/decrease the value by ten units at time, before use STOP or
START, press and keep pressed the VIEW key. To confirm the selected new value press
the MODE key; to abort the modification and come back to the initial value press (and
release) the VIEW key.
The procedure here described is valid for the parameters of the first type. They allow the
setting of every number included between its minimum and maximum values (NOTE:
pressing START when at maximum it passes to the minimum and pressing STOP when at
minimum it passes to the maximum).
The procedure is valid also for the second and the third type; for them each pressure of the
STOP or START keys steps to the previous/next listed value.
See next paragraph to modify the parameters of the fourth and fifth type.
2.2.5 Modifying a string/hexadecimal parameter
The actions to begin the procedure and to confirm or abort it are the same as previous
paragraph (MODE and VIEW keys). Once started the procedure of a string or hexadecimal
parameter, a cursor under one of the parameter characters will appear. It shows the actual
character. Use the START and STOP to modify that character: all standard ASCII characters
included between hexadecimal codes 0x21 and 07F are available. They include digits, lower
and upper case letters and the punctuation signs. For hexadecimal parameters, only digits
between 0 to 9 and letters from A to F are available. Press the KR/KG key to make the
cursor jump to the next character; pressing KR/KR at the end of the string makes the cursor
come back to the first char.
If the parameter cannot be fully visualized (because it is longer than 14 characters), arrows
will be shown at the beginning and/or the end of the value itself. As example, the parameter
P.601 uses 16 characters. If the present value is “0123456789ABCDEF”, the display will
show what follows:
601-BITM.1 OUT.1
[0123456789ABC→]
In this example the arrow on the right states that there are some characters not visualized on
that side. Pressing the KR/KG key when the cursor is under the character “C” (in this
example) makes the display become like this:
601-BITM.1 OUT.1
[←23456789ABCD→]
Pressing it again more times, all the right characters will be visible, and the display will be:
601-BITM.1 OUT.1
[←3456789ABCDEF]
• Press the VIEW key n times to go back until main menu appears and then press it
again to exit from programming. Coming a next time into programming, it will be
show main menu.
• Keeping pressed the VIEW key for two consecutive seconds from any position: it
follows the instantaneous exit and the next entry will be exactly in same point.
• Switching the key-lock to AUTO or MAN: next entry will be exactly in same point.
2.2.8 Loading default values
In some situation may be useful to reload parameters factory default values. To do this it is
necessary first at all entering in the programming mode, then keep the keys START and
STOP pressed simultaneously and consecutively for five seconds. A message on the display
will show to the operator the confirmation of defaults reload.
NOTE: the default values will be reloaded only for the parameters for which the access rights
are possessed.
Three fundamental menus describe to the board how the panel (or the plant) is made.
• Menu 1-SYSTEM allows mainly to indicate how the board is connected to the engine
and to the generator: single-phase or three-phases connection (P.101 for generator
voltage, P.119 for mains voltage), the type of C.T. utilized (P.107), the presence and
the type of engine speed sensor (P.110 and P.111), the presence and the type of oil
pressure, coolant temperature and fuel level transducers (P.112, P.113 and P.114),
and last, the presence of D+ signal (P.115). This menu allows moreover to set the
nominal characteristics of the electrical measurements: voltage (P.102 and P.116),
frequency (P105), power (P106.) etc. It is fundamental to set correctly these
parameters because almost all the thresholds for the activation of protections are
made in percentage in respect to them
• The 5-I/O menu allows to inform the board how its configurable inputs and outputs
are used. The menu 5.3 BIT_MAP allows a further configuration of the digital
outputs. NOTE: a wrong configuration of the inputs associated functions can
involve (in the worst case) the activation of false anomalies. The wrong
outputs configuration can instead even make damages. Be careful to the
configuration.
• Only with CAN BUS version: the 6-CAN BUS menu allows to set how the board has
to communicate on the bus to acquire the engine measurements and eventually to
send commands. For this argument see the document EAAM013600 or its later
releases.
3. Special procedures
Besides to the normal working sequence, DST4400 includes special procedures which must
to be activated in a particular way. Some of them are reserved to S.I.C.E.S. s.r.l. and then
are not described in this document. Some other instead can be used also by the installer or
by the end user.
When DST4400 does one of these special procedures, the normal working sequence is not
executed and the genset is not available. It is then appropriate executing these special
procedures in phase of plant installing or start up. If these procedures have to be executed
in a second time, be sure to supply the loads from another source before starting
Here the list of special procedures implemented by DST4400. Those ones in italics and
underlined are reserved to S.I.C.E.S. s.r.l
• “RESERVED”.
The necessary operations to active the special procedures are common for all, and are
described forward. NOTE: all special operations are protected with password. In this
document, the passwords are disclosed only for the procedures available to the operator. It
is not possible to modify these passwords: avoid then to disclose them to operators not
interested to special operations.
1) Disconnect the supply from the board (remove J203 connector or open the fuse in the
panel).
3) Now supply the board, keeping pressed together the START and STOP keys. In this
phase, the multifunctional display shows question marks. The two keys must be kept
pressed until the display will appear as in the following example. NOTE: if the keys are
released too soon, the board will start to work with its normal working sequence and to
activate the special procedure it is needed to restart from step 1.
Special function
Func: [xxxxxxxx]
4) On second row appears in square brackets the name of a special procedure. Release
the START and STOP keys and press MODE: the square brackets start to flash
5) Select the request procedure using START and STOP keys (until its name appears into
the brackets). Then confirm with MODE key. The square brackets stop to flash and the
display appears as this
Special function
Password: [0]
6) In the second row it is now necessary to set a password. This password is different for
each special procedure (see next paragraphs). Press MODE to start the password
setting (brackets start to flash); the password setting follows the same rules of the
parameters values.
7) Use the START and STOP keys to increase or decrease the number into the squares
(NOTE: pressing the VIEW key together to START or STOP makes the numbers
increase or decrease faster).
8) When into the brackets there is the desired number, confirm it by pressing MODE key. If
the password is correct the selected special procedure starts (described later on),
otherwise the board shows an error message and automatically comes back to step 1
NOTE: it is possible to abort this procedure in every moment, by removing the supply from
the board. In each case, at the special procedure end, it is necessary removing and
providing again the supply to the board to come back to the normal working sequence.
2) Select the desired language (in the square brackets) using START and STOP keys.
Now it is possible to remove and give back the supply to the board and work with new
language.
To execute this calibration, follow at first the procedure described in 3.1, using the password
“135” to access the function. The board records in a not-volatile memory the calibration
values. Usually this procedure is executed only one time when configuring the genset
When the procedure described in 3.1 is ended, the display will show
MODE TO BEGIN
Ω: ooo.o %: lll
There are visualized the present value of the sensor resistance and the level computed with
the previous calibration. To calibrate the sensor:
2) On first row it appears the string “MOVE TO MIN LEV.”. Now it must to empty the tank,
or move the float to the level correspondent to the minimum measurable (empty tank).
Wait some seconds, until the measurements on second row are stable, then press the
MODE key.
Now set the numerical value to be associated to the present float position. Typically with
empty tank the value to visualize should be 0%, but it is possible to associate any value
(by example, if manually it is not possible to carry the float completely in the empty
position, it is possible to estimate the current level and set this value). To set the level,
press MODE (square brackets start flashing), use START and STOP keys to change
the value and confirm new value with MODE. NOTE: even if the desired value is “0”,
you must however to set it (by pressing two times the MODE key).
4) On first row it appears the string “MOVE TO MAX LEV.”. The tank must to be filled to its
maximum, or you must to move manually the sensor float up to the level corresponding
to full tank. Wait some seconds, until the measurements shown in the second row are
stable, then press the MODE key.
Now set the numerical value to associate to the present float position. Typically, with full
tank, the value should be 100%, but it is possible to associate any value (if, by example,
manually it is not possible to reach the full tank position with the float, it can be estimate
the level reached and use this value). To set the level, press MODE (square brackets
start flashing), use START and STOP keys to change the value and confirm new value
with MODE. NOTE: even if the desired value is “100”, you have however to set it (by
pressing two times the MODE key).
Now the procedure is complete and it restarts from step 1 allowing its repetition if
needed: on the last row it will be shown the level value recalculated with new
calibration. It is so possible to move the float, verifying the proper level visualization.
When the procedure is at step 1, pressing together for five seconds the START and
MODE keys it is reloaded the default calibration. This calibration is suitable for
“VEGLIA” sensor and corresponds to 360 ohms for empty tank and 10 ohms to full tank
• Active energy.
• Reactive energy.
• Engine starts.
To reset the counters it must first at all to execute the procedure described in par. 3.1, using
the password “274”.
When this procedure is ended, counters are automatically reset and the following window is
shown:
CLEARED
4. Working sequence
4.1 Board modes
DST4400 management permits five modes:
• OFF/RESET: genset is not working (or it is stopping), anomalies are all reset and it
is possible to enter to the programming to modify parameters.
• MAN: genset starting and load changeover to the generator are made by operator
(the board does not manage them automatically). The genset stopping and the load
changeover to mains are normally made by the operator; since protections are
active, the board may in all cases changeover the load to mains if the generator is
not in tolerance and in the same way can stop the engine if an anomaly requiring it
occurs. It is not allowed the access to programming.
• AUTO: the genset starting and stopping and the load changeover are managed by
the board (the operator cannot intervene). All the protections are enabled. It is not
allowed the access to
• TEST: this working mode is almost identical to AUTO mode. It differs by the fact that
the engine is in all the cases started (automatically) also with mains or inhibit
command present and loads are not automatically changed over. However, the
operator can do the changeover manually. The board will pass automatically from
TEST to AUTO if the conditions for an automatic genset intervention are verified. It is
not allowed the access to programming.
• REM (REMOTE START): this working mode is used to force the engine start and
the load changeover to generator (if this operation is not inhibited with an input
configured on this purpose with code 30, see par. 6.16). The purpose is to activate
the genset (typically remotely) without waiting a mains fault. The advantage is that
the board acts as in AUTO mode (so with all the protections enabled) and moreover,
when the need for this function ends, the board is already in AUTO, ready to start
the engine if needed. To use this function the board must be in AUTO mode, and
with a digital input configured as “REMOTE START” (code 27 in par. 507 or
following). The board passes from AUTO to REMOTE START when the input is
activated, comes back to AUTO when deactivated. It is possible to start the engine
also by serial command (and so also with SMS by means of a GSM modem); in this
case code 27 and 30 are not needed. The remote start from serial is possible only if
a digital input has been configured with code “29-remote start enable” and this input
is active; if not, the serial start command will be ignored. The engine will run until a
serial stop command will be received.
First three modes are selected with the key-lock switch on the board front panel. To activate
TEST mode, instead, board must be in AUTO mode and without AUTOMATIC start requests
pending (see the description of the engine working sequence late on). The contemporary
flashing of KR and KG LEDs in the board front panel indicates TEST mode (NOTE: in TEST
mode loads are normally supplied by mains, there is no need for the changeover status
signalling). It is possible to pass in TEST mode in the following ways
o Press START button in the board front panel. The passage to TEST mode is
immediately. Press STOP button to return in AUTO mode.
o Set properly parameters P.418, P419 and P420 (PERIODICAL TEST). They permit
to program weekly time slots during which the engine has to run in TEST mode (to
maintain it efficient). First parameter allows to specify in which days of the week the
TEST will be executed, the second is the test starting hour and the third the test
length. In this case, the passage to TEST is automatic in the scheduled days and
hour. The board comes back to AUTO mode at the end of the configured TEST time
interval. NOTE: if these parameters are configured but the clock is not valid (it was
not set) the board actives a warning.
o Through an adequate SMS command message (see the document describing the
use of RS232 port). To utilize this possibility it is necessary that parameter P420 is
different from zero (it is the TEST duration). In this case the board passes to TEST
mode as soon as received the SMS message and comes back to AUTO mode after
the time P.420.
o It is possible to configure one digital input with the REMOTE TEST function (code 26
in P.507 or following). The board will pass to TEST if this input is activated and it will
come back to AUTO if deactivated.
Mains must be connected to J207 connector. For a three-phase system, the three phase
lines (neutral line is not utilized) must be connected, for a single-phase system it must to
connect the only phase line to J207 PIN 3 (“R”) input and neutral line to J207 PIN 2 (“S”)
input.
• P.116: nominal mains voltage. Its value must be the nominal phase-to-phase voltage
for three-phase system and phase–to–neutral voltage for single-phase systems.
Thresholds are expressed in percentage respect to P116; if it is set to zero, mains
voltage is always considered not present, even if physically connected. NOTE: even
if P116 is set to zero, mains voltage value is always computed and visualized
• P.203: low mains voltage threshold (percentage respect to P.116); under this value
mains is considered anomalous and the engine is started.
• P.204: high mains voltage threshold (percentage respect to P.116); over this value
mains is considered anomalous and the engine is started.
Let us see a practical example upon how thresholds work, with default values for the
parameters we have seen. Let us consider a nominal mains value (P.116) of 400V.
Therefore, the minimum mains voltage related to default value for P.203 (80%) is 320V. The
maximum mains voltage related to default value for P.204 (110%) is 440V. With P.201 set to
2.5 (default), the hysteresis is 10 volts (2.5% of P116). With these values, we can identify the
following bands:
0 V .
A band: absent
70 (80-10) V .
B band: hysteresis
80 V .
C band: low
320 V .
D band: hysteresis
330 (320+10) V .
E band : in tolerance
430 (440-10) V .
F band: hysteresis
440 V .
G band: high
xxx V .
An 80 volts fixed threshold (not configurable) is used to define when mains is considered
present ob absent, with a fixed hysteresis 10 volt downward. Practically, mains voltage is
present if over 80 volts, absent if under 70 volts; the previous status is maintained if between
the two thresholds. Moreover, for the two configurable thresholds (320V and 440V), the
hysteresis is fully applied in the direction of threshold entry. This means that mains voltage is
out of tolerance if external to P.203 and P.204 thresholds, it is in tolerance if internal to
P.203 + hysteresis and P.204 – hysteresis thresholds, otherwise it maintains the previous
status
If the mains voltages are in the “B”, “D”, “F” bands, board maintains its previous status
(hysteresis). For example, if mains was in “E” band and now is in “D” band, it is considered
in any case “in tolerance”. If instead mains was in “C” band and now is in “D” band, it is
considered “low”.
Such statuses are managed for each phase. With a three-phase system, in order to
diagnose the mains “global” status, the following algorithms are utilized, shown in their
computing order:
• If all the three phases are in “Absent” status, also global status is “Absent”.
• If all the three phases are in “In tolerance” status, also global status is “In tolerance”.
For automatic genset management purpose, the mains behaviour can be described in three
steps:
a) Steady out of tolerance: the mains global status was different from “In tolerance”
consecutively at least for the time configured in P.206, if the generator is in tolerance,
otherwise for two seconds. If the key switch is in AUTO and P.116 is different from
zero, the board provides to start the engine and to changeover the loads to genset.
The LED “MAINS LIVE” is switched off if mains is “Absent”, otherwise it flashes. (See
also the notes about inhibition command for this LED management).
b) Steady present: the mains global status was “In tolerance” consecutively for the
time set by P.205 (if the key switch is in AUTO, otherwise immediately). If the key is in
AUTO and P.116 is different from zero, the board provides to change over the load to
mains and to stop the engine (with cooling cycle). “MAINS LIVE” LED is switched on.
c) Transitory: between the passage from “a” phase to “b” phase” or vice-versa. The
LED “MAINS LIVE” flashes. (See also the notes about inhibition command for this
LED management).
On the frontal panel only the phases “a”, “b”, and “c” are visualized by means of the “MAINS
LIVE” LED. In no way the status “Absent” etc., whether global or for the single phases are
shown; they are however readable with ModBus protocol from serial port
4.3 Generator
DST4400 measures generator (single or three-phase) voltage and frequency in order to
protect the loads and the generator itself from malfunctioning outside its tolerance
thresholds.
Generator voltages must to be connected to J206 connector. For a three-phase system, you
must connect the three phase lines to their respective inputs; for a single-phase system, the
phase line must be connected to “L1” input (PIN 3) and the neutral line to “N” (PIN 2). The
frequency measure is carried out only on the phase connected to L1 input (PIN 3).
4.3.1 Frequency
Many parameters have effects on frequency measurements:
• P.228: threshold (absolute in Hz) under which the generator is considered stopped.
• P.229: threshold (absolute in Hz) over which the generator is considered working.
• P.307: high frequency threshold (percentage in respect to P.105); over this threshold
the generator cannot be loaded.
Let us see a practical example about thresholds, with default values for the parameters. We
consider a nominal genset frequency (P.105) of 50 Hz. So the threshold set by P.305 (it has
default of 90) is 45 Hz. The threshold related to P.307 default value (110) is therefore 55 Hz.
The threshold related to P.331 (default 120 %) is 60 Hz. Default values for P.228 and P.229
are zero (to disable the acknowledgment of engine running detection by the alternator
frequency measurements). For completeness, in this example, however, we consider that
the engine running threshold is 10 Hz (P.228) and the engine-stopped threshold (P.229) is 5
Hz. With these values, we can identify the following bands:
0 Hz .
A band: Absent
5 Hz .
B band: hysteresis
10 Hz .
C band: low
45 Hz .
D band: in tolerance
55 Hz .
E band: high
60 Hz .
F band: overspeed
xxx Hz .
The only managed hysteresis band is to diagnose the status for engine spotted or engine
running. From generator’s viewpoint, the “E” and “F” bands are the same; they are
separated only to implement an over speed protection for the engine in the case his speed
cannot be detected in other ways (pick-up, “W” signal, etc.).
P.305, P.307 and P.331 thresholds are utilized also to manage the engine/generator
frequency protections. These protections can be individually disabled setting to zero the
parameter specifying the delay (respectively P.306, P.308, P.332). However, if protections
are disabled, thresholds are utilized to determine the frequency status; this allows to not
DST4400 TECHNICAL HANDBOOK - 21/12/05 - pag. 26
EAAM010504I.doc
changeover the loads on generator if its electrical measurements are not in the tolerance
band (useful for asynchronous engines).
• P.227: threshold (absolute in volts) over which the generator is considered working
• P.301: low generator voltage threshold (percentage respect to P.102); under this
value loads cannot be changed-over to genset
• P.303: high generator voltage threshold (percentage respect to P.102); over this
value loads cannot be changed-over to genset
Let us see a practical example upon how thresholds work, with default values for the
parameters. Let us consider a nominal generator value (P.102) of 400V. Therefore, the
minimum generator voltage related to default value for P.301 (75%) is 300V. The maximum
mains voltage related to default value for P.303 (112.5%) is 450V. With P.202 set to 2.5
(default), the hysteresis is 10 volts (2.5% of P102). Default values for P.226 and P.227 are
respectively 70 and 80 volts. With these values, we can identify the following bands:
0 V .
A band: Absent
70 V .
B band: Hysteresis
80 V .
C band: Low
300 V .
D band: Hysteresis
310 (300+10) V .
E band: In tolerance
440 (450-10) V .
F band: Hysteresis
450 V .
G band: High
xxx V .
To the two configurable thresholds (300 and 400V) is applied hysteresis fully in the direction
for the threshold entry. This means that generator voltage is out of the tolerance if external to
the thresholds P.301 and P.303, it is in tolerance if between P.301 + hysteresis and P.303 –
hysteresis, otherwise the previous status is maintained.
If the voltage is in the “B”,”D” or ”F” previous status is maintained (hysteresis). For example,
if the voltage was in “E” band and now it is in “D” band, it is considered however “In
tolerance”. If instead voltage was in “C” band and now is in “D” band, it is considered “Low”.
Such statuses are managed for each phase. With a three-phase system, in order to
diagnose the generator “global” status, the following algorithms are utilized, shown in the
order they are computed:
• If all the three phases are in “Absent” status, also global status is “Absent”.
• If all the three phases are in “In tolerance” status, also global status is “In tolerance”.
P.301 and P.303 thresholds are utilized also to manage the generator protections on
voltages. These protections can be singularly disabled setting to zero their related parameter
specifying the delay (respectively P.302 and P.304). Thresholds are however utilized in
order to identify the voltage status: this allows to non-changeover the load to genset if its
electrical measurements are not in the tolerance band, also if protections are disabled (this
is useful for asynchronous engines).
4.3.3 Overview
To the general management, the generator behaviour can be described in three phases:
a) Steady out of tolerance: the generator voltages and/or frequency status was
different from “In tolerance” consecutively for two seconds. The LED “GENERATOR
LIVE” is switched off if voltages and frequency are in “Absent” status, otherwise it
flashes.
b) Steady present: the generator voltages and frequency status must be “In
tolerance” consecutively for 0.5 seconds “GENERATOR LIVE” LED is switched on.
c) Transitory: between the passage from “a” phase to “b” phase” or vice-versa. The
LED “GENERATOR LIVE” flashes.
On the frontal panel only the phases “a”, “b”, and “c” are visualized by means of the
“GENERATOR LIVE” LED. In no way the status “Absent” etc., whether global or for the
single phases voltages and frequency are shown; they are however readable with ModBus
protocol from serial port
4.4 Inhibition
In automatic mode, the engine is started/stopped relating to the mains voltage status (AMF
function), in order to allow a correct supply to the loads. Actually, the engine starting for
mains voltage anomalies can be inhibited by at least two sources:
• digital input
The “MAINS VOLTAGE” flashes when there is an active inhibition (75% on and 25% off if
mains status is different from “Absent”, 25% on and 75% off if mains status is “Absent”).
4.4.1 Inhibition from digital input
It is possible to configure one or more digital inputs of the board with the inhibition function
(code 25 in P.507 and equivalents). By default digital input number eight is configured with
this function. If the input is active, the engine is not automatically started when an anomaly
on mains voltage occurs. NOTE: if the internal mains sensor is not used (P.116 set to zero),
mains is always to be considered absent and then the engine in auto mode would always
start. Therefore, this input is the only way to keep stopped the engine. To this input can be
then connected an external mains failure sensor
To manage any kind of external mains sensor there are two parameters to provide the
timings for mains steady present or steady absent. These parameters are P.207 (same as
P.205 for internal sensor) and P.208 (equivalent to P.206).
a) Not active: the input is not consecutively active for the time configured with P.208 (if
the generator is not ready to supply, otherwise for two seconds).
b) Active: the input is consecutively active for the time configure with P.208 (if the key
switch is in AUTO, otherwise immediately).).
c) Transitory: when it passes from “a” status to “b” status or vice versa.
4.4.2 Inhibition by internal clock
With parameters P.421, P.422, P.423 it is possible to define weekly time bands in which the
genset is enabled to work. In particular, by means of P.421 parameter is fixed in what days
of the week the genset can work. By the others it is selected a time band, same for all the
selected days. The time band start (P.422) is referred to the days selected with P.421, and
the time band end (P.423) is referred to the same day if it has value higher than P.422, to
the next day if lower (across midnight). Moreover, setting P.422 equal to P.423, it is defined
a band covering the whole day
NOTE: if these parameters are configured but the clock is not valid (not set up), the board
actives a warning.
4.5 Engine
DST440 is able to start, stop and protect the engine with a series of thresholds upon the
acquired measurements (oil pressure, coolant temperature, speed etc.). Before to describe
the engine management sequences, it is necessary to define in which way the board
determines the engine running status.
4.5.1 Engine running/stopped status acknowledgement
There are six possible ways to determine if the engine is running:
• The engine speed is higher than P.225 threshold. This control is not used if this or
P.224 threshold is set to zero or the measurement is not available (both P.110 and
P.111 parameters set to zero and CAN BUS not used).
• The D+ signal voltage is higher than a fixed threshold. This control is not used if the
measurement is not available (parameter P.115 set to zero).
• If the low/minimum oil pressure inputs are not active. This control is not used if the
parameter P.232 is zero (that is if it explicitly was chosen to not use it) or no digital
input is configured to acquire low and minimum oil pressure signals.
• If the voltage measured on at least one generator phase is higher than P.227
threshold. This control is not used if this or P.226 thresholds are set to zero.
• If the frequency measured on generator is higher than P.229 threshold. This control
is not used if this or P.228 thresholds are set to zero.
To acknowledge the engine running status, to DST4400 it is sufficient that at least one of the
previous conditions is verified consecutively for 0.2 seconds. The board disables the starter
signal (and prevent others activations) if it diagnoses that engine is running
In the same way the conditions to acknowledge the engine-stopped status are:
• The engine speed is lower than P.224 threshold. This control is not used if this or
P.225 threshold are set to zero or if the measurement is not available (both
parameters P.110 and P.111 set to zero and CANBUS not used).
• Signal D+ voltage is lower than a fixed threshold. This control is not used if the
measurement is not available (parameter P.115 set to zero).
• If the low/minimum oil pressure inputs are active. This control is not used if
parameter P.232 is set to zero (that is if it explicitly was chosen to not use it) or if no
digital input is configured to acquire low and minimum oil pressure signals.
• If the voltage measured on all the phases of the generator is lower than P.226
threshold. This control is not used if this or P.227 thresholds are set to zero.
• If the frequency measured on the generator is lower than P.228 threshold. This
control is not used if this or P.229 threshold are set to zero.
The engine is considered stopped if all the previous conditions are verified (all that are not
disabled) consecutively for five seconds.
4.5.2 Engine commands
The board has four relay outputs (max 3A), available on J202 connector (PIN 1 to 5). This
relays, when active, apply on pins 1, 2, 3 and 5 the voltage of pin 4 of J202 connector.
PIN 3 is dedicated to engine starter command (START command). PIN 5 is dedicated to the
fuel solenoid command.
It is possible to configure the two auxiliary outputs (pins 1 and 2) for the following functions:
• PREHEAT: command for the preheater for Diesel engines (code 2 in P.581 or
equivalents). By default no output is configured with this function.
• GAS: command for the gas valve, for gas engines (code 143 in P.581 or
equivalents). By default no output is configured with this function.
In the following descriptions the outputs for the engine commands will be identified as:
The fuel solenoid command (FUEL) is activated always at the engine start request; the
START command comes after a fixed delay of 200ms. The FUEL command stays active
until a stop request arises. The FUEL output usually command, in addition to the fuel
solenoid, all the services and the devices that must stay supplied only if the engine is
running (such as the engine electronic unit, the speed regulator, etc.).
However, with some engines there is a working problem in the fuel solenoid: when the
engine is stopping it is necessary to delay the closing of the fuel solenoid after the engine is
stopped. On the contrary case, the solenoid could become stuck. This problem can appear
only with systems having the stop command given not simply by removing the fuel command
but with other methods (as a CANBUS command, or removing the supply from the engine
electronic unit, or with a separated stop command).
From release 00.04 to avoid this problem it is possible to use the “P.234-fuel solenoid
closure delay from stop command” parameter; it is a delay time settable from 0.0 and 255.0
seconds with a 1/10 second resolution between the instant the engine stop is requested and
the fuel solenoid command is released.
For the engines that can be stopped by removing the supply from their electronic units or
speed governor, it is possible (starting from release 00.04) to configure an output with the
code “25-engine enable command”; this command acts exactly as the fuel command but
without the delay set by P.234. This means that the engine enable output, usable to supply
the engine electronic unit (in case, use an external relay if more current is needed), is
activated (together to the FUEL command) with the start request and will be deactivated with
a stop request (while the FUEL command can be delayed with P.234). This allows to remove
the power supply from the engine electronic unit when the stop request arises, but keeping
the fuel solenoid enabled for the time that the engine takes to stop.
4.5.2.2 Idle speed command (IDLE)
The board manages, by means of a configurable output connected with the engine
electronic unit or with the speed regulator, or directly by CANBUS (if available), the engine
idle speed working mode. This mode is usually utilized to allow the engine to warm up before
loading, but can have other uses.
To use this function, one output must be configured with the code “23-idle speed command”;
if the command has to be given by CANBUS, the board must have the possibility to manage
the engine speed by the bus.
• together with the start request, for the time configured with parameter P.233; it is the
time length of the idle speed command
• together with the start request and until the coolant temperature is under a minimum
threshold, configured with P.223. The P.233 timing has in any case to be configured
(however, if the time P.233 elapses and the temperature is still under P.223, the idle
speed mode ends).
• (from release 00.06) by means the activation of a digital input configured with the
code “35-idle speed request”. This input allows to enter the idle speed mode both in
manual and in AUTO mode also when the engine is already running; if the genset
was supplying, it will be unloaded and then the idle command will be activated.
When the idle speed input will be deactivated, the board disables the idle speed
command and waits that the engine reaches its nominal speed (with the usual P.217
parameter to manage an eventual operating conditions failure) before to change
over the loads on generator.
Preheat
Stopped
Fuel solenoid
Not stopped
Washing (gas)
Cancel
stopping
Start
Running
The manual engine management presents the status showed in the previous diagram. The
rest status are Stopped and Not stopped. For both statuses, the board has deactivated all
the engine commands. The Not stopped status means that some other device has started
the engine or the engine did not stop after a stop cycle (this is possible only with engines
having excitation shutdown system or with defective fuel solenoid). By the board viewpoint,
these two statuses are the same, because the generator and engine protections were never
activated since the board considers that another device started and controls the engine.
4.5.3.1 Manual start
From rest status, pressing the “START” key on the frontal panel, manual start cycle begins.
If the engine was Not stopped, the starter is not activated and the next status is Running. If
the engine was Stopped, the cycle begins whit Preheat (if configured) or with the activation
of the Fuel solenoid
• If the engine running status is diagnosed, next status will be Idle speed (if
configured) or Running.
Preheat status is executed only if parameter P.209 (preheat duration in seconds) is different
from zero and no output is configured for the GAS engine washing (gas valve): in fact the
parameter P.209 is shared with preheat cycle and washing cycle (so they are executed in
alternative). It is not compulsory to set an output as preheat command. When this phase is
ended the engine will be ready to start. In this status the FUEL, ENABLE and PREHEAT are
activated; this is useful if there is a need to introduce a delay between FUEL (and ENABLE)
and START commands (some SOLEINOD may stuck in case a de-pressure is applied
before they have switched).
The status Fuel solenoid is executed in alternative to preheat and is used to introduce a
minimum delay of 0.2 seconds between FUEL (and ENABLE) and START commands. This
is made because some fuel solenoids have a mechanical problem and cannot be opened
while there is a fuel de-pressure. After this status follows the engine start or, if configured,
the washing cycle. In this status, FUEL, ENABLE and IDLE commands are active.
The Washing cycle is useful only for gas engines. It consists in the activation of the starter
keeping closed the GAS valve. In this way a depression is created, which extracts the
residuum gases before the engine start. The cycle is executed if at least one output is
configured as GAS output and the duration time is configured by parameter P.209 (shared
with the preheat cycle). When the configured time is ended, the engine starts cranking. In
this status FUEL, ENABLE, IDLE and START are active
During Start status, FUEL, ENABLE, IDLE, GAS and START are active. This phase lasts
until the acknowledgement of engine running status or until the “START” button is released.
The engine running status is watched continuously (see previous paragraphs) to release as
soon as possible the starter engine. The cycle ends when the “START” button is released or
when the engine starts up (see notes at the beginning).
The Check for running status is entered if the “START” button is released before the board
has acknowledged the engine running. Actually, the given command should be sufficient to
the engine, which should so start regularly. In this status the engine is checked for a
maximum time of 10 seconds, to verify if it is running. IDLE, FUEL, ENABLE and GAS
commands are active (to help the engine to start). If the engine is really running, it follows
the Running status, otherwise at the end of the 10 seconds the board comes back to
Stopped status. Pressing the “START” button in this phase the start procedure is repeated,
bypassing the preheat status (from Fuel solenoid status).
The Idle speed status is executed if the parameter P.233 is different from zero. In this status
the commands FUEL, ENABLE, IDLE and GAS are active. If the board is connected with
CAN BUS to the engine, the idle speed command is managed directly by bus. Otherwise it is
necessary to configure one output to give this command. The cycle ends when the
configured time is over. If the board acquires the coolant temperature (with CANBUS or from
sensor), it is also possible to set a minimum temperature threshold (P.223) to end the cycle:
if the coolant temperature is higher than this threshold for two consecutively seconds, the
idle cycle is ended. Next status is Running.
From Running status (but also from any other status described in the previous paragraph)
the board passes to Stopping status in the following cases:
NOTE: the stopping phase can be executed also with stopped engine.
During the Stopping phase, the FUEL (if the delay P.234 is not configured), ENABLE, GAS,
START and PREHEAT commands are disabled and it is instead activated the STOP
command. The length of this phase is configurable with the parameter P.213 (stop pulse
duration). At the end, the board passes to the Waiting for stopping phase. FUEL command
will stay until the P.234 delay is ended (only with P.234 configured) from the moment of the
stop request.
During Waiting for stopping phase all five engine commands are disabled (only FUEL
command will stay enabled if the delay P.234 is configured) and the board wait for the stop
of the engine. The length of this phase is configurable with parameter P.214 (stop cycle
duration, from which it is subtracted the time configured with P.213). At the end of this
phase, if the engine is not stopped the board passes in the Not stopped phase. If the
engine stops, the board returns to the Stopped status. The entire Waiting for stopping
phase can however be disabled setting parameter P.214 to zero.
If during these last two phases all the stop requests cease and the “START” button is newly
pressed, the board passes to the Cancel stopping status even if the engine has not been
already diagnosed stopped. It is in fact possible to end a stop cycle if the board is in MAN
mode.
The phase Cancel stopping is useful only to allow a little delay between the deactivation of
the eventual “STOP” command and the activation of the FUEL and ENABLE commands.
This delay is of 0.2 seconds, at the end of which the board comes back to the Stopped
status, from which the board will carry on with the engine start being there the conditions
Not stopped
Start
Cancel stopping
Idle speed Delay between
two starts
Wait for
stopping
Start
Confirmation
Stopping
Running
Cooling
The automatic engine management is used with AUTO, TEST and REMOTE START modes.
It does not exist any difference in the sequence between the three modes: differences are in
the protections and load change over management.
In automatic mode, the board manages the engine by means the status shown in the
diagram. Before describe the diagram it is necessary to define when the engine has to be
started or stopped automatically.
The engine is automatically started if there are not alarms or deactivations and if at least one
of these conditions is verified:
• The mains voltage is out of tolerance and it is not active the inhibition to the start,
nor by digital input neither by clock/calendar.
• The TEST mode is activated (see the paragraph describing the board working
modalities).
• The REMOTE START mode is activated (see the paragraph describing the board
working modalities).
a) With normal procedure. This procedure consists of doing an engine cooling cycle
(only if the load was been connected to the generator), keep it running with loads
connected to the mains. This procedure is applied if:
b) With an emergency procedure. This procedure requires the immediate engine stop,
without engine cooling cycle. It is applied if:
To describe the diagram, let us think as starting point the Stopped and Not stopped status.
In both the cases, all the engine commands are disabled. The Not stopped status means
then that engine has been started by some other device or it is not stopped after a stop cycle
(this is possible only with engines having excitation shutdown system or with defective fuel
solenoid). For the board view point the two status are the same, since the protections of the
engine and alternator were never been activated because the board considers that some
other devices is managing the genset. It is possible to exit from this status only if an
automatic start or stop request arises.
4.5.4.1 Automatic start
From the rest status, if a request (see before) arises, the start procedure is activated, doing
the Preheat cycle (if programmed) or activating the FUEL command and subsequently the
START command. If the start request is activated with the engine in a Not stopped
condition, the board passes directly in the Start confirmation status.
• If the engine running status is diagnosed, then board goes on to Idle speed status
(if configured or requested) or to Running status.
For the Preheat, Fuel solenoid, Washing, Start and Idle speed see what described for
manual starting procedure. As unique difference, the Starting status has a maximum length
configurable with parameter P.210.
The Start confirmation status is executed when the Idle speed cycle has ended or
however after the engine was acknowledged running. This status is used to wait until the
generator reaches its working conditions. The engine in fact could stop itself (the board
could have acknowledged it running just because the starter has enough speed). In these
cases, the board has to try again to start the engine, until the end of the configured attempts.
From this status the board passes to Running status if the generator reach its working
conditions (in this case the start was successful and a subsequently stop of the engine is
symptomatic of a serious anomaly on genset); board continues with the Delay between two
starts status if the engine stop itself and to the Stopping status if the engine didn’t stop but
the generator didn’t reach its operating condition within the time configured with parameter
P.217 (the alarm A008 - “operating conditions failure” is activated). In this status, the FUEL,
ENABLE and GAS command are active.
The status Delay between two starts is executed each time the engine does not start after
an automatic start attempt. The length of this status is configured with the parameter P.212.
At the end the board goes on with the Start status: this status is executed P.211 times: if
after all the configured attempts the engine did not start, the board actives the alarm A022-
“Overcrank” and goes to the Stop status. In this status FUEL, ENABLE and PREHEAT are
active, in order to use itself for the preheater of Diesel engines.
The starting procedure ends with the Running status. In this phase, the changeover is
enabled (in fact if the generator parameters drop out from the tolerance band, the board
actives alarms or deactivations and force the engine management to execute a stop cycle
with standard or emergency procedure). In this phase, FUEL, ENABLE and GAS commands
are active.
4.5.4.2 Automatic standard stop
The standard stop procedure is preceded by a Cooling cycle (during which the board
changes-over the loads on mains) for the engine. This cycle is done only if during the
Running status the loads were changed-over on generator. During this cycle, the FUEL,
ENABLE and GAS commands are active. The length of the cycle is configurable with
parameter P.215. From this status it is possible to come back to the Running status if the
requests to stop end and it is present at least one start request (for instance the board was
in this status after the return of mains, but during the Cooling mains fault again). The cycle
can be interrupted also if an emergency stop request rises up (an alarm or the key switched
to OFF). In this case, or in any case when the time P.215 ends, the emergency stop cycle
follows.
After Cooling, the board begins to stop the engine; see the following paragraph.
4.5.4.3 Automatic emergency stop
The emergency stop procedure consists in stopping the engine without the cooling cycle.
This procedure is common also in the standard stop, after exactly the cooling cycle. During
the Stopping phase the commands FUEL, GAS, START and PREHEAT are disabled and
instead the STOP command is active. The length of this phase is set with parameter P.213
(stop pulse duration). When this time is over, the board passes in the Waiting for stopping
status. If during this phase all stop requests cease and at least one start request is present,
the board passes to Cancel stopping status but only and uniquely if the engine was
acknowledged stopped. It is not in fact possible interrupt an automatic stop cycle, because
situations in which the engine may be difficult to restart if not previously stopped can happen
During the Waiting for stopping phase, all engine commands are disabled and board waits
exactly the engine stop. The length of this phase is configurable with parameter P.214 (stop
cycle duration, to which it is subtracted the time set by P.213). At the end of this phase, if the
engine is still running, it is activated the A021 alarm – “overcranck” and the board passes to
the Not stopped status. The entire Waiting for stopping phase (and so the alarm too) can
be in any case disabled setting to zero the P.214 parameter. If the engine stops, the board
comes back to the Stopped status. This phase cannot be interrupted to effect further starts
The phase Cancel stopping is used only to allow a little delay between the deactivation of
the possible STOP command and the activation of the FUEL and ENABLE commands. This
delay is set to 0.2 seconds, at the end of which the board comes back to the Stopped
status, and goes immediately on with the start having the right conditions (and restarting
from zero the start attempts count).
circuit breaker (KG), the three remaining are dedicated to the mains circuit breaker (KR). It is
possible to configure the board to command two separated breakers or a power switch
o Separated breakers. It has to be used the KG “normally open” contact to connect the
load to the generator. It has to be used, instead, the KR “normally closed” contact for
command the connection of the loads to the mains. In this way, with the board not
supplied (and so with both the relays at rest) the loads are connected to mains. To
use this function it needs to set the parameter P.219 to a proper value. This
parameter set the minimum time that has to elapse between the open of a breaker
and the closing of the other. DST4400 never closes at the same time the two
breakers
o Power switch. It has to be used the KG “normally open” contact for the command to
changeover the loads to genset. The changeover on mains is done when this
contact is open. To use this function, P.219 must be set to zero (see above);
otherwise, there will be a useless wait during the phase of changeover between
genset to mains. Moreover, it is possible to configure with the parameter P.220 a
minimum time for the holding of the power switch command: it will be not possible
(nor in manual neither in automatic) to invert the power switch command until the
time P.220 is not passed since previous command. This is useful because if the
command is inverted during the movement phase, with some type of power switches
it is possible that they lock themselves, and a manual action will be required to
unlock them.
The LEDs on the panel, named KR and KG, are switched on when the respective breaker is
closed and are switched off when it is open.
The board normally considers commanding directly the breakers. If their command is subject
to other external logics, it is possible to connect the status of one or both the breakers to the
board’s digital inputs. Then the board should be configured to acquire the status from the
connected input (codes 06 for KR and 07 for KG in the P.507… parameters). Using this
function, the actual status of the breakers is shown on the frontal panel:
o Flashing KR/KG led (on for 25% of the time): the board has commanded the breaker
to close, but it is open.
o Flashing KR/KG led (on the 75% of time): the board has commanded the breaker to
open, but it is closed.
Besides, configuring a time different from zero for the inputs that are connected to the
breaker status (parameters P.508…), the board actives a warning if the command and the
status stay conflicting consecutively for that time.
It is however possible to connect also the status of only one breaker (if needed): the
signalling of the conflicts command/status and the incidental warnings will be managed only
for this breaker.
4.6.1 Change-over logic
Loads can be changed-over to generator only if all the following conditions are verified:
o Generator voltages and frequency are in the tolerance band from a proper time (see
the generator sequence description).
o The engine has been started by the board (the fuel solenoid command must be
active).
In the OFF/RESET mode, loads are always changed-over to mains (and so, switching the
key in this position will cause an automatic changeover to mains if load was connected to
genset).
In the MAN mode, loads are usually changed-over to mains. Using the KR/KG button it is
possible to invert the changeover status (the changeover to genset is possible only if the
conditions previously seen are verified). NOTE: it is possible only to invert the status: it is not
possible to open both the breakers. Passing from AUTO to MAN, the changeover status
rests unchanged (with /P version, it is forced the change-over to mains.
In AUTO mode, the loads are changed-over on genset (with respect of the proper
conditions) only when mains is out of the tolerance thresholds. As soon as mains comes
back in tolerance (with proper times, see mains sequence), loads are newly changed-over
on mains. Passing from any other working mode to AUTO, loads are forced as described,
driving a changeover if needed. The KR/KG button is ignored. This status uses another
timing: to close the loads on genset it must be passed the P.218 time since engine started,
or, more precisely, since the genset voltages and frequency are internal to the its tolerance
bands. This delay is used mainly to give a minimum time to the engine to warm itself before
supply the load. The automatic changeover can be inhibited setting and activating an
apposite digital input (see par. 6.10)
In the TEST mode, loads are normally changed-over to mains. Using the parameter P.222, it
is possible to force a changeover to genset following an engine start. Passing from any other
working mode to TEST, loads maintain their status. Using the LOAD/UNLOAD button it is
possible to invert the changeover status (the changeover to genset is possible only if the
conditions previously seen are verified). NOTE: it is possible only to invert the status: it is not
possible to open both the breakers. For this status too the delays configured with P.218 are
applied. NOTE: the board passes automatically in AUTO (aborting TEST mode) if its
automatic intervention is required.
In the REMOTE START mode loads are always supplied by genset (in the conditions
previously seen), also with mains presence. All timings of AUTO mode are valid. The KG/KR
button is ignored. NOTE: the board passes automatically to AUTO mode (aborting REMOTE
START mode) if its automatic intervention is required (fault on mains). It is possible to
configure a digital input with code “30-changeover inhibition”; when activated this input
inhibits the automatic changeover but only in remote start mode and only if the remote start
command is required with a digital input (not by serial command). See also EJP function
description in par. 6.16.
Wait mains -
genset
On mains
On genset
Wait genset -
mains
This diagram describes the changeover status. We examine it starting from the rest status
On mains. In this status both KR and KG relays are at rest (so closing loads on mains
because the command for the mains breaker is taken from the normally closed contact of
KR). If a changeover on genset is required, board passes to the Wait mains-genset status
only if KR relay is at rest at least since P.220 time, otherwise board waits in this status
During the Wait mains-genset phase the KR relay is at work, whereas KG is at rest (so
opening both the breakers, or confirming the change over on mains with power switch). In
this status, the board stays for the time configured by parameter P.219, then it passes to the
On genset status. If during the wait the changeover to genset request disappears, it comes
back to the On mains status, but only when the time P.220, since the entry in this status, is
elapsed
In the On genset status both KR and KG relays are at work (closing then the loads on
genset because the command for the mains breaker is taken from the normally open contact
of KR). If it is required a change-over on mains, it passes to the Wait genset-mains status
only if the KG relay is at rest at least since time P.220, otherwise the board waits in this
status
In the Wait genset-mains phase the KR relay is at work whereas KG is at rest (so opening
both the breakers, or forcing the change over on mains if it is used a power switch). In this
status, the board stays for the time configured by P.219, then passes to On mains status. If
during the wait a changeover to genset is activated, the board come back to On genset
status, but only when the time P.220, since entry in this status, is elapsed.
5. Anomalies
This chapter describes all the anomalies managed by the board. Some of these act as
protections for the loads, for the generator or for the engine. There is also signaling of
particular events in the management of the plant. Before describing them in detail, it is
opportune to give some definitions.
• Warnings: these anomalies don’t require the arrest of the engine. They point out to
situations that are not dangerous at the moment, but the operator must take some
action because, if ignored, they could degenerate in one of the following categories.
• Deactivations: these anomalies require the arrest of the engine. They are
dangerous for the loads but not immediately for the engine. For this reason the
engine can be stopped with the standard procedure (with the cooling cycle).
However, it is not possible to restart the engine until someone takes care of the
anomaly.
• Alarms: these anomalies require the arrest of the engine. They are dangerous for
the loads and/or for the engine and for the generator. For this reason the engine
must be stopped immediately, without the cooling cycle. It is not possible to restart
the engine until someone takes care of the anomaly.
a) It activates the internal horn and, if configured, also the external one.
b) It forces the multifunction display on MODE 1 (see the signaling description of the
frontal panel).
c) It shows the numerical code (see the anomalies description) and the text, in the
selected language, related to the anomaly on second row of the multifunctional
display (see the signaling description of the frontal panel).
d) It flashes the MODE2 LED if the anomaly is a warning, otherwise the MODE3 LED
a) Acknowledge: this indicates to the board that the operator has token action about
the situation.
b) Reset: it tells to the board that the anomaly is not yet active.
The operator can acknowledge the anomaly (ISA2C sequence) by pressing the MODE key.
This operation also stops the internal and the external horns. The horn management is
however related to the P.491 parameter:
o If set to 999, the horn will be activated when a new anomaly arises, and will be
deactivated when the operator press the MODE key”.
o If set to any value between 1 and 998, the horn will be activated when a new
anomaly arises, and will be stopped both for pressing the MODE key and after
P.491 seconds from activation.
The multifunction display shows the anomaly up to when the operator doesn't acknowledge
it, even if its cause is not still present.
The board automatically reset all the acknowledged warnings when their cause is not still
active. In order to reset the deactivations and the alarms, the operator must move the key-
lock switch in the “OFF/RESET” position (obviously it must be moved back to MAN or AUTO
in order to use the genset again). With this procedure, it is also possible to reset externally
managed anomalies. In fact, one of the board digital outputs can be configured (value 1 in
the parameter P.581 or P.582) to activate itself for one second when the internal reset
procedure is performed. NOTE: this one-second pulse is generated only for the reset
procedure, not for the acknowledgement one.
An alarm can be activated only if no other alarms are already active (there are some
exceptions to this rule and will be underlined in the rest of the paragraph). An alarm can be
activated if some deactivations or warnings are active.
A deactivation can be activated only if no alarms and deactivations are already active.
Instead, some warnings can be active.
A warning can be activated only if no alarms and deactivations are already active. Instead,
some warnings can be active.
Here follows a detailed description of each anomaly. The word “enable” will be used to
describe the minimum conditions needed by the board in order to look for the anomaly. The
word “activation” will be used to describe the condition needed by the board to activate the
anomaly, after it has been “enabled”.
Note: normally all protections are “enabled” if the engine is started by the board, thus
if the fuel solenoid control is active (with some exceptions). If not, the only way to
“enable” the protections is to force the board to start the engine again (by pressing
the START key in MAN, by example): the cranking motor will not be activated, but the
fuel solenoid control will be set and so all the protections will be “enabled”.
This protection is enabled only if the engine was started by the board (fuel solenoid control
activated), and is disabled during the engine starting and stopping cycle. It is enabled when
the generator voltages and frequency firstly enter inside the band of tolerance (from the
engine start moment, see the engine sequence description). It is activated if, in the
previously conditions, at least one generator voltage falls under the P.301 threshold,
continuously for the P.302 time.
This protection is enabled only if the engine was started by the board (fuel solenoid
command activated), and is disabled during the engine starting and stopping cycle. It is
activated if, in the previously conditions, at least one generator voltage become greater than
the P.303 threshold, continuously for the P.304 time.
This protection is enabled only if the engine was started by the board (fuel solenoid control
activated), and is disabled during the engine starting and stopping cycle. It is enabled when
the generator voltages and frequency firstly enter inside the band of tolerance (from the
engine start moment, see the engine sequence description). It is activated if, in the
previously conditions, the generator frequency falls under the P. 305 threshold, continuously
for the P. 306 time.
This protection is enabled only if the engine was started by the board (fuel solenoid control
activated), and is disabled during the engine starting and stopping cycle. It is activated if, in
the previously conditions, the generator frequency become greater than the P. 307
threshold, continuously for the P. 308 time.
This protection is enabled only if the board is configured to use the D+ signal (P.115=1) and
if this signal is physically connected to the J202 connector. The protection is enabled only if
the engine was started by the board (fuel solenoid control activated) and is disabled in the
cranking and stopping phases. It is activated if the D+ signal potential is lower than the fixed
internal threshold continuously for the P.349 time.
06 – Maximum current
Type: Configurable
Category: Generator protection
Related parameters: P.101 P.102 P.106 P.309 P.310 P.323
To disable: P.310=0
Enabled in: MAN, AUTO, TEST, REMOTE START
DST4400 implements a time-related maximum current protection (it activates so much more
quickly how much higher is the overload). The used curve is named EXTREMELY
INVERSE, and implements an I2t function. It is a generator protection (not an engine
protection) because it limits the thermal accumulation of the generator during, the generation
phase. For the engine, the maximum power protection must be used, that is independent
from the load typology.
We define a maximum current threshold, and the maximum time the generator can work with
this current. If the current is lower than the defined threshold, the protection is not activated.
If the current become greater than the threshold, the protection is activated with a time
inversely proportional with the entity of the over current. In order to correctly set the
thresholds, follow the following steps:
• You must know the nominal current of the system. You can obtain it from the
nominal power (P.106) and the nominal voltage (P.102):
P.106
o Mono-phase system: I nom =
P.102
• Configure the intervention time for the protection in the P.310 parameter: the
protection will be activated exactly after the time you’ve configured if the current is
constantly equals to the P.309 threshold multiplied by 2 . In the previous example,
if you set 10 s in P.310, the protection will be activated after 10 seconds with around
495 A of constant load, in a fewer time if the current is higher, in a longer time if the
current is lower and never if the current is minor than 350 A.
The following graph shows the used curve, with P.310 set to 60 seconds (I is the maximum
current):
Intervent time
1000
Tempo
Intervent
time
intervento
100
Intervent time (seconds)
10
IInI
0,1
1 10
Multiple of I
This protection is enabled only if the engine was start by the board (fuel solenoid command
active) and it’s disabled in the cranking and stopping phases.
Starting from release 00.03 the action of this protection is configurable as deactivation or
alarm (default) with P.323. This parameter (and so the action) is shared with the short circuit
protection.
This protection is always enabled and cannot be disabled. It is activated when, in AUTO,
TEST or REMOTE START the operator presses the STOP key or if a stop command is
received from the serial port or by an SMS. The pressure on STOP key doesn’t active this
alarm only when the engine was manually started in test mode (START key pressed when in
AUTO mode); in this case the STOP key simply stops the test and the engine stops
immediately (without cooling cycle) because there was no load changeover on generator.
This protection is always enabled. It is activated if the generator voltages and frequency are
not firmly inside the band of tolerance within P.217 seconds from the recognition of the
engine running status (or from the end of the engine’s idle cycle, if enabled).
11 – Power reverse
Type: Alarm
Category: Generator protection
Related parameters: P.106, P.313, P.314
To disable: P.314 = 0
Enabled in: MAN, AUTO, TEST, REMOTE START
This protection is enabled only if the engine was started by the board (fuel solenoid control
activated), and is disabled during the engine starting and stopping cycle. It is activated if, in
the previously conditions, the system total active power is negative and has an absolute
value greater than the P.313 threshold, consecutively for P.314 seconds.
12 – Genset locked
Type: Alarm
Category: Generic
Related parameters: -
To disable: -
Enabled in: MAN, AUTO, TEST, REMOTE START
This protection is always enabled and cannot be disabled. It is activated when the board
receives the lock command from the serial port or by an SMS. It is deactivated only when the
board receives the unlock command from the serial port or by an SMS. Disconnecting the
board from the battery cannot disable the protection. This feature can be useful in case of
rent; if the client requires the genset during the weekends of a month, the renter can lock the
genset from Monday to Friday, and is not forced to continuously move the genset to and
from the client
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the KR status (code 6 for P.507 parameters, or equivalent for other inputs), and if a
delay different from zero has been set for this input (P.508 or equivalent for other inputs). It
is activated only when the board closes the KR (relay on idle) but the acquired status is not
active (open) continuously for the configured time. No automatic changeover to the
generator is provided.
Related parameters: P.507 P.508 (for input 1, or equivalent parameters for the input to
configure)
To disable: P.508=0 (or equivalent)
Enabled in: AUTO, TEST, REMOTE START
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the KG status (code 7 for P.507 parameters, or equivalent for other inputs), and if a
delay different from zero has been set for this input (P.508 or equivalent for other inputs). It
is activated only when the board closes the KR (relay at work) but the acquired status is not
active (open) continuously for the configured time. No automatic changeover to the mains is
provided
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the external over load contact (code 17 for P.507 parameters, or equivalent for other
inputs), and if a delay different from zero has been set for this input (P.508 or equivalent for
other inputs). It is always enabled, also with KG open and engine dead. It is activated if the
configured input is active continuously for the related time.
Until release 02 included, the protection was enabled only if the engine was started by the
board (fuel solenoid control activated), only if the loads were connected to the generator and
it was disabled during the engine starting and stopping cycle.
DST4400 implements a short circuit protection, in addition to the over current protection.
This is in order to act as much faster as possible and to be untied with the timing described
for the over current protection. The protection is configured by setting a threshold (P.311)
expressed as a percentage of the nominal current (see the maximum current protection for
how to calculate the nominal current from the parameters P.101, P.102 e P.106). It is
enabled only if the engine was started by the board (fuel solenoid control activated), and is
disabled during the engine starting and stopping cycle. It is activated when at least one
phase’s current is higher than the threshold P.311 continuously for P.312 seconds.
Related parameters: P.507 P.508 (for input 1, or equivalent parameters for the input to
configure)
To disable: P.508=0 (or equivalent)
Enabled in: MAN, AUTO, TEST, REMOTE START
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the external over speed contact (code 18 for P.507 parameters, or equivalent for
other inputs), and if a delay different from zero has been set for this input (P.508 or
equivalent for other inputs). It is enabled only if the engine was started by the board (fuel
solenoid control activated), and is disabled during the engine starting and stopping cycle. It
is activated if the configured input is active continuously for the related time.
This protection is enabled only if the board acquires the engine speed measure. It can be
acquired by the pick-up input (P.110 different from zero) or by the W input (P.111 different
from zero) or by the CAN BUS (P.700 different from zero). It is enabled only if the engine
was started by the board (fuel solenoid control activated), and is disabled during the engine
starting and stopping cycle. It is activated when the acquired speed is higher than the P.333
threshold continuously for P.334 seconds
This protection is enabled only if the engine was started by the board (fuel solenoid control
activated), and is disabled during the engine starting and stopping. It is activated when the
generator frequency is higher than the P.331 threshold continuously for P.332 seconds.
Note: P.331 is expressed as a percentage of P.105
This protection is activated if the engine does not stop itself before P.214 seconds from the
stop command. Note: this alarm can be activated even if another alarm is still active.
22 – Over crank
Type: Alarm
Category: Battery protection
Related parameters: P.211
To disable: -
Enabled in: AUTO, TEST, REMOTE START
This protection is activated after P.211 attempts of starting the engine without results. It
cannot be disabled.
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the KR status (code 6 for P.507 parameters, or equivalent for other inputs), and if a
delay different from zero has been set for this input (P.508 or equivalent for other inputs). It
is activated only when the board opens the KR (relay on work) but the acquired status is
active (closed) continuously for the configured time. No automatic changeover to the
generator is provided.
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the KG status (code 7 for P.507 parameters, or equivalent for other inputs), and if a
delay different from zero has been set for this input (P.508 or equivalent for other inputs). It
is activated only when the board opens the KG (relay on idle) but the acquired status is
active (closed) continuously for the configured time. No automatic changeover to the mains
is provided.
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the minimum fuel level contact (code 8 for P.507 parameters, or equivalent for other
inputs), and if a delay different from zero has been set for this input (P.508 or equivalent for
other inputs). It is activated if the configured input is active continuously for the related time.
To disable: P.348=0
Enabled in: MAN, AUTO, TEST, REMOTE START
This protection is enabled if the board is configured to use the analog fuel level sensor
(P.114 different from zero), and if this sensor is connected to the J204 connector. It is
activated when the fuel level is lower than or equal to the P.347 threshold continuously for
P.348 seconds.
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the low fuel level contact (code 9 for P.507 parameters, or equivalent for other
inputs), and if a delay different from zero has been set for this input (P.508 or equivalent for
other inputs). It is activated if the configured input is active continuously for the related time.
This protection is enabled if the board is configured to use the analog fuel level sensor
(P.114 different from zero), and if this sensor is connected to the J204 connector. It is
activated when the fuel level is lower than or equal to the P.345 threshold continuously for
P.346 seconds.
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the high fuel level contact (code 12 for P.507 parameters, or equivalent for other
inputs), and if a delay different from zero has been set for this input (P.508 or equivalent for
other inputs). It is activated if the configured input is active continuously for the related time.
This protection is enabled if the board is configured to use the analog fuel level sensor
(P.114 different from zero), and if this sensor is connected to the J204 connector. It is
activated when the fuel level is greater than or equal to the P.343 threshold continuously for
P.344 seconds.
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the high coolant temperature contact (code 15 for P.507 parameters, or equivalent
for other inputs), and if a delay different from zero has been set for this input (P.508 or
equivalent for other inputs). It is enabled only if the engine was started by the board (fuel
solenoid control activated), and is disabled during the engine starting and stopping cycle. It
is activated when the configured input is active continuously for the related time, but only
after P.216 seconds was elapsed from the engine start (oil mask time). This is useful to
avoid false anomalies when the engine starts immediately after a previous emergency stop;
in this situation, in fact, the engine has the tendency to warm up itself.
This protection is enabled only if the board acquires the engine coolant temperature
measure. It can be acquired by the board input 4/5 of J204 connector (P.113 different from
zero). It is enabled only if the engine was started by the board (fuel solenoid control
activated), and is disabled during the engine starting and stopping cycle. It is activated when
the acquired temperature is higher than or equal to the P. 335 threshold continuously for P.
336 seconds, but only after P.216 seconds was elapsed from the engine start (oil mask
time). See previous paragraph note.
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the maximum coolant temperature contact (code 16 for P.507 parameters, or
equivalent for other inputs), and if a delay different from zero has been set for this input
(P.508 or equivalent for other inputs). It is enabled only if the engine was started by the
board (fuel solenoid control activated), and is disabled during the engine starting and
stopping cycle. It is activated when the configured input is active continuously for the related
time, but only after P.216 seconds was elapsed from the engine start (oil mask time). See
previous paragraphs note
This protection is enabled only if the board acquires the engine coolant temperature
measure. It can be acquired by the board input J204 PINS 4/5 (P.113 different from zero) or
by the CAN BUS (P.700 different from zero). It is enabled only if the engine was started by
the board (fuel solenoid control activated), and is disabled during the engine starting and
stopping cycle. It is activated when the acquired temperature is higher than or equal to the
P.337 threshold continuously for P.338 seconds, but only after P.216 seconds was elapsed
from the engine start (oil mask time). See previous paragraphs note
It is always enabled except when the cranking motor is activated. It is activated when the
battery voltage is lower than the P.362 threshold continuously for P.363 seconds. Note:
P.362 is expressed as a percentage of the nominal battery voltage, which is not configurable
but is automatically selected by the board between 12 e 24 Vdc. The nominal battery voltage
is selected each time the board is powered and each time the key-lock switch is moved to
the OFF/RESET position. The nominal battery voltage is set to 12 V if in the previous
conditions the battery voltage is not greater than 17 V, otherwise is set to 24V
It is always enabled except when the cranking motor is activated. It is activated when the
battery voltage is greater than the P.364 threshold continuously for P.365 seconds. Note:
P.364 is expressed as a percentage of the nominal battery voltage, which is not configurable
but is automatically selected by the board between 12 e 24 Vdc. The nominal battery voltage
is selected each time the board is powered and each time the key-lock switch is moved to
the OFF/RESET position. The nominal battery voltage is set to 12 V if in the previous
conditions the battery voltage is not greater than 17 V, otherwise is set to 24V
39 – Service required
Type: Configurable
Category: Generic
Related parameters: P.424 P.425
To disable: P.424=0
Enabled in: MAN, AUTO, TEST, REMOTE START
It is always enabled. It is activated after P.424 engine working hours since the last time
P.424 was changed. Note: the working hours are counted also if other devices start the
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the minimum oil pressure contact (code 13 for P.507 parameters, or equivalent for
other inputs), and if a delay different from zero has been set for this input (P.508 or
equivalent for other inputs). It is enabled only if the engine was started by the board (fuel
solenoid control activated), and is disabled during the engine starting and stopping cycle. It
is activated when the configured input is active continuously for the related time, but only
after P.216 seconds was elapsed from the engine start (this delay is needed to ignore the
normal low pressure state when the engine starts up).
This protection is enabled only if the board acquires the engine oil pressure measure. It can
be acquired by the board input (PIN 3 of J204, P.112 different from zero) or by the CAN BUS
(P.700 different from zero). It is enabled only if the engine was started by the board (fuel
solenoid control activated), and is disabled during the engine starting and stopping cycle. It
is activated when the acquired pressure is lower than or equal to the P. 341 threshold
continuously for P. 342 seconds, but only after P.216 seconds was elapsed from the engine
start (oil mask time). See previous paragraph note.
This protection is enabled only if one of the digital inputs of the board is configured to
acquire the low oil pressure contact (code 14 for P.507 parameters, or equivalent for other
inputs), and if a delay different from zero has been set for this input (P.508 or equivalent for
other inputs). It is enabled only if the engine was started by the board (fuel solenoid control
activated), and is disabled during the engine starting and stopping cycle. It is activated when
the configured input is active continuously for the related time, but only after P.216 seconds
was elapsed from the engine start (oil mask time). See previous paragraphs note.
This protection is enabled only if the board acquires the engine oil pressure measure. It can
be acquired by the board input (J204 PIN 3, P.112 different from zero) or by the CAN BUS
(P.700 different from zero). It is enabled only if the engine was started by the board (fuel
solenoid control activated), and is disabled during the engine starting and stopping cycle. It
is activated when the acquired pressure is lower than or equal to the P. 339 threshold
continuously for P. 340 seconds, but only after P.216 seconds was elapsed from the engine
start (oil mask time). See previous paragraphs note
48 – Emergency stop
Type: Alarm
Category: Generic
Related parameters: P.507 P.508 (for input 1, or equivalent parameters for the input to
configure)
To disable: -
Enabled in: MAN, AUTO, TEST, REMOTE START
This protection is always enabled and cannot be disabled. It is activated when one digital
input is configured to acquire the emergency stop contact (code 28 in P.507 or equivalent). It
is enabled when the input contact is not grounded continuously for the related time. (Note:
when the emergency push-button is pressed, the related contact is open).
49 – High power
Type: Warning
Category: Engine protection
Related parameters: P.106 P.481 P.483 P.484 P.485 P.486
To disable: P.486=0
Enabled in: MAN, AUTO, TEST, REMOTE START
This protection is enabled setting the value 1 in parameter P.481 and setting in parameters
P.483 and P485 two thresholds different from zero (the first lower than the second). The
thresholds implement a hysteresis band. It’s enabled only if the engine was started by the
board ((fuel solenoid control activated) and it is disabled in the starting and stopping phases.
It is activated if the total active power stays higher or equal to the threshold P.485
(expressed as percentage of P.106) consecutively for the time P.486.
It is activated when the internal board temperature is higher than the P.366 threshold, even
for a small time.
It is enabled only in three-phase systems (P.101=3) and only if the engine was started by the
board (fuel solenoid control activated), and is disabled during the engine’s starting and
stopping cycle. The generator voltages and frequency must be inside the band of tolerance
and the loads must be connected to the mains (because the protection prevents the loads to
be connected to the generator). You can set the required phases sequence by using the
P.319 parameter (0=disable, 1=CW, 2=CCW). The protection is activated when the
generator phases sequence is different from the configured one continuously for 0,5
seconds. When activated, it acts as warning, deactivation or alarm as configured with the
P.320 parameter.
It is always enabled. It is activated if the board acquires the not valid status from the clock
and is configured at least one function that needs the clock, such as the periodic engine test
(P.418 e P.420) or the working enabled time periods (P.421, P.422, P.423). If you set the
clock, the protection is deactivated.
It is enabled only if CAN BUS option is present and configured (P.700 <> 0) and if the
transmission from the board to the engine is enabled (P703 <> 0). It is activated if internal
CAN controller enters the BUS-OFF status because of communication errors on bus. See
document EAAM0136XX for more details. When active, it signals the impossibility of the
board to send information (as requested engine speed) to the engine. It is automatically
disabled when the communication with the engine comes back. It is possible to manually
attempt to reset the warning going in the fifth window of the “MODE 4” mode (the one with
the message “CAN:BUS-OFF”) and keeping pressed the VIEW key for at least five seconds.
From release 00.07 it is possible with P.709 to configure the action this anomaly must
generate (warning, deactivation alarm). See anomaly n° 98 for its management.
It is enabled only if it is configured the management of the fuel pump for an external tank
(one output must be configured as pump command with the code “3- fuel pump”) and if the
time in P.404 is <>0. The protection is activated if the pump stays switched on consecutively
for the time P.404; the warning stops the pump command passing it in the “MAN-OFF”
status. See also the paragraph related to the fuel pump management.
From rel. 00.04. It is enabled if the board acquires the coolant (water, oil) temperature by
sensor or CAN and with P.354 <> 0. It is activated if the temperature stays lower than the
threshold P.353 for consecutively P.354 seconds.
Type: Configurable
Category: Generic
Related parameters: P.507 P.508 P.509 P.216
To disable: P.507=0
Enabled in: MAN, AUTO, TEST, REMOTE START
With the P.507 parameter, you can configure the type of protection you want. The following
codes are available:
• 04: generic external engine alarm, masked by P.216 parameter. It is enabled only
after P.216 seconds from the engine starting time.
• 19: generic external engine warning, masked by P.216 parameter. It is enabled only
after P.216 seconds from the engine starting time.
• 21: generic external warning, masked by gas valve control. It is enabled only when
this control is active.
• 22: generic external alarm, masked by gas valve control. It is enabled only when this
control is active.
• 23: generic external warning, masked by fuel solenoid control. It is enabled only
when this control is active.
• 24: generic external alarm, masked by fuel solenoid control. It is enabled only when
this control is active
• 31: generic external warning, masked by KG control. It is enabled only when the
board is commanding KG or, with the inputs to read the real changeover status
enabled, if the KG is effectively closed.
• 32: generic external alarm, masked by KG control. It is enabled only when the board
is commanding KG or, with the inputs to read the real changeover status enabled, if
the KG is effectively closed.
The codes 01, 19, 21, and 23 act as warnings, the code 02 as deactivation and the codes
03, 04, 22 e 24 as alarms. The anomaly is activated when the input is grounded (in the
respect of the specific conditions of each) continuously for the time configured for that input
(P.508). You must configure the text related to the anomaly with the parameter P.509
because no text is provided by the board for those generic anomalies (but the numeric code
is fixed).
Since release 00.04. The protection is enabled only if an input is configured with the code
“34-external fuel tank empty” and P.508 (or the parameter related to the configured input) is
<>0, with the pump management in “MAN” or “AUTO” mode. It is activated if the configured
input stays activated consecutively for the time P.508 (or its equivalent). The protection
stops the fuel pump command (see the related paragraph) to avoid the fuel pipes run dry.
Since release 00.07. This protection is enabled only if the board is connected via CANBUS
with MTU engines and it is configured for them with P.700. The protection is used only with
MTU engine because MTU standard explicitly requires a stop command on an apposite
engine ECU pin if communication errors are present. The anomaly is configurable as
warning (1), deactivation (2) or alarm (block, 3) by means of P.709 (default = warning). The
MTU standard requirement can be satisfied in two ways (this is valid for the anomaly 62 too):
• configuring parameter P.709 with the value 3 and using the STOP SOLENOID
command (as for the excitation shutdown systems) to remove the enabling
command from MDEC unit (pin 25W004).
• if for any reason the anomaly cannot be used as block, it is possible to use the
outputs mapping function to associate the anomaly 98 and/or 62 to a configurable
output: when one of these anomalies is activated, also the configured output will do.
This output must be connected to the enabling command of the MDEC unit. Check
the polarity of the logic of the command required by the MDEC; in case a relay can
be used to invert the logic level of the signal.
This protection is enabled only if the board is connected to the engine by CANBUS (P.700 <>0). Up to
release 00.06 the protection was enabled only if the engine was started by the board (fuel solenoid
command activated) and was disabled in the start and stopping phases. From release 00.07 the protection is
no more subject to the engine running status acknowledged by the board (the engine itself does the mask if
required). The protection is activated when the engine signals the belt break status on CANBUS
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). Up to release 00.06 the protection was enabled only if the engine
was started by the board (fuel solenoid control activated), and was disabled during the
engine starting and stopping cycles. From release 00.07 the protection is no more subject to
the engine running status acknowledged by the board (the engine itself masks it if required).
The protection is activated when the engine signals the over speed state on the CAN BUS
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). Up to release 00.06 the protection was enabled only if the engine
was started by the board (fuel solenoid control activated), and was disabled during the
engine starting and stopping cycles. From release 00.07 the protection is no more subject to
the engine running status acknowledged by the board (the engine itself masks it if required).
It is activated when the engine signals the high coolant temperature state over the CAN
BUS.
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). Up to release 00.06 the protection was enabled only if the engine
was started by the board (fuel solenoid control activated), and was disabled during the
engine starting and stopping cycles. From release 00.07 the protection is no more subject to
the engine running status acknowledged by the board (the engine itself masks it if required.
It is activated when the engine signals the maximum coolant temperature state over the CAN
BUS.
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). It is activated when the engine signals the minimum coolant level
state over the CAN BUS.
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). It is activated when the engine signals the low coolant level state
over the CAN BUS.
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). It is activated when the engine signals the low battery voltage
state over the CAN BUS.
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). Up to release 00.06 the protection was enabled only if the engine
was started by the board (fuel solenoid control activated), and was disabled during the
engine starting and stopping cycles. From release 00.07 the protection is no more subject to
the engine running status acknowledged by the board (the engine itself masks it if required.
It is activated when the engine signals the minimum oil pressure state over the CAN BUS.
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). Up to release 00.06 the protection was enabled only if the engine
was started by the board (fuel solenoid control activated), and was disabled during the
engine starting and stopping cycles. From release 00.07 the protection is no more subject to
the engine running status acknowledged by the board (the engine itself masks it if required.
It is activated when the engine signals the low oil pressure state over the CAN BUS.
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). Up to release 00.06 the protection was enabled only if the engine
was started by the board (fuel solenoid control activated), and was disabled during the
engine starting and stopping cycles. From release 00.07 the protection is no more subject to
the engine running status acknowledged by the board (the engine itself masks it if required.
It is activated when the engine signals the high oil temperature state over the CAN BUS.
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). Up to release 00.06 the protection was enabled only if the engine
was started by the board (fuel solenoid control activated), and was disabled during the
engine starting and stopping cycles. From release 00.07 the protection is no more subject to
DST4400 TECHNICAL HANDBOOK - 21/12/05 - pag. 60
EAAM010504I.doc
the engine running status acknowledged by the board (the engine itself masks it if required.
It is activated when the engine signals the maximum oil temperature state over the CAN
BUS.
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). It is activated when the engine signals the water in fuel state
over the CAN BUS.
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). It is activated when the engine signals the active state of its
yellow lamp over the CAN BUS.
This protection is enabled only if the board is connected to the engine via the CAN BUS
(P.700 different from zero). It is activated when the engine signals the active state of its red
lamp over the CAN BUS. Note: this is only a warning; the alarm should be activated on
another code 1xx
6. Other functions
6.1 Nonvolatile memory
The board is provided with a nonvolatile memory, used to store many information such as
parameters, counters etc... The memory is divided into ten areas. The data stored in each
area are provided with a checksum for their validation. When you supply the power to the
board, it verifies all the data stored in each area: if at least one area is not correct, the
following message will be shown (after the window with the firmware release):
MEM ERRORS.(xxx)
PRESS MODE
Between the square brackets, one hexadecimal number is shown: each bit of this number
set to one corresponds to a not valid memory area. The following table shows the memory
areas and the related bits
Area Version Bit Value Description
1 00.00 0 1 (001) Display contrast
2 00.00 1 2 (002) Current language
3 00.00 2 4 (004) Various (service request, board block, etc.)
4 00.00 3 8 (008) Calibration offsets for measure inputs
5 00.00 4 16 (010) Calibration factors for measure inputs
6 00.00 5 32 (020) Fuel level sensor setting
7 00.00 6 64 (040) Maximum peaks
8 00.00 7 128 (080) Counters
9 00.00 8 256 (100) Parameters
10 00.14 9 512 (200) Parameters for outputs mapping
By example, if the value inside the square brackets is “80”, It means that only the counters
area is non valid. If the value is “101”, it means that both the parameters area (100) and the
current language area (002) are not valid
If at least one area is not valid, the normal working sequences are not executed until the
operator presses the MODE key: it is necessary that the operator acknowledge the situation
because there can be malfunctions (for example, if the non valid area is the parameters
one). The board reloads the default values for the not valid data only when the operator
press the MODE key: this means that if you switch off the power of the board without
pressing the MODE key, when you re-connect the power the board will show again the same
memory error.
6.2 Clock
The board is provided with a hardware internal clock. If the capacitor/battery option is not
present, date/time settings will be lost if the board is disconnected from its power supply. For
each case the date/time is shown on the multifunction display (only when the board is
supplied) and is configurable from the menu 4.2 of the program function or from the serial
port, and is used for many functions:
• Weekly planning of time intervals in which the genset must not automatically starts.
• P.418: lets you specify in which days of week to perform the engine TEST. It is a bit-
configurable parameter; each bit of the parameter corresponds to a day of week.
The value you must set for the parameter is the sum of the value field of the
following table for the days needed.
0 1 Sunday
1 2 Monday
2 4 Tuesday
3 8 Wednesday
4 16 Thursday
5 32 Friday
6 64 Saturday
By example, if you want to perform the TEST only on Monday and Thursday, you
must set 18 (16+2).
• P.419: lets you set start time for the TEST (Hours and minutes).
By P.420 you configure duration instead of a time for the end of TEST. This is because the
same parameter is used also for the TEST activated by an SMS command.
6.2.2 Working time intervals weekly planning.
In some applications, it is useful to inhibit the automatic intervention of the engine for mains
failure in hours or days where the mains is not used. For example, if a factory is closed on
Sunday, the engine should never start in this day for mains fault (because it consumes
unnecessary fuel). With this function, you can select in which days and in which time
intervals the engine can start automatically. The planning is made weekly: it is so possible as
many days of week as required, and also one time interval for enabling automatic
intervention of the engine; this time interval will be the same for all selected days.
• P.421: lets you specify in which days of week the engine can start automatically. It is
a bit-configurable parameter; each bit of the parameter corresponds to a day of
week. The value you must set for the parameter is the sum of the value field of the
following table for the days needed
0 1 Sunday
1 2 Monday
2 4 Tuesday
3 8 Wednesday
4 16 Thursday
5 32 Friday
6 64 Saturday
• P.422: lets you configure the start of the time interval into which the engine can start
automatically (by hours and minutes).
• P.423: lets you configure the end of the time interval into which the engine can start
automatically (by hours and minutes).
Normally P.422 will be set to a lower value than P.423. Instead, if it contains a greater value,
the board interprets that the time interval is configured across midnight: in this case, the time
set by P.422 is referred to the days selected by P.421, while the time set by P.423 is referred
to the next days.
By example, if you want that engine can automatically start only on Monday and Friday,
between 08:00 and 18:00, you must set:
P.421=62 (2+4+8+16+32)
P.422 = 08:00
P.424 = 18:00
6.3 Thermometer
The board is provided with a hardware thermometer, for measuring its internal temperature.
The temperature is shown on the multifunction display. It is used for many functions
• The LCD displays become slower in showing information at very low temperatures.
By using the thermometer, when the temperature falls under a very low threshold,
the board switches on the backlight lamp of the display, and this contributes to warm
it up and to improve its performances.
• The electronic components inside the board have an extended working temperature
range. Despite this, it is possible in critical ambient conditions that temperature goes
out of this range. The board uses the thermometer to activate a warning if the
ambient temperature becomes greater than a configurable threshold. This is useful
for alerting the operator, but is also possible to use one board configurable output for
activate an external cooling system (by using the bit-mapping function you can
configure one output to follow the state of the high internal temperature warning)
• For diagnosis purpose, the board stores in its history logs the most high and low
temperature measured, by using also the internal clock. With this function, it is
possible to examine in a second time the board working conditions, checking if it is
necessary to install external warming/cooling systems, in order to improve the
operating conditions
6.4 Counters
The board manages internally the following counters:
1. Active power (kWh): it counts only the supplied power, it does not count in case of
power reverse.
3. Engine starts
5. Engine running hours with load (with KG closed), from rel. 00.04
All these counters are visualised on board frontal panel and are readable by means of serial
port (with the ModBus protocol). Some of these counters can be reset from operator by a
proper procedure or by means of the serial port; in no way can be reset the time to next
service counter, the absolute engine running hours counter and the board absolute supply
time counter. All these counters are saved in a non-volatile memory and so they maintain
their value also removing supply from the board. Since non-volatile memories “consume”
themselves writing in them, it is necessary to reduce at the minimum the number of writings.
For this reason, a counter is not immediately saved as its value changes, and it is then
important to know when values are saved and how to be sure that they are saved before
removing supply from the board.
Counters are saved (all together and in the same time) in the following conditions:
• Immediately after each engine start (with engine running, not after each start
attempt)
• Immediately after each engine stop (when board acknowledges the engine stopped
status, not when stop is request).
• After each engine running hours counter increase, that is for each full hour, (total,
also if the engine has been started for instance six times for ten minutes each time).
• After each absolute engine running hours counter increase, which is for each full
hour, (total, also if the engine has been started for instance six times for ten minutes
each time)
Furthermore, counters are saved when they are reset (singularly or globally) from frontal
panel or serial port. Beware that some counters have a decimal part (example the minutes-
counters associated to hours-counters), which is saved in non-volatile memory too.
Removing supply to the board in an uncontrolled way, there is the risk to loose just this
decimal part. It is however sufficient switch the key to OFF/RESET to force the board to save
data, before removing the supply.
6.5 Maintenance
The board can signal automatically to the operator the periodical service request. This
function is configurable with the parameters P.424 and P.425. In particular, with P.424 it is
configured the running hours beyond which it is request a service. With P.425 it is configured
what kind of signalling has to be activated at the expiry: a warning, a deactivation or an
alarm (the anomaly code is W39 or D39 or A39
The function is enabled if the parameter P.424 contains a value different from zero. The
count starts in the moment this parameter is set. When the time configured has elapsed, the
board memorizes in the non-volatile memory the status of the service request. In this way,
also removing supply to the board, this signalling cannot be lost and it cannot be reset.
Besides, if with P.425 it is selected the signalling by means of an alarm, then the genset will
not be anymore used. This function allows to manage rental contracts “by hour number”.
To cancel the service request (and also the related signalling) it needs to set again the
parameter P.424; it can be set to zero to disable the function, it can be simply confirmed to
require that next service will be after the same hours number, or it can be set with a new
value
The configuration of what type of signal has to be acquired is effectuated with the
parameters P.110 and P.111. Setting a value different from zero in P.110, it is enabled the
management of the pick-up, otherwise, setting a value different from zero in P.111, W signal
management is enabled (if both parameters are set, P.110 has priority).
The number of the teeth of the gear must be set in parameter P.110. If this value is not
known, it can be easily computed.
In parameter P.111 there must to be the ratio between the W signal frequency and the
engine RPM (this one expressed in rotation/second). This number depends on many
factors and it is not easy to calculate. If a frequency counter is available, it is sufficient to
start the engine (it will run at is nominal and known speed, i.e. 1500 rpm) and measure the
W signal frequency, and then calculate the ratio. If a frequency counter is not available, the
following method can be used:
• Start the engine and, when at its rate, note the rpm value shown by the board.
• Calculate the ratio between the visualized speed and the real engine speed
(visualized/real)..
• Multiply the value previously set in P.111 by this ratio and set P.111 with the result
Restarting the engine the speed measurement should be near to the real. Then P.111 can
be adjusted manually until the visualization will be correct; with the same real engine speed,
increasing P.111 the visualized value decreases. To determinate the engine speed, also the
generator frequency can be used.
• A low load condition (used in plants with paralleled gensets to disable the
unnecessary ones).
The condition to monitorize must be chosen using the parameter P.481 being the two
function mutual exclusive. Setting it to zero it is selected the survey on low load, to one the
high load is selected.
Starting from release 03 this function is enabled/disabled with a digital input appositively
configured (code “33-load function enabled) and it is independent from the KG status; if no
input is configured with code 33, the function is always enabled.
6.8.1 Low load
The purpose of this function is to diagnose a low load condition, in a scenario with more
genset working in parallel, in order to disable the ones not required. For the gensets
enabling/disabling it is used one of the configurable board outputs, for which the code 04
(load status) is configured in parameter P.581 (or followings). If no output is configured in
this way, this function is not available.
The board surveys the total active power supplied, confronting it with two thresholds (which
set a hysteresis band): the output is activated (requiring then the disabling of some gensets)
if the power stay below than the lower threshold for the configured time. These thresholds
and delays are set with following parameters:
If the thresholds P.483 and P.485 or inconsistent, the function is disabled. To makes things
working, the board must know the actual closing status of the gensets parallel bus bars (KG)
is only the enabling to the closing of the parallel panels). It must to exist so an input
configured to acquire this status (code 07 in parameters P.507 and followings): if there is
not, the function is not enabled. The moment of closing is needed because, starting from it, a
timing begins (its length is configured with parameter P.482), during which the output is kept
low independently from the power. This time is used to give a way to the system to stabilize
itself before starting to survey powers
• Engine starting, waiting for generator at rate and enable to supply: in this phase the
output is not active.
• Wait for the closing on parallel bus bar (acquired from configurable input): in this
phase the output is not active.
• Wait for the time configured in P.482: in this phase the output is not active.
• Survey of power: if power drops down for P.484 seconds under the threshold P.483
the output is enabled, if it rises for P.486 seconds over the threshold P.485 the
output id disabled; in the other cases it stays unchanged (hysteresis).
Configuring thresholds P.483 and P.485, it must to take in account the power increase on
one genset when one other is stopped: if they are of the same power, there is a doubling of
the power supplied from first. If threshold P.485 is configured with a too low value, as soon
as the second genset is stopped the output will be disabled and this involves a new start of
first genset.
This system works properly only if, when the board acquires the “parallel done” status, loads
are already connected. If they are not, in fact when the initial survey time has finished power
will be very low and so the other genset will be stopped. When loads are connected, this
genset will have to be restart. The input acquiring the parallel done status should be
conditioned to load presence
The board surveys the total active power supplied, comparing it with two thresholds (that fix
so a hysteresis band): the output are disabled if the power stays below the lower threshold
for the configured time. These thresholds and delays are configured with the same
parameters of the low load signalling (see previous paragraph).
The output is then activated in a maximum power situation, and can so be used directly as
control for the disconnecting of loads. Here too it has to beware to the thresholds: when a
part of the loads is disconnected, the power will drop low. If the lower threshold is too high,
the output will be disabled, and this could make the load to be reconnected and so on.
It is also configurable the protection delay (P.351) and the action (warning, deactivation or
alarm) with P.352. By default, the protection is disabled (P.351=0).
Generally an input can be used to active an anomaly (of every category), to acquire status or
controls. In the following, all possibility will be described.
To each configurable input are related three parameters (the following example is made only
for input 01; for other inputs use their own related parameters):
• P.507: this parameter, using a numerical code, allows to choose the function to be
assigned to the input (see after).
• P.508: allows to define a time (expressed in seconds) associated to the input. The
use of this time depends on the function selected with previous parameter.
• P.509: allows to relate a text message to the input (max eighteen characters). It is
used only for functions, which configure the input to generate generic anomalies:
this text will be shown on multifunctional display as message for the anomaly; it is
available also from serial port with ModBus protocol.
The following tables show the possible functions (subdivided by the categories described at
the beginning), showing for each one if and how parameter P.508 is used and if parameter
P.509 is applicable.
Codes to relate the input to the anomaly. For all these functions, parameter P.509 defines
the minimum consecutive time of the input activation so that the board actives the related
anomaly
Codes to acquire external status. For all these functions parameter P.509 (the text) is not
available.
Codes to acquire external commands. For all these functions parameter P.509 is not
available.
30 Changeover From rel. 00.04.See the EJP function description. P.508 is not
sequence used.
inhibition
35 Idle speed From rel. 00.04. Enable the engine idle speed mode.
request
This paragraph will describe all possibilities. To each configurable output is related a
parameter (P.581and followings), which allows configuring the function. Each output has
other two parameters (P.601 and P.602 for output 1), used to configure the output as remote
signalling of status, showing in details what status the board has to signal (see after). No
configurable timing is related to these outputs.
Code Description
2 Glow-plugs preheater commands (Diesel engines)
14 Gas command (gas engines).
16 Stop solenoid command.
23 Idle speed command
24 Coolant heating command (from rel. 00.04.)
25 Engine enable command (from rel. 00.04.)
Code Description
1 Reset pulse. The board generates a one-second-length pulse on this output when
the anomalies reset is made (key switched to OFF/RESET). NOTE: no pulse is
generated when the MODE button is pressed to acknowledge an anomaly.
3 Fuel pump command (from rel. 00.04); see related paragraph
4 Load management.
21 External horn: the output is activated in parallel to internal horn.
Code Description
5 TEST in progress signalling.
6 Mains measurements in tolerance signalling.
7 Generator measurements in tolerance.
8 Engine running signalling.
9 Cumulative generator anomalies signalling: D01, A02, A06, A08, A15, A16, X55.
10 Cumulative engine anomalies signalling: A05, A21, A22, W31, W32, A33, A34,
W37, W38, X39, A41, A42, W43, W44, W49, W132, A134, A135, W136, W137,
A142, W144, W158, A159, W160, W198, W199.
11 Cumulative engine speed regulator anomalies signalling: D03, A04, A11, A17, A18,
A19, A118.
12 Cumulative fuel anomalies signalling: A25, A26, W27, W28, W29, W30.
13 Cumulative changeover anomalies signalling: W13, W14, W23, W24.
17 Cumulative signalling of anomalies classified as alarms and deactivations.
18 Cumulative signalling of anomalies classified as warnings.
19 Key-lock switch in MAN or AUTO.
20 Key-lock in AUTO.
More than these all, there is the code 22. It configures the output for a generic signalling of
internal status. There are 128 conditions, which comprises all blocks and warnings (already
implemented or futures) and a series of status as mains, generator, engine, changeover,
key-lock switch, etc. To each output can be associated from one to 128 conditions, and the
output will be activated if at least one condition is verified (then with an OR logic). NOTE: an
AND logic is possible by selecting all the conditions except which desired, and inverting the
output status. In document EAAM010201 or in its successive releases, there is a table
showing all the possible conditions, numbered from 0 to 127. Not all conditions are
assigned: there are spares for future conditions. In particular, conditions between 0 and 95
are reserved for blocks and warnings
The conditions can be configured on the board using the programming parameters. The 128
possible conditions were been divided in two blocks of 64. For each output two parameters
allow to set the two blocks of 64 bits (for output 1, parameters are P.601 and P.602). Each
parameter allows to set the 64 bits status as hexadecimal string (to represent 64 bits, 8
bytes and then 16 hexadecimal characters are needed). In the 16 hexadecimal digits, the
digit more on the right is the less significant. Moreover, between the two parameters related
to each output, the one with lower index configures the conditions numbered from 0 to 63,
the one with higher index configures the conditions fro 64 to 127. Let us see a practical
example: let us suppose that parameter P.601 contains the string 1000000000000001 and
parameter P.602 the string 0100000400000000. These parameters configure the output 1
(as first in parameter P.581 we need to set 22). In the string in P.601 bits 0 and 60 are
active, which correspond to the conditions 0 (overcranck alarm) and 60 (maximum auxiliary
current alarm). In the string P.602 the bits 34 and 56 are active, which correspond to the
conditions 64+34=98 (cumulative alarms) and 64+56=120 (engine running). The output 1
then will be active if at least one of the four previous conditions is verified (the example has
no meaning; it is used only to show the link between the parameters and the conditions for
the outputs).
It has to remember that a hexadecimal digit has values included between 0 and 9 and
between A and F for a total of 16 different values. The 16 values are given by the
combination of 4 bits; for this reason, it needs 16 characters to express 64 bits. Therefore, to
locate the position of a function in the string, given the number of the function, we have to do
in this way
• First digit on right contains bits (functions) from 0 to 3 or, if this is the higher
parameter (i.e. P.602), the functions from 64 to 67
• For each digit shifting to the left, increase the counter of 4 until the digit containing
the bit (desired function) is located
• As alternative, divide by 4 the number of the function and start to count from the left
up to reach the result of the division; remember that first digit on the left has index 0
• Maximum active total power peak, with the date/time and the coolant temperature (if
acquired) measured at that moment.
• Maximum current peak, for each phase, with the date/time and the power factor of
the phase measured at that moment
PIN 2 and 3 are used respectively to the fuel level sensor and to the oil pressure sensor. The
temperature sensor has to be connected to the PIN 4. Only if this one is a VDO type, PINS
4 and 5 must be connected together.
To this inputs it is possible to connect only resistive sensors (which change their resistance
with the value of the magnitude measured). For the fuel sensor, the maximum resistance
range is from 0 to 400 ohm (for lower excursions there is an apposite programming
procedure to make the empty/full measurements coincide to the sensor excursion extremes,
see par. 3.3). For the other two inputs the board manages VDO, VEGLIA and BERU (only
temperature) sensors.
After connected the sensors, the board has to be configured with parameters P.112, P.113
and P.114 (see document EAAM010201 or its later releases to details about parameters).
The board can work with systems having level detector with contacts or analogue
transducer.
The minimum condition to use this function is that one of the configurable outputs of the
board is associated to the pump command: this configuration can be done setting the code
03 in the programmable outputs parameters (see the parameter table for the valid
parameters).
The management is fully configurable with the program menu “4.1 FUEL PUMP”. It contains
the following 5 parameters:
• P.400: allows to select the pump working mode within the following choices:
o 0 (MAN-OFF): the pump is off no matter what are the fuel level and the
board status.
o 1 (MAN-ON): if the board is not in OFF RESET, the pump is always on and
is stopped when the level is higher than the “pump stop” or “high level
warning” thresholds; the thresholds are identified by contacts or by analogue
sensor (see in the following). When the level drops under these thresholds
the pump is immediately switched on.
o 2 (AUTO): if the board is not in OFF RESET the pump is started if the level
drops lower than the “pump start “, “low level warning” or “minimum level
alarm” thresholds; it is stopped if the level rises higher than the “pump stop”
or “high level warning” thresholds; the pump status doesn’t change if the
level is within the “pump start” and “pump stop” thresholds.
• P.401: allows to select the type of the sensor to use for the pump management
within the following values:
o 0 (analogue sensor). In this case the thresholds for the pump management
are configurable with the following parameters:
• P.404: allows to set a maximum time for the pump working status; it is a time
between 0 and 9999 seconds, with default 0. If the pump stays activated
consecutively for the configured time, it is generated the anomaly “W64-Fuel pump
fault”, the pump is switched off and the pump status passes to “MAN-OFF”. To reset
the anomaly it must be acknowledged (by pressing the ACK key). The pump must
be manually reactivated selecting again the “MAN-ON” or the “AUTO” mode.
It is possible to automatically stop the pump if the fuel level in the storage tank drops under a
determinate limit level, to avoid that the pump can work without draw the fuel. This requires
another digital input, configured with the code “34-external fuel tank empty”, that has to be
connected with a minimum level threshold contact in the external storage tank. If activated,
the input arouses the W97 anomaly and stops the pump; the pump status passes to MAN-
OFF status.
6.14.1 Usage with an analogue level transducer
To use this function it is required:
• The board has to be configured to acquire the measurement from the transducer
(P.114 different from zero).
• The board has got to be configured to command the pump according with this
transducer (parameter P.401 set to zero)
• At least the thresholds for the activation and deactivation of the pump (P.402 and
P.403) must be configured.
• If configured, also minimum, low and high fuel level are used (parameters P.347,
P.345, P.343).
Attention: if the first three conditions are verified, the board manages in any case the pump,
whatever is the threshold value. In particular, the thresholds defined in the last condition are
used also if their related delay times are set to zero (to disable the anomalies). The
configuration of the thresholds is very important; thresholds have to be put in scale (from
lower to higher values) in this order: minimum, low, start, stop, high. For what we said
before, the board works also if the thresholds aren’t in this order; it is enough that the first
three are lower than the last two (internal to the two groups they can be exchanged, but this
is not recommended)
• The board must to be configured to command the pump according to that transducer
(parameter P.401 set to 1)
• At least the pump start and stop contacts must be connected respectively to two
configurable inputs of the board.
• If connected, also minimum, low and high fuel levels are used.
Attention: if the first two conditions are verified, the board manages in any case the pump,
whatever are the connected contacts. In particular, the contacts indicated in the last
condition are used also if their related delay times are set to zero (to disable the anomalies).
Beware then to their configuration. At least, the contacts must respect the following
convention:
• If the level is lower than the pump start threshold, the board assigns the “start”
status.
• If a low level threshold exists, and the level is lower than threshold, the board
assigns the “low” status.
• If a minimum level threshold exists, and the level is lower than the threshold, the
board assigns the “minimum” status.
• If the level is higher than stop threshold, the board assigns the “stop” status.
• If a maximum level threshold exists, and the level is higher than the threshold, the
board assigns the “maximum” status.
• If no one of the previous condition is verified, the board assigns the “hysteresis”
status.
6.14.4 Automatic pump control
Referring to the status evaluated in the previous paragraph, the pump:
To manage the automatism the board must acquire the coolant temperature (by sensor or by
CAN) and one output must be configured with code “23-engine heating command”.
The parameters define a hysteresis band for the heater command: setting P.355 = P.356 the
function works without hysteresis. It is not possible to set P.355 > P.356. The output
configured with the code 24 is activated if the temperature drops under P.355 threshold for 1
second consecutively; it is deactivated if the temperature rises below the threshold P.356
consecutively for 1 second.
Note: DST4400 board is not able to detect EJP signals on the grid. In order to use this
function, an external device detector should be used. The detector should provide
due output signals consistent with the DST4400 EJP functionality.
The EJP function allows to start the engine and warm it before mains faults, so when it will
happen, loads can be immediately changed-over on genset, reducing to the minimum the
time the loads stay unsupplied. EJP is used also to signal the beginning of more expansive
fare band for the energy; some users prefer to generate the energy by theirselves during that
band. EJP is a French specification and regulation.
A. A signal activated well in advance with respect to the mains fault or fare change.
What is desired is to start the engine in some advance (configurable) in respect to B signal;
load however is changed-over only when B is activated. The board can do this, but the
following rules have to be followed:
• A and B signals must stay active until mains comes back (or high fare ends).
To use this function the board has to be configured in the following way:
• Configure one digital input to acquire the “REMOTE START REQUEST” (code 27 in
P.507 or equivalent parameter for other inputs). Moreover, for this input it has to
configure the desired delay between A signal activation and the engine start (in
Then connect the N.O. contact of the relay on A signal to first configured input and N.C.
contact of B signal relay to second input.
When both signals are inactive, the board has not the remote start request and so stays at
rest in AUTO mode. The CHANGEOVER SEQUENCE INHIBITION command is ignored.
When A signal is activated, both board inputs will be active. The board will not pass
immediately to REMOTE START mode, but will do it only after the time configured in P.508
(or equivalents). So in this phase, too the CHANGEOVER SEQUENCE INHIBITION is
ignored. In this phase, window S.02 shows the remaining time.
After the configured time from A signal activation, the board passes in REMOTE START
mode and proceeds to start the engine. In this phase, the CHANGEOVER SEQUENCE
INHIBITION is no more ignored, and being it active (connected on N.C. relay contact), it will
prevent the loads changeover on genset.
When the function ends, both A and B signals are deactivated. Therefore, the board comes
back in AUTO mode, and being mains present, it provides to stop the engine (with cooling
cycle).
Default value is 0.
The events archive can be visualized with the key-lock switch in OFF and pressing the
MODE key. First row shows the date and the time of the event (alternating them each
second) and, on the right side, the number of the visualized event and the total number of
the events recorded (e.g. 2/43 means that it is shown the second event of the 43 recorded).
The enumeration of the events follows their sequence: the event with the higher number is
the more recent. The second row shows the code related to the event, followed by a
description; if the text is longer than 165 characters, it slides from right to left with one-
second steps.
Use the START and STOP keys to browse the events. The archive capacity is of 99 events;
after which the first event (the older one) is overwritten.
Press the VIEW key to exit from the events archive visualization.
6.17.2 Trends archives
The board stores two types of trend archives: fast trend and slow trend. The difference is the
different time interval between two consecutive recordings; the fast trend archive is managed
by parameter P.442, which is the time interval in seconds configurable from 0 to 999 (default
60 seconds). The slow trend archive is managed by P.443, which is the time interval in
minutes, configurable from 0 to 999 (default 30 minutes).
The board records, with its date and time, the following analogue measurements:
o Starting battery voltage, engine rotation speed, coolant temperature, oil pressure
and engine fuel level.
o Active, reactive and apparent powers, the power factor and the type of the plant
total load.
6.18 CANBUS
For an exhaustive description of CANBUS management, ask to S.I.C.E.S. for further
documentation.
Generator voltages L1-L2, L2-L3, L3-L1. True rms measurements. Maximum phase to neutral voltage <
300Vac cat. IV
Generator currents: L1, L2, L3, True rms measurements. Maximum nominal current: 5Aac
Overload conditions measurements up to 4x5Aac (sinusoidal)
Oil pressure gauge: VDO 0-10 Bar, VDO 0-5 Bar or Veglia 0-8 Bar or 0-10V (MTU)
Engine revolution counter: By W, programmable frequency/revolution ratio. Same input can be used with
pick-up signal.