Drive BB Global Guide
Drive BB Global Guide
BaseBox
Engine controller for Gas
applications
SW version 1.0.0
1 Document information 5
2 System overview 10
3 Installation and wiring 14
4 Controller setup 36
5 Communication 182
6 Troubleshooting 186
7 External modules connection 187
8 Technical Data 191
9 Appendix 196
IMPORTANT: This type of paragraph highlights a procedure, adjustment etc., which can cause a
damage or improper function of the equipment if not performed correctly and may not be clear at
first sight.
Example: This type of paragraph contains information that is used to illustrate how a specific function
works.
Note: The controller contains a large number of configurable setpoints, because of this it is impossible to
describe all of its functions. Some functions can be changed or have different behavior in different SW versions.
Always check the Global guide and New feature list for SW version which is used in controller. This manual
only describes the product and is not guaranteed to be set for your application.
IMPORTANT: Be aware that the binary outputs can change state during and after software
reprogramming (before the controller is used again ensure that the proper configuration and
setpoint settings are set in the controller).
The following instructions are for qualified personnel only. To avoid personal injury do not perform any action not
specified in related guides for product.
Active current
Mains
sensor Current measuring
Passive current
Battery
Current measuring sensor
Bo Pick - up
Diode
Breaker Resistor
Fuel solenoid
Switch - manually
Capacitor Generator
operated
schematic
Transformer
Coil
Grounding
Transformer with 2
Connector - male windings
IG-AVRi
2.1.2 PC Tools
There are several tools that are used for the configuration and monitoring of InteliDrive BaseBox controllers.
These tools are listed below with brief description. If you need more information on them you can use their built-
in help.
InteliMonitor
WebSupervisor
Web-based system for monitoring and controlling ComAp controllers. See more at the WebSupervisor mobile
web-page.
IGS-LOG
You can get more information on wiring of standard extension modules in the chapter Extensional modules
(page 575).
6 back to System overview
Image 3.3 Panel door mounting – Image 3.4 Panel door mounting –
InteliVision 5 InteliVision 8
Left to right: Pull down Bias / 120 Ω / Pull up Bias / 120 Ω / 120 Ω
AOUT setting
Down: AI3 setting / AI2 setting / AI1 setting
SG OUT setting
Boot jumper (upper one, rest of the jumpers is for
internal use only)
InteliVision 5 connections
Connection to InteliDrive BaseBox
1When more devices connected to RS485 bias resistor jumpers should be closed only on one of them.
Tightening torque, allowable wire size and type, for the Field-Wiring Terminals:
For controller field wiring terminals
3.5.2 Grounding
2
The shortest possible piece of wire should be used for controller grounding. Use cable min. 2.5 mm . A brass
M4 x 10 screw with star washer securing ring type grounding terminal shall be used.
The negative “-” battery terminal must be properly grounded.
Switchboard and engine must be grounded at a common point. Use as short a cable as possible to the
grounding point.
For more extension units use separate fusing according to the table above.
Controller power supply should never be connected to starter terminals.
For the connections with 12 VDC power supply an I-LBA module can be connected to controller power terminals
in order to allow the controller to continue operation during cranking if the battery voltage dip occurs. I-LBA
module can not be connected on +PWR BOUT outputs on the controller, because their consumption would
exhaust I-LBA capacitors very fast.
Low side or High side function of binary outputs can be chosen in configuration tool GenConfig in Modules tab.
This configuration is used for all binary inputs available on the controller.
Every group of outputs (i.e. 1..8 and 9..16 or 1..6 and 7..12) can provide steady current of up to 2A. Every single
binary output can provide up to 0.5A of steady current unless the total current of group of outputs does not
exceed 2A.
IMPORTANT: Both “+” and “-“ terminals (power supply for lower part of the controller and for
higher part) on the controller need to be connected at all times to ensure the proper function of
Binary Ouptuts 9 to 12(16).
IMPORTANT: Never use DC relays without protection diodes. Use protection diodes at all relays in
the switchboard even if they are not connected directly to controller Binary outputs.
A Binary inputs Common terminal is connected to Binary inputs common terminal is connected to negative
positive supply terminal, Binary inputs contacts are supply terminal, Binary inputs contacts are closed to
closed to negative supply terminals. positive supply terminals.
Input voltage range for opened contact is from 8 VDC to Power supply VDC. Input voltage range for closed
contact is from 0 to 2 VDC. Voltage level is defined between Binary input and Binary input COM terminal and
does not depend on “positive” or “negative” connection.
Image 3.14 Resistive sensor on Analog Image 3.15 Resistive sensor with grounding
input 3 on Analog input 3.
Image 3.16 Active Current sensor on Analog Image 3.17 Passive Current sensor on
input 2 Analog input 3
Status Tx Rx
Communication is OK Fast flashing - data transfer
Note: See the website www.can-cia.org for information about the CAN bus, specifications, etc.
Wiring examples
1. For shorter distances (all network components within one room) – picture 1
interconnect A and B; shielding connect to PE on controller side
2. For longer distances (connection between rooms within one building) – picture 2
interconnect A, B, COM; shielding connect to PE at one point
3. In case of surge hazard (connection out of building in case of storm etc.) – picture 3
We recommend using the following protections:
Phoenix Contact (www.phoenixcontact.com): PT 5-HF-5DC-ST with PT2x2-BE (base element)(or MT-
RS485-TTL)
Saltek (www.saltek.cz): DM-006/2 R DJ
Recommended data cables: BELDEN (www.belden.com)
1. For shorter distances: 3105A Paired – EIA Industrial RS-485 PLTC/CM (1x2 conductors)
2. For shorter distances: 3105A Paired – EIA Industrial RS-485 PLTC/CM (1x2 conductors)
3. In case of surge hazard: 3106A Paired – EIA Industrial RS-485 PLTC/CM (1x2+1 conductors)
Image 3.23 CAN wiring – longer distances (connection between rooms within one building)
Image 3.24 CAN wiring - surge hazard (connection out of the building in case of storm etc.)
4.1.1 InteliVision 5
Front panel elements 37
Page Structure 38
Connection 41
Alarms 41
Setpoint Change 44
Entering the password 45
Numeric Setpoint change 47
String Selection 47
String edit 48
Time and Date Edit 49
Combined Setpoints 49
History 50
Display Contrast Adjustment 50
Languages 51
Controller Information Screen 52
LED Indication
Position Button Description
Direct Buttons
Position Button Description
Up button. Use this button to move up, scroll up the screens or increase a value.
Menu button. Use this button to switch to menu subpages. See Page Structure
(page 38) chapter below this table for more details.
Enter button. Use this button to enter item from the list, menu, or confirm a value.
Down button. Use this button to move down, scroll down the screens or
decrease a value.
1
History button. Use this button to call controller history screen.
Horn rest button. Use this button to deactivate the horn output without
acknowledging the alarms.
Start button. Works in MAN and SEM mode only. Press this button to initiate the
start sequence of the engine.
Page Structure
Display Screens and Pages Structure.
The displayed information is structured into "pages" and "screens".
1. The pages Metering consist of pages which display measured values, e.g. voltage, current, oil pressure,
etc,. and computed values, e.g. Controller power, statistic data, etc. Use Up and Down buttons to switch
over the pages.
2. The Setpoints screen contains all setpoints organized into groups and also a special group for entering a
password.
3. The History screen shows the history log in the order that the last record is displayed first.
Help/Others screen allows set-up languages, user access, InteliVision 5 setting and etc..
To select required item use and and press . To select required item use and and press .
Example: History: Example: Help/Others::
To select required item use and and press . To select required item use and and press .
Alarms
Alarms are structured into two levels and InteliVision 5 allows easy interpreted their meaning based on the
colour scheme. First level alarm (yellow lamp, warnings) is interpreted with yellow colour . Red colour
is used for all second level alarms (Red lamp, ShutDown,…). When an error occurs, a new alarm appears
in the AlarmList screen, exclamation mark starts blinking on the metering screens.
When a new alarm appears AlarmList screen is displayed automatically when the main/first Metering screen is
displayed. From different screen, Alarm button has to be used to display AlarmList screen.
Setpoints marked with a padlock icon are password protected. Enter password as described in the chapter
Entering the password (page 45).
Press and than use again or to choose required user. Then choose EnterPassword and press
again. Numerical value is changed by using or . Cursor position is control by context buttons.
How to log-in
Password dialog has to be open and then use right context or left context for position and for the field use
or .
Password is a five-digit number (0 - 65535). Only setpoints associated with the entered password level can be
modified. Display is locked automatically when no action is done within 15 minutes.
For setpoints change use arrows or to go to a certain setpoint (e.g. Base load) and press Enter button,
see Numeric Setpoint change on page 47.
Use left context or buttons to go to a certain position of the field and use or buttons to change the
value. Then use button to confirm new value.
If you set the value out of limit, the field will get red colour and the new value is invalid. Invalid value cannot be
confirmed.
String Selection
Use , buttons to go to a certain setpoint and press button. See picture below:
String edit
Use or to select the character and use left context or buttons to the next position and press
button.
Use or to select the character and use left context or right context buttons to the next position
and press button.
Combined Setpoints
Use or buttons to select the number, left context or right context buttons for the next position or
go Up or go Down context buttons and press button.
History page
Note: Display backlight could be switched off due to Backlight Time. For recovery any button has to be
pressed.
Languages
1. Press Menu button
Note: InteliVision 5 will reboot when the language is changed. This reboot does not affect control unit.
Lost password
Display the information screen containing the serial number and password decode number as described in the
picture bellow and send them to your local distributor.
4.1.2 InteliVision 8
Front panel elements 53
Page Structure 57
Connection 59
Alarms 60
AlarmList screen 61
Setpoint Change 62
Change of the numerical value 63
String Selection 64
String edit 64
Time and Date Edit 64
Combined Setpoints 65
Entering the password 65
History 67
Display Contrast Adjustment 67
Direct Buttons
Direct Buttons
Position Button Description
Trends button. Use this button to go to the trends screen where chosen values in
graphs/real time trends are displayed.
Note: The icon in the bottom right hand corner (see picture above) indicates possibility to use PgDn button
to see next items of the context menu.
Navigation Buttons
ESC button. Escape from any dialog window or menu (cancels an action).
Right button. Use this button to move the cursor to the right, scroll to the right
history page and etc.
Home button. Jump to Home screen. Main Metering screen is used in default
configuration.
Down button. Use this button to move down, scroll down the screens or decrease
a value.
PgDn button. Use this button to quickly go down among Metering screens or
Setpoints groups (when menu is active) or among Setpoints or History records
(when menu is not active).
Left button. Use this button to move the cursor to the left, scroll to the left history
page and etc.
Up button. Use this button to move up, scroll up the screens or increase a value.
Enter button. Use this button to confirm a value or opens a value adjustment within
setting dialogs.
Direct Buttons
Position Button Description
Fault reset button. Use this button to acknowledge alarms and deactivate the
horn output. Inactive alarms will disappear immediately and status of active
alarms will be changed to “confirmed” so they will disappear as soon as their
1
reasons dismiss.
1
Mode button. Use this button to call mode change.
HORN RESET button. Use this button to deactivate the horn output without
acknowledging the alarms.
START button. Works in MAN mode only. Press this button to initiate the start
sequence of the engine (MAN and SEM mode only).
STOP button. Works in MAN mode only. Press this button to initiate the stop
sequence of the Controller. Repeated pressing or holding the button for more than
2s will cancel current phase of stop sequence (like ramping the power down or
cooling) and next phase will continue.
LED Indication
Position Button Description
Engine indication. Engine LED indication lights only when engine is running.
Alarm indication. Alarm LED indication indicate alarms. Yellow colour for the first
level alarms and red colour for the second level alarms.
Note: LED diode blink when at least one acknowledge alarm is present in the
Alarm List.
LED diode lights when alarms were acknowledged but are still active.
Note: When you switch on InteliVision 8 display, Power LED turns on and Engine and Alarm LEDs start to blink
for a while.
Colour Display
Resolution display units are 800 × 600 pixels.
Page Structure
Display Screens and Pages Structure.
The displayed information is structured into "pages" and "screens".
1. The pages Metering consists from pages which displays measured values like voltages, current, oil
pressure etc., computed values like i.e. Controller power, statistic data and etc.. Use arrows Up and Down
Alarms
Alarms are structured into two levels and InteliVision 8 allows easy interpreted their meaning based on the
colour scheme. When an error occurs, a new alarm appears in the AlarmList screen (page 61), exclamation
mark starts blinking on the metering screens. When all alarms are acknowledged, the exclamation stops
blinking and is on.
Note: When a new alarm appears AlarmList screen (page 61) is displayed automatically when the main/first
Metering screen is displayed. From different screen, AlarmList button (see Direct Buttons on page 54) has to
be used to display AlarmList screen (page 61).
AlarmList screen
Setpoint Change
On Setpoints screens you can set various setpoints. To go to Setpoints screen press Setpoints button (see
Direct Buttons on page 54). Setpoints screen appears with the context sensitive buttons for the the setpoints
group.
Note: Content of the context buttons list depends on the type of the application. To get more familiar with
setpoints go to the chapter List of setpoints (page 199) or use context help in GenConfig and InteliMonitor
(press F1 while a setpoint is highlighted).
String edit
The characters set table appears on the screen when string will be edited (like Controller name). Use ,
and , to find the position, then press button to confirm text.
Combined Setpoints
Use Left or Right buttons to move between the cells. Use Left or Right arrow to change cursor position.
Note: Password is a five-digit number (0 - 65535). Only setpoints associated with the entered password level
can be modified.
The icons in the top right-hand corner then show you that you are logged on.
PageMode On. Use this button when the PageMode is ON you can use buttons to
jump by page right or left (quicker movement through columns). Icon at the top of the screen
indicates that PageMode is On.
When brightness dialogue is active, use + buttons or + to switch between modes, which shall be
adjusted.
System overview
General description
InteliVision 12Touch (InteliVision 12Touch OEM), industrial operator panel equipped with a 12.1" color, multi-
touch screen, is dedicated together with the main ComAp controller to visualize and control single Controller
and drive controllers in various applications.
Supported controllers
Product Description Order code
Industrial grade controller for gas Controller based CHPs and power
InteliDrive BaseBox I2GASXXBAB
generation applications
InteliDrive Mobile Electronic Controller for Off-road Vehicles and Machinery ID-MOBILE
InteliDrive BaseBox Industrial grade controller for gas engine operated applications ID1COMBBBAB
PC tools
IVProg
The InteliDrive BaseBox InteliVision 12Touch display unit is programmed by the IVProg utility. It can be started
from GenConfig PC tools or directly via menu start in Windows. The IVProg utility is included in the installation
suite for a controller and it is installed automatically. The IVProg utility can also be used for Images and Skins
upload into the InteliDrive BaseBox InteliVision 12Touch display unit. InteliDrive BaseBox InteliVision 12Touch
comes with the ComAp default Skin. There is no software available for user skin modifying. User skins must be
developed in ComAp. Skins consists of only sets of colours used in Graphical User Interface, which means,
there is no change regarding dimensions or forms if customized skin is used.
Microsoft ActiveSync (for Windows XP) or Microsoft Windows Mobile Device Center (WMDC; for Windows
Vista, Windows 7 or Windows 10) must be installed on your computer to make IVProg run.
You can download these drivers from Microsoft web page http://www.microsoft.com/. To install these drivers
properly, follow Microsoft instructions.
The IVprog utility supports 64-bit Windows Vista, Windows 7 and Windows 10.
Image Manager
The ImageManager utility is included in the GenConfig Software. The main purpose of the external pictures is to
allow users modification and build their own Metering screens and use their own pictures, schemes, block
diagrams, etc. to build an impressive view of the application in the Metering screens. The ImageManager utility
is dedicated to the external images managing and building of *.ivi packages. External images (*.ivi packages]
must also be stored in the display for correct function. If there are no External images in the display and even
you can see the external images in GenConfig (Screen Editor) nothing is displayed on the display InteliVision
12Touch.
IMPORTANT: The screen resolution of the Metering screen is 800 x 660 px. It is recommended to
not to exceed this resolution for external pictures.
Screen Editor
InteliDrive BaseBox is distributed with the default metering screens. The screens are predefined in each
configuration (archive). The User is able to modify the metering screens if necessary. The default screen
template should cover most of the applications.
The user can easily modify the screens himself by drag&drop using predefined commands and pictures in the
powerful easy to use graphical utility ScreenEditor.
Gestures
InteliVision 12Touch uses gestures for configuring, moving, scrolling, commands and other functions.
Tap
The Tap gesture is the most known gesture. The gesture is defined as click on the touch area. It is a
standard gesture which can be used for click on the buttons, areas, cells, etc.
Press and hold
The Press and hold gesture is defined by attaching finger into the touch area and releasing of the finger
after time period. The period is stored in firmware and is not user defined. This gesture can be used e.g.
for deleting long number in the GUI dialogs.
Dialogs
Values, parameters and other names can be stored in the controller via dialogs. There are several dialogs in the
GUI. Dialogs for numbers, texts and lists. Available dialogs are described in the concrete chapters of this
manual.
Pages
There are several screens called pages in the GUI, which are accessible by buttons in the bottom status bar.
The actual GUI consists of 6 different pages : Trends, History, Alarmlist, Metering Screens, Setpoints and
Administration. Each page has a different function and different structure. The description of the concrete pages
is in special chapters in this manual.
Screens
Each type of controller has special set of screens stored in the configuration inside the controller. The
description of the each screens (metering) is defined by the user via powerful easy to use ScreenEditor in
GenConfig PC Tool. Scrolling between the screens is performed using the pan/flick gesture.
Special screens
There are 2 special screens defined inside the set of screens : status screen, service screen and bottom status
bar.
1. Home button - using the tap gesture on the Home button The return to Home screen is executed. Home
button is available in entire Graphical User Interface.
2. Page title - each page and each metering screen has its own title. The first number in square brackets
describes the actual metering screen position. The second number describes the total available number of
metering screens.
3. Access Lock - if the access lock function in the controller is active the display is locked for security
reasons. The icon is not the button, it only provides information about the actual state.
4. Communication error - the icon is displayed if any communication error appears. The icon is grey if the
communication error has appeared sometime in the past but the communication was automatically
reestablished. The icon is inactive if there is no communication error from the last display power up or
touching connect button in the administration. The icon is not the button, it only provides information about
the actual state.
5. USB Stick - the icon is active (lights green) if the USB stick is plugged in the display unit. Icon is inactive if
there is no USB stick plugged in. The icon is not button, it provides only information about actual state.
6. Trending - the icon is active (lights green) when the trending is running. Icon is inactive when the trending is
stopped. The icon is not button, it provides only information about actual state.
7. Alarm indication - if any alarm (Shut Down or Warning) appears the icon will start flashing red. Using the
tap gesture on this button the jump to the alarmlist page is executed.
Metering screens
Metering screens are dedicated for important controller values and setpoints. When the display is connected to
the controller screen configuration is downloaded into the display. The concrete template of the screens
depends on the type of controller. After the configuration is downloaded specific meters, values and setpoints
are displayed on the metering screens.
Trends settings
1. Channel color - there is the possibility to change the trend line colour, 16 colours are available. The colour
dialog appears when the simple Tap gesture is called.
2. Channel value - the value menu appears if the gesture tap in the cell in the value collumn is called. Inside
the value menu the user is able to choose the requested channel value. The value availibility depends on the
type of configuration stored in the controller.
3. Trends channel visibility - the checkboxes in the column Visible ensure the visbility of the trends lines. If
the channel is configured and the checkbox Visible is not checked the trend line will not be visible but will be
logged in the internal memory or a USB stick. The user is able to switch on/off the visibility independently for
each channel.
4. Y-axis visibility - checkboxes in the column Y-axis ensure the visbility of the Y-Axis labels. It is
recommended to display a few mandatory Y-Axis labels to have a good overview of the main trend window
with trend lines.
5. Low limit value - the low limit column is intended for changing the low border of the value range. For the
best view of the displayed trends it is highly recommended to set this limit to the minimum expected value
with some reserve.
6. High limit value - the high limit column is intended for changing the low border of the value range. For the
best view of the displayed trends it is highly recommneded to set this limit to the minimum expected value
with some reserve.
7. Quick channel removal - clicking on the trash bin icon the actual channel is not configured.
8. Binary value options - calling this dialog using tap gesture in the cell with the binaries allows the user to
see only the requested bits in the binary value. Note in total 32 bits can be displayed in the background of the
trend window.
History
The history page displays the records of the important moments in the controller history.
There are 3 types of history records :
Event records - are also known as standard history records. This type of record appears in case the
controller event has been made. The time stamp history also belongs in the event history. The time record is
stored for a specified period of time.
System records - are also known as text history record. These type of records are generated during the user
login/off or controller programming.
Premortem record - is visually a different block of records generated just before the shutdown alarm
1. Fixed columns - has a different shade of colour. Fixed columns are always merged and anchored on the left
side of the history page. Anchored columns can be adjusted using button column settings (point 7.)
2. Event history record - this type of record appears in case the controller event has been made.The time
stamp history also belongs in the event history. The time record is stored for a specified period of time.
3. Premortem history record - is visually a different block of records generated just before the shutdown
alarm.
4. Jump to first column button - the jump to the first column is performed if the button is pressed.
5. Jump to last column button - the jump to the last column is performed if the button is pressed.
6. Filter row button - the dialog Filter Row appears if this button is pressed. Displaying / hiding of the
specified type of the records can be adjusted using this dialog (See chapter Row Filter for more information).
7. Column settings button - the dialog column settings appears If this button is pressed. Anchor, visibility
and movement of the columns can be adjusted (see chapter Column settings)
8. History settings button - by pressing this button the settings button is hidden or displayed.
9. History page button - by pressing this button from the entire GUI displays the History page.
1. Reason area filter - by pressing the reason area the string dialog appears. Then user writes the requested
text filter. The reason history checkbox MUST be checked to filter the rows using the inserted text. If the
checkbox is not checked the inserted text will not be included.
2. Event history checkbox - if the checkbox is checked the event history is displayed.
3. Premortem history checkbox - if the checkbox is checked The Premortem history is displayed.
4. System history checkbox - if the checkbox is checked the system history is shown.
5. Reason history checkbox - if the checkbox is checked the reason history area is taken to the account and
The records are filtered based on the inserted text.
6. Acknowledgment buttons - ensure the choice confirmation. Until the button Accept is not pressed the
setting is not validated. The cancel button deletes all the setting actually made by user.
1. Anchor columns - if the checkbox in the concrete position is checked the column is anchored to the last
anchored position. If the checkbox is unchecked the column is released to the first released position.
2. Columns visibility - the visibility checkbox is intended for displaying /hiding the requested columns. The
visibility has no other function. The anchored or released columns can be visible or not.
3. Moving arrows - the arrow buttons move the selected column up and down.
4. Acknowledgment buttons - ensure the choice confirmation. Until the button Accept is not pressed the
setting is not validated. The Cancel button deletes all the setting actually made by user.
Alarmlist
The alarmlist page is intended for displaying the controller alarms. If any of the following type of the controller
alarm occurs The alarmlist page is displayed and also the alarm button in the Top status bar starts flashing
RED, even if it is not the shutdown alarm. The Automatic jump to the Alarmlist page is performed only in case
the actual GUI position is the Home metering screen. The alarm button in the top status bar is informative icon
where the display unit informs the user that there is any alarm stored in the controller unit. Pressing the button
opens the alarmlist page. The alarmlist page is displayed until the alarmlist contains the not confirmed alarms.
There are 4 different types of controller alarms :
Warning (often also known as 1st level alarm) - represented by the YELLOW colour. These types of
alarms inform the user that something is wrong and need to be checked and confirmed.
Shutdown (often also known as 2nd level alarm) - represented by the RED colour. These types of
alarms protects the Engine during the wrong state.
ECU alarm - represented by the BLUE colour. This type of alarm comes from the ECU units.
Sensor fail alarm - represented by the WHITE colour. A special kind of alarm that appears if any connected
sensor emits the wrong state.
For more information about alarm types see Alarms types on page 104.
ECU Alarmlist
InteliDrive controllers (compared to the InteliDrive BaseBox, InteliGen and InteliSys based controller) have
visually separated pages for common alarms and alarms coming from the ECU. It means that ECU alarms are
displayed on the special ECU Alarmlist page.
The ECU Alarmlist page is accessible by pressing the ECU Alarm button on the Alarmlist page in the section
Alarm control.
Setpoints
The setpoint page is intended for setting the controller values. Each type of controller has specific setpoints to
be set. The setpoints also depend on the type of application like SPtM, SPI, MINT, COMBI, COX (see the
concrete manual of the requested controller for available setpoints to be set).
1. Setpoints group - the informative column setpoint group displays the available groups based on the
controller and application type.
2. Setpoint name - each setpoint group contains specific setpoints. The informative column Setpoint name
displays the available set of setpoints to be set in each Setpoint group. Pressing the item in the concrete row
marks the entire row.
3. Actual value - by pressing the concrete cell in this column will display the specific dialog. There are several
types of dialogs (alpanumeric, numeric, stringlist) and the type of dialog depends on the setpoint type.
4. Information - by pressing the concrete item in the column the setpoint name marks the chosen row and
there is also more detailed information displayed in the Information panel, like units, limits, available
stringlist values, information about a locked setpoint, etc.
5. Setpoint Description - the special panel is intended for user adjustable hint (help). See the chapter user
editable help for setpoints.
6. Setpoints button - by pressing this button from the entire GUI displays of the Setpoints page.
Administration
Note: The Administration - Users & Passwords page style is automatically selected based on the connected
controller.
1. Connection type - by pressing the cell area the list of possible interfaces is displayed.
2. Controller address - by pressing the cell area the list of possible controller addresses is displayed.
3. Connect button - after interface and controller settings are made the connect button must be pressed to
establish a connection between the display unit and controller
IMPORTANT: The terminal addresses affect entire CAN bus line. It means that there are maximum
5 free terminal addresses on each CAN Bus line.
IMPORTANT: Only network experienced person should set and perform the ethernet connection
settings !!! All the ethernet parameters must be correctly inserted, otherwise the connection
between the InteliVision 12Touch and the controller will not be established.
1. Connection type - by pressing the cell area the list of possible interfaces is displayed.
2. Controller IP address - by pressing the cell area the dialog for the controller IP addresses insert is
displayed. The Controller IP address can be found and set via the controller setpoints. The controller IP
address is the address where the InteliVision 12Touch will be trying to connect. Be sure there is no address
collision.
3. Controller Autodetection - by pressing the button the autodetection function is performed. The table of the
available controllers is displayed. If there is no controller detected the message "No device found." is
displayed. BE SURE that connect button was pressed before the autodetect button, because the connect
button causes the saving of the IP setttings to the Windows CE system. Only controllers on the same
network as InteliVision 12Touch will be found.
4. Controller IP port - by pressing the cell area the dialog for the controller IP port insert is displayed. The
Controller IP port can be found and set via the controller setpoints. The controller IP port is the port where the
InteliVision 12Touch will be trying to connect. IP port must be the same for InteliVision and controller.
5. Controller address - by pressing the cell area the dialog for the controller addresses is displayed. The
Controller address can be found and set via the controller setpoints. The controller address is the address
where the InteliVision 12Touch will be trying to connect. Be sure the right controller address is selected.
6. Controller access code - by pressing the cell area the dialog for the controller access code insert is
displayed. Because of security reasons the access code must be always inserted when the connection
parameters has been changed or the InteliVision 12Touch has been restarted. The access code need not to
be inserted when the communication is lost and automatically reestablished for some reason
(communication interruption, temporary interference, etc.)
IMPORTANT: Before the first usage of the InteliVision 12Touch 1.4.0 with fixed IP connection
option the Connect button must be pressed before attempt for controller autodetection. This is
because the IP address, SubNet mask settings must be validated by the InteliVision 12Touch
operating system.
IMPORTANT: Ethernet interface on the InteliVision 12Touch does not support the connection to the
controllers via InternetBridge-NT.
IMPORTANT: It is expected the ethernet channel security is solved by the end customer (user)
network infrastructure. It means the ethernet channel encryption is fully under end customer (user)
responsibility. The InteliVision 12Touch ethernet interface is not dedicated and recommended for
remote connection (usage over the internet). The InteliVision 12Touch ethernet interface is
dedicated for local ethernet networks.
1. Language settings - the list of languages stored in the controller configuration is displayed in the list of
possible languages. In case there is another language in the controller configuration the GUI system English
language is set by default. The GUI can be translated to the following GUI languages only :
English
German
Chinese
Spanish
Czech
Arabian
Russian
Korean
Note: The GUI languages does not mean the languages in the controller configuration.
Note: InteliVision 12Touchcan show common code pages (437, 708, 720, 737, 775, 850, 852, 855, 857, 858,
860, 861, 862, 863, 864, 865, 866, 869, 874, 932, 936, 949, 1250, 1251, 1252, 1253, 1254, 1255, 1256, 1257,
1258, 20127, 20261, 20269, 20866, 21027, 21866, 28591, 28592, 28593,28594, 28595, 28596, 28597, 28598,
28599,28603, 28605, 29001).
1. InteliVision 12Touch details - the list of information about the display unit (SW version, HW version,
Branch, Release date, etc.)
InteliVision Settings
IMPORTANT: It is strongly recommended to use Backlight Time (timer) set on the reasonable
amount of time (approximately 30 minutes) during the normal running engine phase. It is because
of saving lifetime of the display unit. The display unit is still running if the backlight is off. For
switching on the LCD backlight the simple gesture tap is necessary.
1. Import function - by pressing the concrete button activates the dialog for import.
a. Trends - for importing the trends values from the existing file. The only *.trd file is supported for import.
b. Logo - the user is able to replace the ComAp logo (ComAp eyes) for his own logo. The supported file
type is *.png. The logo will be resized to the size of the display (1280 x 800).
c. Firmware - the firmware can be upgrade using *.ivp file provided by ComAp. The firmware must be
saved in the specific directory on a USB stick (see the Important note below)
d. Image pack - the desired images can be imported to the display unit. The images must be stored as
*.ivi package (use ImageManager - part of GenConfig to create an *.ivi package file)
e. Clone - the clone is the complete copy of the entire InteliDrive BaseBox InteliVision 12Touch unit. The
display unit expects *.ivc file to import the clone of the display unit.
f. Settings - the *.ivs file is expected for import function. The *.ivs file contains a brightness setting,
history settings, chosen language, trends channel settings, trends settings.
g. Skin - the *.ivk file is expected for the import function. The *.ivk file contains the custom or default skin.
By default only the ComAp skin exists, for more information about custom skin contact ComAp.
h. Hint - *.qm binary file with the custom setpoint hints is expected. For more information on how to create
the custom hint (help) in the Setpoint page see chapter Extended functions.
2. Export function - by pressing the concrete button activates the dialog for export.
a. Trends - for exporting the trends values from the existing file. The *.trd (ComAp proprietary format) and
*.csv (coma separated format, e.g. csv) files are supported (in the Trends settings). Here in the
administration panel only the *.csv file is supported.
b. Logo - the user is able to save the actual logo (ComAp eyes) on a USB Stick. The USB stick must be
plugged in. The logo will be saved as logo.png to the specific directory on a USB stick.
c. Firmware - the actual firmware can be saved to the *.ivp file as a backup. The firmware will be stored in
the specific directory on a USB stick (see the Important note below)
IMPORTANT: Requested files to be imported must be saved in the specific directory on a USB
Stick. The directories are created once the USB stick is inserted in the display unit.
The service screen is a special screen which can be adjusted using the powerful easy to use Screen Editor in
GenConfig PC Tool. By default the service screen is predefined by general information.
6 back to Graphical User Interface
Industrial grade controller for gas Controller based CHPs and power
InteliDrive BaseBox I2GASXXBAB
generation applications
InteliDrive Mobile Electronic Controller for Off-road Vehicles and Machinery ID-MOBILE
InteliDrive BaseBox Industrial grade controller for gas engine operated applications ID1COMBBBAB
Controller Type (min version) RS-485 (1) RS-485 (2) CAN2 Ethernet
InteliSys GAS YES YES YES NO
InteliSys NTC BaseBox (3.7.0) YES YES YES NO
InteliGen NTC Basebox (3.7.0) YES YES YES NO
IntelIGen NT BaseBox (3.7.0) YES NO YES NO
InteliMains NTC BaseBox (3.5.0) NO YES YES NO
InteliMains NT BaseBox (3.5.0) NO NO YES NO
InteliSys NTC Hybrid (2.0.0) NO YES YES NO
InteliDrive DCU Marine (3.0.0) NO YES YES NO
InteliGen GSC YES NO YES NO
InteliGen GSC-C YES YES YES NO
InteliSys GSC-C YES YES YES NO
InteliDrive Mobile YES YES YES NO
InteliDrive BaseBox YES YES YES NO
The table above shows the controller interfaces which are supported and can be used for connection with
InteliVision 12Touch.
IMPORTANT: CAN interface on the InteliVision 12Touch is supported from the version
InteliVision 12Touch 1.3.1
Auto detection or passive detection is not available on the RS-485 interface on the InteliVision 12Touch. The
passive detection is partially supoprted on the CAN interface.
To connect or change connection settings use the Administration Menu - Connection.
1. Connect the ComAp controller to the display using the standard twisted pair cable (2 wires).
2. Check the wires are connected correctly (A,B terminals).
3. Choose the connection type (RS-485 or CAN)
4. Choose the correct controller address.
5. Choose the correct terminal address (for CAN interface only).
6. Press the Connect button.
If the cabling and settings are right, the display unit InteliVision 12Touch will start to download the configuration
from the controller to the display.
Note: If the display does not start with the downloading of the configuration from the controller try to check the
wiring of RS-485 cables, check if the correct interface is selected, check the termination resistors on both ends,
check the right controller address, check if the free terminal address is selected.
Note: The controller setpoint RS485(1)conv. in the group comms must be set as ENABLED if the controller is
supposed to be connected to the display unit via RS-485 (1) port. The setpoint RS485(1)conv is present in the
specific controller firmware.
IMPORTANT: InteliDrive BaseBox supports only the newest controller archives (InteliVision
12Touch templates included) !!!
IMPORTANT: If the communication between InteliDrive BaseBox and the controller is lost for some
reason the display will try to re-establish communication twice, then the communication error
appears and limited GUI is displayed. Check for possible faults (see note in this chapter), otherwise
please contact your local technical support for help.
Note: The only logged administrator is able to reset the password to other users.
IMPORTANT: Locked setpoints can not be changed. The user must be logged in to change the
locked setpoints.
Important values
The important controllers values and system buttons are displayed by default and accessible from the Home
and Synchrol metering screens. The breaker status, controller status and system timer are displayed on the
bottom status bar. The statistic and all the system buttons are also displayed on the Status screen which is
accessible from the top status bar and very right button (status screen button).
Note: Metering screens and bottom status bar are user adjustable using the powerful easy to use Screen Editor
in GenConfig or DriveConfig PC Tool.
Setpoints setting
The setpoints can be changed using the page Setpoints. There is also a instrument (meter) called the
FastSetpointEdit, which is used for quick setpoint setting directly on a metering screen.
For more information about setpoints see Setpoints on page 84.
Note: The out of range setpoint image is displayed as a red field in the cell with the value. There is also a red dot
in the top right hand corner of the concrete group.
IMPORTANT: Each user can change only his own password. The only administrator can RESET
the password to other users.
Backlight Time - can be set at a range of 1 to 254 minutes. The backlight time can also be switched off, which
means the backlight never shuts down.
Skin Control
Alarms types
All the alarms generated by the connected controller are collected in the Alarmlist page.
There are 4 different types of controller alarms :
Warning (often also known as 1st level alarm) - represented by the YELLOW colour. These types of
alarms inform the user that something is wrong and needs to be checked and confirmed.
Shutdown (often also known as 2nd level alarm) - represented by the RED colour. These types of
alarms protects the Controller or Engine against the wrong status.
ECU alarm - represented by the BLUE colour. This type of alarm comes from the ECU units.
Sensor fail alarm - represented by the WHITE color. A special kind of alarm which appears if any
connected sensor emits the wrong status.
For more information about the alarmlist see Alarmlist on page 82.
Note: If the Alarmlist exceeds 8 items the heights of the rows are automatically lowered to display 16 alarms.
Communication issues
If a communication error occurs, the red stripe at the top and bottom of any screen appears, the minimal GUI is
also displayed. When a communication error relating to the change of a controller address occurs, follow the
instructions in the chapter Connection to the controller.
When the cause of the problem is removed the communication error disappears, but the gray inactive icon of
lost communication in the top status bar stays visible until the next restart.
Custom configuration
Custom logo
There is a possibility to change the starting logo (ComAp eyes).
OFF mode
No start of the engine is possible. Outputs STARTER (PAGE 555), CLUTCH CONNECT (PAGE 503) and FUEL
SOLENOID (PAGE 510) are not energized.
No reaction if buttons START,STOP,CLUTCH ON/OFF are pressed.
RUN mode
1. To start the engine press START.
2. When the generator voltage is within limits (adjusted in the setpoints group Generator protections) GCB
green LED on the front panel lights.
3. Press CLUTCH I/O to close the clutch. If the engine speed is out of the limits, controller does not respond to
the CLUTCH I/O.
4. To stop the engine press STOP
a. controller unloads the engine, opens CLUTCH CONNECT (PAGE 503).
b. Engine is cooled down and stopped.
Controller does not respond to external signals and/or conditions. The engine is fully in manual control; there is
no automatic way to stop it (except protections). The engine stays running until STOP button is pressed.
RS232
It is possible to connect to the controller using RS232 direct connection (serial port or USB to RS232 converter
may be used). The following settings need to be checked in the controller:
USB
You may connect to the controller using the USB port. In this case standard USB A to B cable should be used.
The following settings need to be checked:
Contr. address (page 217) has to be set to the same value as in the PC tool.
Direct connection
When you use direct connection the controller needs to be reachable directly from the PC you use (i.e. one LAN
or WAN without any firewalls and other points that may not allow the connection). The following settings need to
be checked in the controller:
Contr. address (page 217) has to be set to the same value as in the PC tool
IP Addr mode (page 225) can be set to AUTOMATIC when there is DHCP service is available. Otherwise
it needs to be set to FIXED
IP address (page 226) - IP address is either set automatically or it can be adjusted to a specific requested
value
Net mask (page 226) - Network mask is either set automatically or it can be adjusted to a specific
requested value
Gateway IP (page 227) - IP of a gateway can be set by this Setpoint when it is used
ComApProtoPort (page 227) - ComAp protocol port number is 23. Make sure that this port is open for
communication in your network
Note: For more information on how user management (access rights, access codes and passwords) works in
ComAp controller please visit the chapter User management (page 176).
Airgate connection
You can use ComAp's AirGate service that allows you to connect to any controller via Internet no matter what
are the restrictions of the local network (if the controller can connect to the Internet AirGate service will work).
The following setpoints have to be adjusted:
Contr. address (page 217) has to be set to the same value as in the PC tool
IP Addr mode (page 225) - can be set to AUTOMATIC when there is DHCP service is available.
Otherwise it needs to be set to FIXED
IP address (page 226) - IP address is either set automatically or it can be adjusted to a specific requested
value
Net mask (page 226) - Network mask is either set automatically or it can be adjusted to a specific
requested value
More details about features and setting can you find related reference guides or datasheet presented on the
websites WebSupervisor.
Note: For controller monitoring via IB-NT use firmware version 2.4.0 or higher. In case of using lower version
will not work monitoring via web browser.
This installation package will automatically unpack all files to their right location. The default location of these
file in Windows 7 and higher is the following:
For firmware: C:\Users\Public\Documents\ComAp PC Suite\GenConfig\App
For archives: C:\Users\Public\Documents\ComAp PC Suite\GenConfig\Archives
The controller can be uploaded with different versions of the firmware. These can be updates of existing
firmware or they can be different branches of the firmware with different supported functions.
First firmware needs to be uploaded to the controller. It has file extension .mhx. Then archive is uploaded.
Archives contain certain applications that are supported by the controller.
Firmware upload
GenConfig is used to upload the firmware in the controller. You can adjust the connection in GenConfig
according to the chapter Controller connections (page 109).
Once you have adjusted the correct connection, you can select Firmware upgrade (default configuration) from
menu File->Firmware upgrade and Cloning...->Firmware upgrade (default configuration).
The following dialog window will appear:
IMPORTANT: If the controller is not responding GenConfig will automatically initiate upload using
boot jumper. To get more details on this procedure go to the chapter Troubleshooting (page 186)
Once the controller finishes firmware upload it will let you know that everything went correctly by the following
dialog window.
Archive
Once the controller is uploaded with the firmware it can be uploaded with a variety of archives that provide you
with different application options. To look at the available application overview please go to the chapter
Applications overview (page 1).
The archive is uploaded using GenConfig. You can either download and archive from the controller, change its
configuration and then re-upload it again or you can open offline archive, modify (or not) the configuration and
upload it to the controller.
To download the archive from a controller adjust the correct connection settings and then click the Read from
controller icon.
The following dialog will let you know that the download is underway:
Once it is done the archive will open in GenConfig. You will see mostly the same thing as if opening the archive
offline. To open a archive offline click on the Open icon.
The following dialog will let you know that the upload is under way.
After it is done GenConfig will ask you whether you want to rewrite setpoint values and then the controller will be
ready with new configuration (when no setpoint change this dialog is skipped).
4.3 Functions
4.3.1 Modes overview 126
4.3.2 AFR 127
4.3.3 Gas Valve Test 135
4.3.4 Engine control 136
4.3.5 Controller redundancy 142
4.3.6 Service timers 143
4.3.7 Force value 145
OFF mode
No start of the engine is possible. Outputs STARTER (PAGE 555), CLUTCH CONNECT (PAGE 503) and FUEL
SOLENOID (PAGE 510) are not energized.
No reaction if buttons START,STOP,CLUTCH ON/OFF are pressed.
RUN mode
1. To start the engine press START.
2. When the generator voltage is within limits (adjusted in the setpoints group Generator protections) GCB
green LED on the front panel lights.
4.3.2 AFR
AFR control functionality is dedicated for gas engines only.
AFR - Overview
AFR - configuration
AFR functionality can be added as virtual extension module in GenConfig card Modules.
Logical analog inputs, Logical binary inputs and Logical binary outputs are presented in configuration even if the
AFR module is not configured but the function is locked.
Dongle
AFR control functionality is locked by special Dongle.
There is dongle with order code IS-AFC-PCM available for InteliDrive BaseBox
When is the AFR module configured see AFR - configuration on page 127 and the required Dongle is not
present in controller, then will be all Values placed in AFR control group fixed at zero value and the alarm
message "Dongle incomp" will be initiated.
Second required sensor is LAI: MAT A (PAGE 430) (Manifold air temperature).
Range, dimension and resolution of these analog inputs are used as reference Values for dedicated Setpoints.
IMPORTANT: If one of these sensors is not configured or have invalid Value, the shut down is
iniciated and alarm message "AFRcontrolFLS" is displayed.
The LAI: SENSORB (PAGE 431) and MAT B (PAGE 430) are as optional used for control of second mixer.
LAI: AFR VALVEFDBA (PAGE 419) and AFR VALVEFDBB (PAGE 419) serves as indicative Value of mixer
feedback.
For better correction of mixer position due to variable gas quality can be used the LAI: ANA CH4A (PAGE 420)
resp. ANA CH4B (PAGE 420) which is connected with Setpoints MxPos40%CH4A (page 352),
MxPos60%CH4A (page 353) resp. MxPos40%CH4B (page 369), MxPos60%CH4B (page 370).
Configured
Type of
LBI LAI Alarm Description
configuration
GasAB SensorB MATB SensorA MATA
NO NO NO NO NO YES invalid
NO NO NO NO YES YES invalid
NO NO NO YES NO YES invalid
One Mixer, One Mixer using table A
NO NO NO YES YES NO
One Gas only
NO NO YES NO NO YES invalid
NO NO YES NO YES YES invalid
NO NO YES YES NO YES invalid
NO NO YES YES YES YES invalid
NO YES NO NO NO YES invalid
NO YES NO NO YES YES invalid
NO YES NO YES NO YES invalid
NO YES NO YES YES YES invalid
NO YES YES NO NO YES invalid
NO YES YES NO YES YES invalid
NO YES YES YES NO YES invalid
Two Mixers, Mixer A using table A,
NO YES YES YES YES NO
One Gas Mixer B using table B
YES NO NO NO NO YES invalid
YES NO NO NO YES YES invalid
YES NO NO YES NO YES invalid
Mixer A using table A or B
One Mixer,
YES NO NO YES YES NO based on value in LBI
Two Gases
GasAB
YES NO YES NO NO YES invalid
YES NO YES NO YES YES invalid
YES NO YES YES NO YES invalid
YES NO YES YES YES YES invalid
YES YES NO NO NO YES invalid
YES YES NO NO YES YES invalid
YES YES NO YES NO YES invalid
Another possibility how to change the position of the mixer is with gas quality analyzer, which can measure the
CH4 content in the gas and in depend on this can move the position of mixer.
Note: This feature is mostly used in situations where is very various gas quality and the solution with fixed
positions is not sufficient.
Starting position is active until the timer Idle time (page 238) is counted down and engine needs to reach the
Nominal RPM (page 203).
In that time activates the second fixed position of the mixer RunPositionA (page 340).
The third fixed position LoPwrPositionA (page 341) is active.
With correct adjustment of this Setpoint, has engine be able to start the ramping on the load.
LoPwrPositionA (page 341) is active till the Controller across the first point of Power characteristic (Power1A
(page 341)).
Note: LoPwrPositionA (page 341) is back activated by undergoing of the Power1A (page 341) Value.
Note: When the fixed positions of the mixer are active, the Value AFRSensReqA (page 415)is disabled and
shows invalid Value.
In that case will be visible Value AFRSensReqA (page 415) which is calculated Value from the characteristic
adjusted by Setpoints Sensor1A (page 342), Sensor2A (page 343), Sensor3A (page 345), Sensor4A (page
346) and Sensor5A (page 348).
If the actual sensor Value AFRSensActA (page 415) is different from the required sensor Value
AFRSensReqA (page 415) the AFR PID loop represented by Setpoints AFRvalve gain (page 329),
AFRvalve int (page 330), AFRvalve der (page 330) starts to regulate and the output from the PID control loop
is visible as Value AFRVlvRegA (page 415).
Value AFRVlvRegA (page 415) is regulated as long as the regulation reach the regulation limit position
LimPos (page 331).
The output for mixer position MIXPOSA (page 414) is sume of the Values AFRVlvOffsetA (page 414) and
AFRVlvRegA (page 415).
Example: For the first setting of the whole characteristics is used Mixer RUN mode (page 132). Operator
changes the compressor power (e.g. via Base load (page 1)) to the Value Power1A (page 341) and
watches the actual value of emissions. With manual adjusting of the mixer position reaches the required
value of emissions. In that case write the actual value of sensor and mixer to the Sensor1A (page 342) and
MixPos1A (page 342). The same will be repeated for other points of characteristic. After that can be mixer
switched to AUTOMATIC mode.
For that reason is there tolerance level of the measured Value from required Value.
If the measured Value of the sensor across the tolerance level defined by Setpoint SensorValTolA (page 351),
then starts to be counted the timer TAFROFFA (page 349), after which is set the Value AFRVlvRegA (page
415) (output from AFR PID loop) to 0 zero.
And simultaneously is counted the timer TAFRERRA (page 350). When is this time counted down, the LBO
AFR ERRA (PAGE 499) is set.
6 back to Functions
Conditions
There are several conditions that are evaluated. Based on these conditions the controller decides if the Gen-set
is successfully started, running, or if it is successfully stopped.
IMPORTANT: If the engine is stopped and any of the conditions above is not fulfilled the controller
will consider the engine to run spontaneously and it will initiate stop sequence and issue alarm
Stop fail.
Note: If some of the conditions are not configured (e.g. LBI RUNINDICATION 1 (PAGE 483) is not configured) it is
not taken into account. On the other hand RPM comparison is always considered.
Start sequence
Successful start sequences - GAS
Activation of the LBO FUEL SOLENOID (PAGE 510) can be delayed with the setpoint FuelSol offset (page 241).
This delay starts to be counted when the engine speed exceeds 30 RPM.
IMPORTANT: The Underspeed protection is activated regardless of the Setpoint Idle time (page
238) 5 seconds after reaching Starting RPM (page 233) level. To get more information on when
other protections get activated please refer to the chapter Protections and Alarm management (page
169).
Ventilation sequence
When the Fuel Solenoid is set to GAS the controller performs Preventilation and Ventilation sequences.
Ventilation
Prelubrication
When the prelubrication is activated (Prelubr time (page 235) is set to none zero value and the controller is not
in the OFF mode) the controller cycles according to the settings and periodically prelubricates the engine
(activates LBO PRELUBR PUMP (PAGE 551)). There are pauses between prelubrication that are set by the
Setpoint Prelubr pause (page 236). The prelubrication cycle start when:
The controller DC power is switched on
The controller is switched from OFF mode to other modes
The alarm Alarm Type Level 2 is reset
Alarm Not lubricated is shown when the engine is being lubricated.
Stop sequence
When the engine stops normally:
6 back to Functions
IMPORTANT: Do not use Shared Binary Inputs/Outputs for LBO CTRL HBEAT FD (PAGE 508) -> LBI
EMERG. MANUAL (PAGE 438) connection since the failed controller may not interpret it correctly.
Actual value of counters is located in Values-Statistics: Service time 1 (page 411), Service time 2 (page
412), Service time 3 (page 412), ServiceTimeSd (page 1). This Value is decremented every running hour.
When the value of first three counters reaches 0, the alarm WrnServiceT1+2 respectively WrnServiceT3 is
activated and the counter continues decrement the value next to minus values until the respective counter is
readjusted back to nonzero value.
When the ServiceTimeSd (page 1) counter reaches 0, the alarm Sd Service time is issued until the related
counter is readjusted back to nonzero value.
Note: Service timers can be renamed in the GenConfig tab Miscellaneous.
6 back to Functions
For example if we add Force value 1 (page 266) to be forced to Export limit (page 1) as value 0 (DISABLED)
by Binary Input FORCEVALUEIN 1 (PAGE 452) we can change the function of Export limit (page 1) from
ENABLED to DISABLED by activation of FORCEVALUEIN 1 (PAGE 452). It is possible to rename the setpoint to
e.g. ExportDisabled and Binary Input as well to e.g. DISABLEEXPLIM. The function will not change (only the
corresponding names).
It is possible to use several force value functions for one setpoint. If more than one forcing Binary Input is
active, the one with the highest position (lowest number in the Force value dialog) is used.
It is possible as well to use one Binary Input to force multiple setpoints (e.g. in case of complex function
change).
Note: It is possible only to force value or setpoint in other setpoint if their dimension and range are the same
(e.g. only value with dimension in hours and which is Integer 16 to a setpoint with dimension hours and which is
as well Integer 16). You may use PLC block Convert to change the dimension and range if needed.
It is possible to use up to two different External values for continuous writing from external sources. The values
are adjusted by setpoints in Force value group. Default (also initial) value may be adjusted, rate of change of
ExValueX (by Binary Inputs EXVALUEX UP and EXVALUEX DOWN) can be adjusted as well as high and low limit
of the value.
Get more information on this function in the setpoints ExValue1deflt (page 300) and ExValue2deflt (page
300).
There are two ways, how to adjust External values. One is using Binary Inputs mentioned above. Second one is
to write the value directly using e.g. Modbus. External values then may be converted using PLC block convert
and force into setpoint which is then continuously forced by the value of ExValueX.
External values are reverted back to their default (initial) value (given by corresponding setpoint) when Logical
binary input EXVALUE1RESET (PAGE 445) or EXVALUE2RESET (PAGE 446) for their reset is active (and they
change to the previous value after Binary Input deactivates). When the Binary Input is active the External value
cannot be changed by Modbus writing or by using Binary Inputs for up and down value.
Note: External values are not available for external writing when any Binary Input (up, down or reset) related to
them is active.
IMPORTANT: Note also that when the controller is reset (powered down and up again), all external
values are reverted back to their default (initial) values.
6 back to Functions
The mode of each timer channel is adjusted by an assigned setpoint. The setpoints are located int the Timer
settings group and can be adjusted via InteliMonitor and GenConfig.
1. The output TIMERACT 1-4 (PAGE 557) is configured internally in GenConfig (LBI tab) to the logical binary
inputs REMOTE TEST (PAGE 1) and TEST ON LOAD (PAGE 1).
2. The setpoint Timer settings:Timer channel 1 (page 306) is adjusted to "repeated" mode, "weekly" period,
only sundays, starting date/time next sunday at 0:00, timer duration 0:30 min.
3. The setpoint Timer settings:TimerChannel 2 is adjusted to "once" mode, starting date/time 1.5.2010 at
01:00, timer duration 3:00 hrs.
6 back to Functions
Note: Values that are displayed in green color are recomended to be placed in the fast part.
Note: If the checkbox Add modules to history automatically.. in the Modules tab is checked then all values
of a module are automatically added into the history record when the module is inserted into the configuration.
You can find more information in the estpoint Time stamp act (page 323).
Note: Please be aware that in other regions summer time adjustments may be done in different time.
You can get more information in the setpoint #SummerTimeMod (page 324).
6 back to Functions
Note: It is possible to lock User Button with password (go to tab Commands in GenConfig). User Buttons 1-5,
6-8 and 9-16 (IS controllers only) can be locked separately. It is also possible to use User Buttons in
SCADAdiagrams.
6 back to Functions
Remote Switches may be easily used to trigger logical Binary Input function and all other related functions as
normal switch on Binary Input. Module VPIO (Virtual Peripheral Inputs- Outputs) can be added to configuration
and it will copy the state of Remote Switch on virtual output to its counterpart virtual input. Refer to the figure
below for example.
6 back to Functions
The principal of how shared Binary inputs and Binary outputs work is shown below.
Note: Controller sends Shared Binary Outputs each 100ms if there are any changes in any bit position. If there
are no changes, controller sends the information with period 1s.
A protection upon module failure can be configured in GenConfig. See the schematic below.
6 back to Functions
4.3.14 Modbus
Controller supports Modbus Slave functions (an external device may write or read from a controller). Modbus
registers corresponding to objects in the controller can be exported to text form in GenConfig.
If Modbus Master function is required extension module I-CB/Modbus connected via CAN1 can be used. For
more information on how to use this module please refer to IS2GASXX Communication Guide and to I-CBEdit
manual.
User Modbus
Users can define Modbus registers from 42754 to 43009. Values, setpoints and Alarm states can be specified
for these new Modbus registers to prepare the Modbus protocol for batch reading or to standardize Modbus
protocol between FW versions or branches.
Modbus Switches
The Modbus Switches consist of two groups of Logical binary outputs in Values named ModbusSw1 (page
403) and ModbusSw2 (page 404). Both registers are available on Modbus for simple writing (using command 6
or 16). The particular bits of these registers are available as binary status for universal use in Logical binary
The LSB of ModbusSw1 (46337) corresponds to LBO “ModbusSw1”. The LSB of ModbusSw2 (46338)
corresponds to LBO “ModbusSw17”.
IMPORTANT: The Values ModbusSw1 and ModbusSw2 LSB starting from the left.
6 back to Functions
4.3.15 Sensors
Controller and/or some extension modules allow connection of sensor outputs to Analog Inputs. There is whole
variety of common sensor output characteristics prepared in configuration by default. Although if there is sensor
that is not in the list, it is possible to prepare custom characteristics (up to 16) with up to 31 definition points.
Default sensors:
PT100/°C
PT1000/°C, PT100/°F
PT1000/°F
NI1000/°C
NI1000/°F
4-20mA active (linear)
0-2400ohm (linear)
0-2.4V (linear)
Tristate
For the definition please see the chapter Analog Inputs wiring (page 30).
The configuration of a sensor for analog inputs is shown below.
Example: If engine shutdown/stop is required when Fail sensor appears, configure in GenConfig →
Inputs/Outputs -> Analog inputs → Protection → property “Active when” to Under/Over limit + Fls.
6 back to Functions
Note: Range of some setpoints and values is changed significantly when different Power Formats are
selected. Last Power Format is designed to be used in combined Power/High Voltage and Low Voltage
installations. High voltage is then interpreted in Volts (e.g. 33256V instead of 33kV). Last two Power Formats
can be used in combination on one CAN bus.
6 back to Functions
6 back to Functions
General specification
Each function output can be configured to:
another function input
any physical terminal (e.g. to controller’s physical Binary Output) - GenConfig I/O sheet
Each function limit (parameter) can be configured as:
constant limit (fix): just write requested value into the field (-32768 to +32767)
setpoint limit (customer adjustable): click on field and select one from PLC setpoint list
any value (e.g. from Analog input): click on field and select one from controller or PLC values list
All PLC function analog inputs are signed type and that is why the following analog values must not be
configured to any comparator and PID analog input:
Info: ECU DiagSource, Timer val, PasswordDecode.
Statistics: NumSuccStarts, NumUnscStarts, Service time.
All function limits and analog outputs must follow input analog value format:
e.g. input value is 0,0 to 10,0 bars, then setpoint limit is e.g. 3,2.
Any time and delay limit is in 0,1s step in the range 0,1 to 3276,7 sec.
PLC consistency check indicates incorrect PLC configuration.
Required function
Based on adjustable pressure limits controller switch the engine between RPM1 to RPM2. When Pressure
drops below Pressure ON limit engine increases from RPM1 to RPM2 and after Pressure increases above
Press OFF limit goes back to RPM1.
Configuration steps
1. Start DriveConfig and open default archive IS2GASXX-DriveBB.ant.
2. Pressure measuring: configure pressure sensor characteristic – suppose range 0 to 10,0 Bars on
IS2GASXX-DriveBB Analog input 4. Wrn and Sd protection limits should be adjusted over Pressure OFF
limit.
3. Go to PLC window and drag & drop PLC functional block Comp Hyst, double click the block.
7. Drag & drop PLC functional block Ana Switch, configure Input 1 and Input 2 as PLC setpoints and edit the
setpoint names to RPM 1 and RPM 2.
New button on PLC toolbar to access password settings and login/logout. Button has 3 different colours:
All existing passwords are entered (all PLC sheets with password are unlocked)
Any (but not all) existing passwords are entered (any, but not all PLC sheets with password
are unlocked)
No existing password is entered or no password exists (all PLC sheets with passwords are
locked)
To assign password to the PLC sheet, click on assign icon in title of PLC sheet:
IMPORTANT: Very important parts of the control algorithm must not be locked in PLC sheets.
Certification authorities may request their unlocking if necessary.
Note: Fixed protections have (usually) configurable settings but they are fixed because they cannot be
removed from the configuration completely. However they may be disabled in their settings. On the other hand
Universal (configurable) protections can be removed from the configuration completely and new protections
with individual settings may be created from scratch.
Alarm types
There are two levels of alarm. Level 1 (Yellow) does not have direct effect on the controlled system (i.e. engine
is not stopped, Circuit breaker is not opened). Level 2 (Red) has direct effect on the controlled system
There are several types of alarm for both Level 1 and Level 2 alarms. The table below gives overview of these
types.
Protection blocking
Fixed protections may be blocked based on fixed conditions (e.g. electrical protection are blocked in states
where healthy voltage is not expected - engine stopped, cranking etc.). Universal (configurable) protections may
be blocked based on the following conditions.
Example: There is an example of setting of Remote Alarm Messaging. In this case active calls we be
triggered on Mains protect and Mains protect with Reset alarms. Message is sent via email to
emailAddress@domain.com (Channel 1 – available for NTC controller or with any controller with connected
IB-NT or I-LB+), archive is sent via ISDN modem to the number +111222333444 (Channel 2) and SMS is
sent to the number +999111333555 (Channel 3).
Default protections
There are many default (fixed) protections in the controller. These protections are highly dependent on what
application is running in the controller.
Shutdown override
nd
If the Logical binary input SD OVERRIDE (PAGE 484) is closed, all 2 level protections are disabled to allow the
Gen-set run in an emergency situation, e.g. sprinkler devices power supply.
All protections are shown in Alarmlist and recorded into History, but the controller does not stop the engine
because of them. If the input is deactivated and some protections are still active or not yet reset, the controller
starts to take these protections into account and consequently stops the engine.
nd
All 2 level protections are locked out, except of these:
Emergency stop
Overspeed
Underspeed
Pressing of the fault reset button (at any terminal or external button) resets
DISABLED only inactive alarms. Active alarms remain in the alarmlist unchanged and must be reset
again when they become inactive.
Pressing of the fault reset button (at any terminal or external button) resets all alarms that
are currently present in the alarm list. Inactive alarms disappear from the alarm list
ENABLED
immediately, active alarms are changed to "confirmed" state and disappear when the alarm
condition disappear or the alarm starts to be blocked.
Note: ENABLED position corresponds to the method how the IG-classic and IS-classic controllers handled the
alarms.
Note: Select the value for protection first and then use Wizard – it will take you through all the steps and help
you adjust them correctly.
Ready Engine is ready to run, all condition for start are fulfilled
Prestart Prestart sequence in process. From closing of Prestart output to closing of Starter output
Gas engine - ventilation of unburned fuel when stop command comes during cranking with
Ventil
gas
SDVentil Gas engine - ventilation of unburned fuel after unsuccessful start attempt
6 back to Functions
Entering password
If the Sites connection mode is used, then the passwords for each controller can be entered in advance into the
Controllers list (refer to the context help of InteliMonitor- press F1 in InteliMonitor). If the Quick connection mode
is used, then the passwords for the particular controller can be entered before the connection is opened.
Single connection: To enter the password while the connection is already running, go to the menu Monitor ->
Enter password or click to the icon . You also have to select the user, for whom the password is beeing
entered.
Multiple connection: To enter the password while the connection is already running, in the toolbar select the
Controller to which you want enter the password and then go to the menu Monitor -> Enter password or use the
item Enter password from the pull-down menu of the desired controller. You also have to select the user, for
whom the password is beeing entered.
Deactivating password
Click to the icon resp. or use the menu item Monitor -> Deactivate password to deactivate the
currently entered password (the current user).
Manage users
Log-in as the administrator and click to the icon or use the menu Monitor -> Admin users to open the
window where you can manage the other users of the controller.
1. Select the user that you want to edit in the list (2). The name of the user can be changed after clicking into
the name field. The name of the currently selected user is indicated in the label (3).
Note: To change user name and levels user must be enabled first in section (1).
2. Select the top access level for this user by double-clicking on the appropriate rectangle in the access level
map (4). All lower levels will be selected automatically. To select levels individually, hold the Ctrl key and
click on level field.
3. Uncheck the "Enabled" item (1) if you want to disable the selected user, i.e. the user will not have any
access level assigned.
4. You can reset password to default for all users except the administrator by clicking on the button (5) or reset
password only for the selected user by clicking on the button (6).
Note: Warning “PassInsertBlck” appears in alarm list when controller is blocked. It is not allowed to insert
the password in case that controller is blocked. There is information that controller is blocked for next
password attempt and time remaining till the end of blockation instead of password input window at the
terminal screen. The controller is locked for 5 minutes when the password is 6 times wrong entered (in case
of next 6 wrong attempts (correct password was not inserted at all) for 30, 60, 120, 240 minutes). Incorrect
password message appears in the history of the controller when the invalid password is used.
6 back to Functions
LBI Note
SafetyFunct1NO Normaly open contact. Can be configured as standard LBI. Pair 1
SafetyFunct1NC Normaly close contact. Can be configured as standard LBI. Pair 1
SafetyFunct2NO Normaly open contact. Can be configured as standard LBI. Pair 2
SafetyFunct2NC Normaly close contact. Can be configured as standard LBI. Pair 2
SafetyFunct3NO Normaly open contact. Can be configured as standard LBI. Pair 3
SafetyFunct3NC Normaly close contact. Can be configured as standard LBI. Pair 3
SafetyFunct4NO Normaly open contact. Can be configured as standard LBI. Pair 4
SafetyFunct4NC Normaly close contact. Can be configured as standard LBI. Pair 4
Mismatch evaluation delay = this delay is given by the internal structure of the function (this delay is the same
as in the case of Emergency stop mismatch evaluation).
If only one of LBIs from the pair is configured the function automatically issues alarm SafetyFnXMism (where X
is an integer according to the pair with invalid configuration).
If none of the LBIs from one pair is configured the function is not evaluated at all.
IMPORTANT: This function is not suitable for inputs from sources with longer refresh delay (e.g.
extension modules, Modbus...)
Note: The RS232/RS485 converter is included in the IG-NTC, IG-EEC and IS-NT controllers (no external
RS232/RS485 converter is needed).
Note: RS485 communication line has to be terminated by 120 ohms resistors at both ends – follow converter
user manual. RS485 communication can be used for monitoring and controlling of many controllers via
InteliMonitor.
Note: To use I-LB Modbus communication connect Modbus jumper in I-LB unit (P16). Additionally, you can
choose the communication speed using the speed selection jumpers (P13, P14). Their combination allows the
speed selection of 9600/19200/38400/57600 bps.
RS232(1) 1 IV 8
PC
Modbus terminal
Modem
RS485(1) 3 IV 8
IV 5
RS485(1) 1 IV 8
PC
Modbus terminal
Modem
RS232(2) 1 IV 8
PC
Modbus terminal
Modem
RS485(2) 1 IV 8
PC
Modbus terminal
Modem
CAN1 45 AIN (9x)
BIN (12x)
AOUT (4x)
BOUT (12x)
DENOX20 (1x)
ECON3 (1x)
ECON4 (1x)
Other specialized HW
CAN2 35 Controllers
IV 8
I-LB+
InternetBridge-NT
USB 1 PC
Note: RS232(1) – RS485(1) can be switched and only one port at a time is available for universal
communication (it is possible to use RS485 for internal display communication while still using RS232).
IMPORTANT: CAN bus line has to be terminated by 120 ohm resistors on the both ends.
Always check the number and placement of terminating resistors in the CAN bus line, only correct wiring
ensures reliable operation! Resistors must be placed at either end of the line (see picture), and correct number of
resistors must be used! Correct number can be checked using ohmmeter - when power supply for ALL devices
on the CAN bus line (including third party, e.g. ECU) is switched off, the resistance measured between A and B
wire should be 60 Ohms.
ECU communicating over the CAN bus is connected to CAN1 port of the controller and other ComAp modules
can be connected to this CAN bus as well. For detailed description of connection of various ECUs refer to
ComAp Electronic Engines Support manual.
When internal RTC battery becomes flat, controller function (e.g. Ready for stand by) does not change until
controller power supply is switched off. Some time before the battery is completely exhausted, a warning
message appears in Alarmlist: "RTCbatteryFlat".
After the next power switch on (with flat battery already) controller:
Stays in the INIT state (not possible to run engine)
All History records disappear except of "System log: setpointCS err" record
Time and Date values are set to zero
Statistics values are random
IMPORTANT: If the RTC is not present during controller initialization the time and date is not set
up and Watchdog function will not be initialized which has influence for "Single fault tolerancy"
function. In that case is strongly recommended that change of RTC battery is provided only in
authorized services.
8.6 D+ function
Max. D+ output current 300 mA
Guaranteed level for signal Charging OK 80% of supply voltage
Following dynamic cable parameters are important especially for maximal 200 meters CAN bus
length and 32 iS-COM units connected:
Nominal Velocity of Propagation min. 75% (max. 4,4 ns/m)
Wire crosscut min.0,25 mm2
Maximal attenuation (at 1 MHz) 2 dB / 100 m
6 back to Appendix
For full list of setpoints go to the chapter List of setpoints (page 199).
6 back to Controller objects
Gear Teeth
Setpoint group Basic Settings Related FW 1.0.0
Range [units] 1..500[-]
Force
Default value 120 valueAlternative NO
config
Step 1
Comm object 8252 Related applications all
Config level Standard
Setpoint visibility Always
Description
Number of teeth on the engines flywheel for the pick-up. RPM PICK-UP (PAGE 431) is ignored when RPM
is received via J1939.
Note: Generator voltage must be higher than 10 V effective to measure the speed from the frequency
correctly. If this condition is not fulfilled at low speeds (cranking) it is recommended to use additional
running indication as e.g. D+ signal to prevent overcranking of the engine. See the binary output
STARTER (PAGE 555) for additional information.
IMPORTANT: The starting procedure of gas engine may not work without the pickup. The
pickup must be always used for gas engines.
ControllerMode
Setpoint group Basic Settings Related FW 1.0.0
Range [units] OFF, RUN [-]
Force
Default value OFF valueAlternative NO
config
Step -
Comm object 8315 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint can be used to select the controller mode. It is equivalent to selecting the mode by the
buttons on the front panel. Currently active mode is displayed on the controller main screen.
Note: If any of the mode forcing inputs REMOTE RUN (PAGE 484), REMOTE AUT/REMOTE SEM (PAGE
1) or REMOTE TEST (PAGE 1) is active, then the currenly active mode can be different than the mode
selected by the setpoint (resp. panel buttons).
Note: The binary inputs for external buttonst may be the following (depending on used application):
GCBButton, MCBButton, MGCBButton, FDRButton, BTBButton, FaultResButton, HornResButton,
StartButton, StopButton etc.
Note: In the case that more IV displays are connected they all behave the same (they are all clones of
each other).
Note: The binary inputs for external buttonst may be the following (depending on used application):
GCBButton, MCBButton, MGCBButton, FDRButton, BTBButton, FaultResButton, HornResButton,
StartButton, StopButton etc.
DispBklStrtOff
Setpoint group Basic settings Related FW 1.0.0
Range [units] DISABLED, ENABLED[-]
Force
Default value ENABLED valueAlternative YES
config
Step -
Comm object 11002 Related applications all
Config level Standard
Setpoint visibility Always
Description
If this setpoint is in ENABLED position the display backlight is temporarily switched off during Controller
start.
WatchedContr
Setpoint group Process Control Related FW 1.0.0
Range [units] OFF, 1..16[-]
Force
Default value OFF valueAlternative NO
config
Step 1
Comm object 11719 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint is used at redundant controller to specify the address of the related main controller in
Redundant systems using CAN bus (page 142). Adjust this setpoint to 0 if the controller is not used
as redundant or if it is used in Redundant systems using binary signals (page 1). Redundant
systems using CAN bus.
ConvCoefPulse2
Setpoint group Basic settings Related FW 1.0.0
Range [units] 1..6500[-]
Force
Default value 1 valueAlternative NO
config
Step 1
Comm object 10995 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the rate of increasing of the PulseCounter #2 module. The module counts pulses at
the input PULSECOUNTER 2 (PAGE 480) and if the input pulses counter reaches value given by this
setpoint, the counter value PulseCounter 2 (in the group Statistic) is increased by 1 and input pulses
counter is reset to 0. Both counter value and input pulses counter are stored in the nonvolatile memory.
ConvCoefPulse4
Setpoint group Basic settings Related FW 1.0.0
Range [units] 1..6500[-]
Force
Default value 1 valueAlternative NO
config
Step 1
Comm object 10997 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the rate of increasing of the PulseCounter #4 module. The module counts pulses at
the input PULSECOUNTER 4 (PAGE 481) and if the input pulses counter reaches value given by this
setpoint, the counter value PulseCounter 4 (in the group Statistic) is increased by 1 and input pulses
counter is reset to 0. Both counter value and input pulses counter are stored in the nonvolatile memory.
ConvCoefPulse6
Setpoint group Basic settings Related FW 1.0.0
Range [units] 1..6500[-]
Force
Default value 1 valueAlternative NO
config
Step 1
Comm object 15347 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the rate of increasing of the PulseCounter #6 module. The module counts pulses at
the input PULSECOUNTER 6 (PAGE 481) and if the input pulses counter reaches value given by this
setpoint, the counter value PulseCounter 6 (page 414) (in the group Statistic) is increased by 1 and
input pulses counter is reset to 0. Both counter value and input pulses counter are stored in the
nonvolatile memory.
ConvCoefPulse8
Setpoint group Basic settings Related FW 1.0.0
Range [units] 1..6500[-]
Force
Default value 1 valueAlternative NO
config
Step 1
Comm object 15349 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the rate of increasing of the PulseCounter #8 module. The module counts pulses at
the input PULSECOUNTER 8 (PAGE 482) and if the input pulses counter reaches value given by this
setpoint, the counter value PulseCounter 8 (page 414) (in the group Statistic) is increased by 1 and
input pulses counter is reset to 0. Both counter value and input pulses counter are stored in the
nonvolatile memory.
ImpCountDef2
Setpoint group Basic settings Related FW 1.0.0
Range [units] 0..65535[-]
Force
Default value 0 valueAlternative YES
config
Step 1
Comm object 14278 Related applications all
Config level Standard
Setpoint visibility Always
Description
By activation LBI: IMPCOUNT SET 2 (PAGE 468) will be set the actual Value PulseCounter 2 (page 413)
to Value presented by this Setpoint.
ImpCountDef4
Setpoint group Basic settings Related FW 1.0.0
Range [units] 0..65535[-]
Force
Default value 0 valueAlternative YES
config
Step 1
Comm object 14280 Related applications all
Config level Standard
Setpoint visibility Always
Description
By activation LBI: IMPCOUNT SET 4 (PAGE 468) will be set the actual Value PulseCounter 4 (page 413)
to Value presented by this Setpoint.
ImpCountDef6
Setpoint group Basic settings Related FW 1.0.0
Range [units] 0..65535[-]
Force
Default value 0 valueAlternative YES
config
Step 1
Comm object 15720 Related applications all
Config level Standard
Setpoint visibility Always
Description
By activation LBI: IMPCOUNT SET 6 (PAGE 468) will be set the actual Value PulseCounter 6 (page 414)
to Value presented by this Setpoint.
ImpCountDef8
Setpoint group Basic settings Related FW 1.0.0
Range [units] 0..65535[-]
Force
Default value 0 valueAlternative YES
config
Step 1
Comm object 15722 Related applications all
Config level Standard
Setpoint visibility Always
Description
By activation LBI: IMPCOUNT SET 8 (PAGE 469) will be set the actual Value PulseCounter 8 (page 414)
to Value presented by this Setpoint.
Contr. address
Setpoint group Comms settings Related FW 1.0.0
Range [units] 1..32[-]
Force
Default value 1 valueAlternative NO
config
Step 1
Comm object 24537 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the address of the particular controller at the CAN2, Modbus and/or RS485 bus.
Each Controller connected to the same bus must have unique address.
If the setpoint (COMBI application only) is in AUT position, the address is assigned automatically. The
setpoint Contr. address (page 217) is preffered then, however if it is in conflict with other controller
present on the CAN2 bus other address will be assigned to aviod address collision.
Note: Address 1 is reccommended for standalone Controllers.
Note: If you are connecting to the Controller remotely you have to adjust the proper controller address in
connection settings of the remote client (InteliMonitor, GenConfig, Modbus client etc.)
Note: Address of the controller is also used for Modbus communication via RS485 etc. Address
adjusted by this setpoint is therefore universal address of the controller.
Connection to a local PC via RS232 or RS485 (with internal or external converter) interface. Use
DIRECT this option also for IG-IB connected via RS232 cable. The internal RS485 converter is
enabled/disabled by the setpoint RS485(1) conv. (page 222).
Modem point-to-point connection to a remote PC with hardware data flow control using signals
MODEM (HW)
RTS/CTS. Full modem cable is required for this option.
Modem point-to-point connection to a remote PC with software data flow control. 3-wire cable
MODEM (SW) (RX, TX, GND) is sufficient for this option. Use this option only if your modem does not provide
RTS/CTS signals.
Modbus RTU connection in slave mode via RS232 or RS485 (with internal or external converter)
interface. The internal RS485 converter is enabled/disabled by the setpoint RS485(1) conv.
MODBUS
(page 222) , the communication speed is adjustable by the setpoint RS232(1)MBCSpd (page
220) . See the latest communication guide for more information about the MODBUS protocol.
Modbus RTU connection in slave mode via modem with hardware data flow control. The
MODBUS-MDM(HW) communication speed is adjustable by the setpoint RS232(1)MBCSpd (page 220). See the latest
communication guide for more information about the MODBUS protocol.
Connection to an electronic-controlled engine which uses non-J1939 ECU. The proper ECU type
ECU-LINK
must be also configured with GenConfig.
Connection to a local PC via RS232 or RS485 (with internal or external converter) interface. Use this
DIRECT option also for IG-IB connected via RS232 cable. The internal RS485 converter is enabled/disabled by
the setpoint RS485(2) conv. (the setpoint is not available in hardware version 2.0 and above).
Modem point-to-point connection to a remote PC with hardware data flow control using signals
MODEM (HW)
RTS/CTS. Full modem cable is required for this option.
Modem point-to-point connection to a remote PC with software data flow control. 3-wire cable (RX, TX,
MODEM (SW)
GND) is sufficient for this option. Use this option only if your modem does not provide RTS/CTS signals.
Modbus RTU connection in slave mode via RS232 or RS485 (with internal or external converter)
interface. The internal RS485 converter is enabled/disabled by the setpoint RS485(2) conv. (the
MODBUS setpoint is not available in hardware version 2.0 and above), the communication speed is adjustable by
the setpoint RS232(2)MBCSpd (page 220) . See the latest communication guide for more
information about the MODBUS protocol.
Modbus RTU connection in slave mode via modem with hardware data flow control. The communication
MODBUS-MDM(HW) speed is adjustable by the setpoint RS232(2)MBCSpd (page 220) . See the latest communication
guide for more information about the MODBUS protocol.
Connection to an electronic-controlled engine which uses non-J1939 ECU. The proper ECU type must
ECU-LINK
be also configured with GenConfig.
Note: The RS232(2) connector is no more available in hardware version 2.0 and above. The COM2 port
is redirected to the RS485(2) terminals all the time. That means modem is not supported at COM2 in
these hardware versions. For modem use the COM1 port instead.
RS232(2)MBCSpd
Setpoint group Comms settings Related FW 1.0.0
Range [units] 9600, 19200, 38400, 57600[bps]
Force
Default value 9600 valueAlternative NO
config
Step -
Comm object 24420 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint adjusts the communication speed on the COM2 connector when it is switched to MODBUS
or MODBUS-MDM(HW) mode. See also the setpoint RS232(2) mode (page 219).
RS232(2)MdmIni
Setpoint group Comms settings Related FW 1.0.0
Range [units] [-]
Force
Default value valueAlternative NO
config
Step -
Comm object 24449 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint can be used to add extra AT commands at the end of the initialization sequence of the
modem connected to the COM2 port. The command can be entered with as well as without the "AT"
prefix, are separated with semicolon and maximal length is 31 characters.
Using a modem at the COM2 port is not supported since the hardware version 2.0. For modem use the
COM1 port instead.
The communication port COM1 is redirected to the integrated RS485(1) converter. The RS232(1) connector
ENABLED
has no function and the external display interface is not available.
The communication port COM1 is present at the RS232(1) connector and the RS485(1) connector is used for
DISABLED
the external display interface.
Note: The redirection is applied only for DIRECT, MODBUS and ECU-LINK modes. See the setpoint
RS232(1) mode (page 218).
Note: This setpoint must be set to DISABLED at controllers that do not have internal display. i.e.
InteliVision 5 or InteliVision 8 is connected to the RS485(1) terminals to allow NT terminal
communication and connection of multiple controllers.
LB/UART Log
Setpoint group Comms settings Related FW 1.0.0
Range [units] DISABLED, ENABLED
Force
Default value DISABLED valueAlternative YES
config
Step -
Comm object 11327 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint enables/disables logging of remote communication activity. If logging is enabled connection
and disconnection of each remote terminal as well as entering access code are recorded into the history.
Note: The terminal is disconnected automatically after 5 min of inactivity and next communication
request from the same terminal is considered as a new connection. When logging is enabled in certain
conditions the history may be filled up with large number of records related to the communication and
important records may be overwritten quite fast.
CANAddrSwitch2
Setpoint group Comms settings Related FW 1.0.0
Range [units] MODEM, OTHER [-]
Force
Default value OTHER valueAlternative NO
config
Step -
Comm object 24398 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint selects function of the terminal address 125 at the CAN2 line. See the latest communication
guide for details about this topic.
IMPORTANT: If you need to use fixed ethernet settings you should consult the proper setting
with your IT specialist.
Net mask
Setpoint group Comms settings Related FW 1.0.0
Range [units] [-]
Force
Default value 255.255.255.0 valueAlternative NO
config
Step -
Comm object 24375 Related applications all
Config level Standard
Setpoint visibility Always
Description
When IP Addr mode (page 225) = FIXED, this setpoint is used to adjust the network mask of
the network segment where the controller is connected.
When IP Addr mode (page 225) = AUTOMATIC, this setpoint is used to display the network
mask which has been assigned by the DHCP server. It is not possible to change the setpoint
value manually in this setting (the value is immediately reverted back by controller communication
module IB-COM).
ComApProtoPort
Setpoint group Comms settings Related FW 1.0.0
Range [units] 1..255[-]
Force
Default value 23 valueAlternative NO
config
Step 1
Comm object 24374 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint is used to adjust the port, which is used for ethernet connection to a PC with any of ComAp
PC program (i.e. InteliMonitor, GenConfig). This setpoint should be adjusted to 23, which is the
default port used by all ComAp PC programs. A different value should be used only in special situations
as e.g. sharing one public IP address among many controllers or to overcome a firewall restrictions.
This is a standard mode, in which the controller listens to the incoming traffic and
answers the TCP/IP queries addressed to him. This mode requires the controller
DISABLED
to be accessible from the remote device (PC), i.e. it must be accessible at a
public and static IP address if you want to connect to it from the Internet.
This mode uses the "AirGate" service, which hides all the issues with
static/public address into a black box and you do not need to take care about it.
ENABLED
You just need only a connection to the Internet. The AirGate server address is
adjusted by the setpoint AirGate IP (page 228).
AirGate IP
Setpoint group Comms settings Related FW 1.0.0
Range [units] max. 32 characters[-]
Force
Default value airgate.comap.cz valueAlternative NO
config
Step -
Comm object 24364 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint is used for entering the domain name or IP address of the AirGate server. Use the free
AirGate server provided by ComAp at address airgate.comap.cz.
SMTP address
Setpoint group Comms settings Related FW 1.0.0
Range [units] max. 32 characters
Force
Default value valueAlternative NO
config
Step -
Comm object 24368 Related applications all
Config level Standard
Setpoint visibility Always
Description
IMPORTANT: Proper setting of SMTP-related setpoints as well as controller mailbox are
essential for sending alerts via emails. For more information about protections please refer
to the chapter Protections and Alarm management (page 169).
This setpoint is used for entering the domain name (e.g. smtp.yourprovider.com) or IP address (e.g.
74.125.39.109) of the SMTP server. Please ask your internet provider or IT manager for this information.
Note: You may also use one of free SMTP servers, e.g. smtp.gmail.com. However, please note that
some free SMTP servers may cause delays (in hours..) when sending e-mails.
Note: If you do not want to send active e-mails, you may leave this setpoint blank, as well as other
setpoints related to SMTP server and e-mail settings.
Time zone
Setpoint group Comms settings Related FW 1.0.0
Range [units] -[-]
Force
Default value GMT+1:00 valueAlternative NO
config
Step -
Comm object 24366 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint is used to select the time zone where the controller is located. See your computer time
zone setting (click on the time indicator located in the rightmost position of the windows task bar) if you
are not sure about your time zone.
Note: If the time zone is not selected properly the active e-mails may contain incorrect information about
sending time, which may result in confusion when the respective problem actually occurred.
ECU Diag
Setpoint group Comms settings Related FW 1.0.0
Range [units] DISABLED, ENABLED[-]
Force
Default value ENABLED valueAlternative YES
config
Step -
Comm object 10353 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint is used to disable reading of diagnostic codes from the ECU if an external diagnostic tool is
connected to the engine.
A message ECU Diag disabled is displayed in the alarm list while ECU diagnostics is disabled.
This setpoint is also used as the speed limit for the Underspeed protection, which is activated 5 seconds
after the starter was disengaged and the controller continued from Starting to Idle or Running phase.
Starting POil
Setpoint group Engine Params Related FW 1.0.0
Range [units] 0.0..10.0[bar]
Force
Default value 10 valueAlternative YES
config
Step 0.1
Comm object 9681 Related applications all
Config level Standard
Setpoint visibility Always
Description
Oil pressure can be used as one of the symptoms that are used for detection that the engine is running.
This setpoint adjusts oil pressure limit above which the engine is considered as started.
Note: Learn more in the separate chapter Start sequence (page 137).
Note: The logical analog input Oil pressure must be configured onto the appropriate analog input where
the oil pressure sensor is connected.
Prelubr time
Setpoint group Engine params Related FW 1.0.0
Range [units] 0..3600[s]
Force
Default value 0 valueAlternative YES
config
Step 1
Comm object 8780 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint is used for adjusting duration of the prelubrication cycle. See the output PRELUBR PUMP
(PAGE 551) for details about prelubrication.
MaxCrank Time
Setpoint group Engine Params Related FW 1.0.0
Range [units] 1..240[s]
Force
Default value 10 valueAlternative YES
config
Step 1
Comm object 8256 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint adjusts the maximum duration the STARTER (PAGE 555) is energized within one cranking
cycle. If there is none of running engine symptoms activated within this period the particular cranking
attempt is finished and either a CrnkFail pause (page 237) follows or start fail alarm is issued.
Note: At gas engines the last cranking cycle is extended about 25 % and the engine is cranked with
closed gas valve during this additional time to ventilate the remaining gas.
Note: If magnetic pickup is used and the controller detects zero RPM within 2 s for gas engine or 5 s for
diesel engine after energizing the starter motor then cranking pause follows immediately (as the pinion is
probably not properly engaged).
Note: Learn more in the separate chapter Start sequence (page 137).
Crank attempts
Setpoint group Engine Params Related FW 1.0.0
Range [units] 1..10[-]
Force
Default value 3 valueAlternative YES
config
Step 1
Comm object 8255 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint adjusts the maximum number of cranking cycles. The alarm Start fail is issued when the
engine does not start within this number of cranking cycles.
Note: An gas engines the last cranking cycle is extended about 25 % and the engine is cranked with
closed gas valve during this additional time to ventilate the remaining gas.
Note: Learn more in the separate chapter Start sequence (page 137).
Cooling speed
Setpoint group Engine Params Related FW 1.0.0
Range [units] IDLE, NOMINAL
Force
Default value IDLE valueAlternative YES
config
Step -
Comm object 10046 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint is used to select whether the cooling phase is performed at idle or nominal speed, i.e.
whether the output IDLE/NOMINAL (PAGE 511) is open or closed during the idle phase.
AfterCool time
Setpoint group Engine params Related FW 1.0.0
Range [units] 0..3600[s]
Force
Default value 120 valueAlternative YES
config
Step 1
Comm object 8662 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint is used to adjust the length of the aftercooling period, i.e. how long the COOLING PUMP
(PAGE 506) remains running after the Controller has been stopped.
SDVentil time
Setpoint group Engine Params Related FW 1.0.0
Range [units] 0..60[s]
Force
Default value 10 valueAlternative NO
config
Step 1
Comm object 9695 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint is used to adjust the length of the preventilation phase at gas engines, i.e. if the setpoint
Fuel Solenoid is switched to GAS ENGINE. The preventilation phase is a period of cranking without
opened gas valve which takes place prior to the first start attempt after a shutdown or after switching on
the controller.
The purpose of the preventilation phase is to clean the engine and exhaust system from possible
unburned gas.
Note: Active sprinkler function enables engine start even if the Gas valve test is negative.
Note: Active sprinkler function enables engine start even if the Gas valve test is negative.
The D+ terminal is used for running engine detection as well as for charger failure
ENABLED
alarm detection.
CHRGFAIL The D+ terminal is used for charger failure alarm detection only.
DISABLED The D+ terminal is not used.
Note: Some alternators provide a terminal labelled as "L" instead of "D+". It is not possible to connect
this "L" terminal to the "D+" terminal of the controller.
RefEngTorque
Setpoint group Engine params Related FW 1.0.0
Range [units] 0 .. 64255 [Nm]
Force value
Default value 0 YES
Alternative config
Step 1
Comm object 16546 Related applications All
Config level Standard
Setpoint visibility Always
Description
Used as a reference value for Engine Torque in relative value (percentage).
Example: The relative value is read from the ECU as a percentage (Actual Engine - Percent Torque =
SPN513, range -125 - 125%). These (and other torque values) are relative to the reference absolute
value stored in engine ECU. So-called Engine Configuration (frame EC1) contains a 2B value Engine
Reference Torque (Engine Configuration) = SPN 544, range 0 - 64255Nm).
EnLocalSpeed
Setpoint group Engine params Related FW 1.0.0
Range [units] [ENABLED, DISABLED]
Force value
Default value DISABLED YES
Alternative config
Step [-]
Comm object 10098 Related applications All
Config level Standard
Setpoint visibility Always
Description
ENABLED: Speed request (page 392) is defined by Local Speed (page 245) setpoint.
DISABLED: Speed request (page 392) is changed via SPEED UP (PAGE 490) / SPEED DOWN (PAGE 489) or
via REQUESTED RPM (PAGE 430).
Local Speed
Setpoint group Engine params Related FW 1.0.0
Range [units] 0.0 .. 100.0 [%]
Force value
Default value 0.0 YES
Alternative config
Step 0.1
Comm object 9948 Related applications All
Config level Standard
Setpoint visibility Always
Description
Setpoint specifies Speed request (page 392) when EnLocalSpeed (page 245) = ENABLED. Setpoint
can be changed as standard setpoint.
Bin selector 2
Setpoint group Engine params Related FW 1.0.0
Range [units] OFF, ON[-]
Force
Default value OFF valueAlternative YES
config
Step -
Comm object 10624 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint is used to switch on and off the output BIN SELECTOR 2 (PAGE 503).
Bin selector 3
Setpoint group Engine params Related FW 1.0.0
Range [units] OFF, ON[-]
Force
Default value OFF valueAlternative YES
config
Step -
Comm object 10625 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint is used to switch on and off the output BIN SELECTOR 3 (PAGE 503).
If you want to get more information on the alarm management in ComAp controller please refer to the
chapter Protections and Alarm management (page 169)
RunOnlyBlkDel3
Setpoint group Engine protect Related FW 1.0.0
Range [units] 0.0..3000.0[s]
Force
Default value 10 valueAlternative YES
config
Step 0.1
Comm object 10025 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the delay after engine start when the alarms configured as RunOnlyBlkDel3 (i.e.
"running only", group #3) are started to be evaluated. The "running only" alarms are not beeing evaluated
while the engine is not running or then, after start, while the adjusted delay is running.
See the setpoint RunOnlyBlkDel1 (page 248) for diagram of alarm groups and their blocking periods.
BinInp delay 2
Setpoint group Engine protect Related FW 1.0.0
Range [units] 0.0..600.0[s]
Force
Default value 5 valueAlternative NO
config
Step 1
Comm object 10132 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the delay #2 which can be assigned to an input configured as alarm input
(protection).
Note: Protections configured at a binary inputs can have either fixed 0.5s evaluation delay or there are
three independent delay setpoints and one of them can be assigned to each particular binary input
protection.
ForceBlockDel1
Setpoint group Engine protect Related FW 1.0.0
Range [units] 0.0..60.0[s]
Force
Default value 5 valueAlternative NO
config
Step 0.1
Comm object 10569 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the delay after the binary input FORCE BLOCK 1 (PAGE 450) has been deactivated,
when the alarms configured as Force block #1 are started to be evaluated.
If you want more information on this function please go to the setpoint RunOnlyBlkDel1 (page 248)
where you can find a diagram for ForceBlockDel function as well.
ForceBlockDel3
Setpoint group Engine protect Related FW 1.0.0
Range [units] 0.0..60.0[s]
Force
Default value 5 valueAlternative YES
config
Step 0.1
Comm object 10571 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the delay after the binary input FORCE BLOCK 3 (PAGE 450) has been deactivated,
when the alarms configured as Force block #3 are started to be evaluated.
If you want more information on this function please go to the setpoint RunOnlyBlkDel1 (page 248)
where you can find a diagram for ForceBlockDel function as well.
ForceBlock5Del
Setpoint group Engine protect Related FW 1.0.0
Range [units] 0.0..3600.0[s]
Force
Default value 5.0 valueAlternative YES
config
Step 0.1
Comm object 11780 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the delay after the binary input FORCE BLOCK 3 (PAGE 450) has been deactivated,
when the alarms configured as Force block #5 are started to be evaluated.
If you want more information on this function please go to the setpoint RunOnlyBlkDel1 (page 248)
where you can find a diagram for ForceBlockDel function as well.
ResetActAlarms
Setpoint group Engine protect Related FW 1.0.0
Range [units] ENABLED, DISABLED [-]
Force
Default value ENABLED valueAlternative NO
config
Step -
Comm object 10665 Related applications all
Config level Standard
Setpoint visibility Always
Description
Pressing of the fault reset button (at any terminal or external button) resets only
DISABLED inactive alarms. Active alarms remain in the alarmlist unchanged and must be reset
again when they become inactive.
Pressing of the fault reset button (at any terminal or external button) resets all
alarms that are currently present in the alarm list. Inactive alarms disappear from the
ENABLED
alarm list immediately, active alarms are changed to "confirmed" state and
disappear when the alarm condition disappear or the alarm starts to be blocked.
If the difference of actual cylinder temperature from the average temperature is out of the allowed range
at one or more cylinders the alarm Wrn CylTemp is issued after the delay CylDifEvalDel (page 260)
elapses. The alarm is intended for detection that there is a problem with combustion at the particular
cylinders.
Note: Logical analog inputs Cyl temp "n" must be configured onto the appropriate physical analog inputs
where the cylinder temperature sensors are connected. Use the "Cylinder temperature configuration
wizard" in GenConfig - Analog inputs tab for easy configuration of cylinder temperature sensors.
Max+CylDifPnom
Setpoint group Engine protect Related FW 1.0.0
Range [units] -32000..+32000[°C]
Force
Default value 10 valueAlternative NO
config
Step 1
Comm object 9624 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the maximum allowed positive difference between a particular cylinder
temperature and average cylinder temperature at nominal power. This setpoint is one of four setpoints
that define the allowed area of cylinder temperature differencies depending on Controller power. See the
setpoint Max+CylDifPmin (page 257) for more details.
PminCylDifEval
Setpoint group Engine protect Related FW 1.0.0
0..Nomin Power (page 202)[kW] (this depends on selected Power formats (page
Range [units]
158))
10 (this depends on Force
Default value selected Power valueAlternative NO
formats (page 158)) config
Step 1 (this depends on selected Power formats (page 158))
Comm object 9626 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the Controller power level below which the cylinder temperature difference
protection is not evaluated. Learn more about this protection in the description of the setpoint
Max+CylDifPmin (page 257).
Service time 1
Setpoint group Engine protect Related FW 1.0.0
Range [units] 0..32766..OFF(32767) [h]
Force
Default value 32766 valueAlternative NO
config
Step 1
Comm object 15114 Related applications all
Config level Standard
Setpoint visibility Always
Description
Service timers could be reseted with password protected command.
There is special dialog window available, where could be every Service timer set on the value prezented
with this Setpoint.
Actual Value of this interval is presented with Value Service time 1 (page 411).
If the Setpoint is set on the maximal Value (OFF), the counter is stopped and actual Value is visible as
####.
If is the actual Value counted to 0, the related alarm message is issued (i.e. WrnServiceT1+2 or
WrnServiceT3) and the counter continous counting until the maximal minus Value.
Alarm remains active until the Service time is reseted.
Note: Each of the maintenance intervals can be used for different type of regular maintenance works
such as oil change, spark plug change etc.
ClutchMinSpeed
Setpoint group Engine protection Related FW 1.0.0
Range [units] 0.0 .. ClutchMaxSpeed [%]
Force value
Default value 0.0 YES
Alternative config
Step 0.1
Comm object 10096 Related applications Allspeed
Config level Standard
Setpoint visibility Always
Description
Clutch can be switched on if ClutchMinSpeed < RPM < ClutchMaxSpeed. Limits are in % of the
Requested speed. See Requested RPM.
Note: 0.0 % corresponds to 0,3*Nominal speed, 100.0 % corresponds to 1,1*Nominal speed.
Batt <V
Setpoint group Analog protect Related FW 1.0.0
Range [units] 8.0..40.0[V]
Force
Default value 22 valueAlternative NO
config
Step 0.1
Comm object 9265 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the warning level for battery undervoltage alarm.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 2
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10668 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 3
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10669 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 4
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10670 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 5
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10671 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 6
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10672 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 7
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10673 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 8
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10674 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 9
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10675 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 10
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10676 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 11
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10677 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 12
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10678 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 13
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10679 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 14
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10680 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 15
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10681 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 16
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 10682 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 16 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 17
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15616 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 18
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15617 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 19
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15618 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 20
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15619 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 21
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15620 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 22
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15621 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 23
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15622 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 24
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15623 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 25
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15624 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 26
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15625 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 27
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15626 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 28
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15627 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 29
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15628 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 30
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15629 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 31
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15630 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
Force value 32
Setpoint group Force value Related FW 1.0.0
Range [units] [-] (this depends on where the Force value is configured)
0 (this depends on Force
Default value where the Force value valueAlternative NO
is configured) config
Step 1 (this depends on where the Force value is configured)
Comm object 15631 Related applications all
Config level Standard
Setpoint visibility Always
Description
This is one of the 32 setpoints reserved for using as alternative setpoints for the force value functions.
The alternative setpoint is to be assigned to a particular force value function and renamed in GenConfig.
See also the input FORCEVALUEIN 1 (PAGE 452).
Note: It is not obligatory to use one of these reserved setpoints for a force value function. It is possible to
use also any other setpoint or value with matching dimension and decimal resolution.
Note: There isn't any relation between the default names of the force value function blocks, associated
binary inputs and the default names of the reserved setpoints. In other words, the setpoint with default
name Force value 3 is not related to the Force value 3 function block.
ExValue1LoLim
Setpoint group Force value Related FW 1.0.0
Range [units] -32000..ExValue1HiLim (page 288)[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 11012 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the low limit of the value of ExValue 1 if the value is lowered/raised by the binary
inputs EXVALUE1 UP (PAGE 439) and EXVALUE1 DOWN (PAGE 442). The ExValue 1 is never lowered
below this limit.
Note: This limit is not taken into account if the value ExValue 1 is written remotely from a terminal using
the appropriate command ExValue #n.
ExValue2LoLim
Setpoint group Force value Related FW 1.0.0
Range [units] -32000..ExValue2HiLim (page 288)[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 11013 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the low limit of the value of ExValue 2 if the value is lowered/raised by the binary
inputs EXVALUE2 UP (PAGE 440) and EXVALUE2 DOWN (PAGE 442). The ExValue 2 is never lowered
below this limit.
Note: This limit is not taken into account if the value ExValue 2 is written remotely from a terminal using
the appropriate command ExValue #n.
ExValue4LoLim
Setpoint group Force value Related FW 1.0.0
Range [units] -32000..ExValue1HiLim (page 288)[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 11015 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the low limit of the value of ExValue 4 if the value is lowered/raised by the binary
inputs EXVALUE4 UP (PAGE 440) and EXVALUE4 DOWN (PAGE 443). The ExValue 4 is never lowered
below this limit.
Note: This limit is not taken into account if the value ExValue 4 is written remotely from a terminal using
the appropriate command ExValue #n.
ExValue6LoLim
Setpoint group Force value Related FW 1.0.0
Range [units] -32000..ExValue2HiLim (page 288)[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 16506 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the low limit of the value of ExValue 6 if the value is lowered/raised by the binary
inputs EXVALUE6 UP (PAGE 441) and EXVALUE6 DOWN (PAGE 443). The ExValue 6 is never lowered
below this limit.
Note: This limit is not taken into account if the value ExValue 6 is written remotely from a terminal using
the appropriate command ExValue #n.
ExValue8LoLim
Setpoint group Force value Related FW 1.0.0
Range [units] -32000..ExValue2HiLim (page 288)[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 16508 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the low limit of the value of ExValue 8 if the value is lowered/raised by the binary
inputs EXVALUE8 UP (PAGE 441) and EXVALUE8 DOWN (PAGE 444). The ExValue 8 is never lowered
below this limit.
Note: This limit is not taken into account if the value ExValue 8 is written remotely from a terminal using
the appropriate command ExValue #n.
ExValue10LoLim
Setpoint group Force value Related FW 1.0.0
Range [units] -32000..ExValue2HiLim (page 288)[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 16510 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the low limit of the value of ExValue 10 if the value is lowered/raised by the binary
inputs EXVALUE10 UP (PAGE 441) and EXVALUE10 DOWN (PAGE 444). The ExValue 10 is never lowered
below this limit.
Note: This limit is not taken into account if the value ExValue 10 is written remotely from a terminal
using the appropriate command ExValue #n.
ExValue12LoLim
Setpoint group Force value Related FW 1.0.0
Range [units] -32000..ExValue2HiLim (page 288)[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 16512 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the low limit of the value of ExValue 12 if the value is lowered/raised by the binary
inputs EXVALUE2 UP (PAGE 440) and EXVALUE2 DOWN (PAGE 442). The ExValue 12 is never lowered
below this limit.
Note: This limit is not taken into account if the value ExValue 12 is written remotely from a terminal
using the appropriate command ExValue #n.
ExValue2HiLim
Setpoint group Force value Related FW 1.0.0
Range [units] ExValue2LoLim (page 282)..32000[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 11017 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the high limit of the value of ExValue 2 if the value is lowered/raised by the binary
inputs EXVALUE2 UP (PAGE 440) and EXVALUE2 DOWN (PAGE 442). The ExValue 2 is never raised over
this limit.
Note: This limit is not taken into account if the value ExValue 2 is written remotely from a terminal using
the appropriate command ExValue #n.
ExValue4HiLim
Setpoint group Force value Related FW 1.0.0
Range [units] ExValue4LoLim (page 283)..32000[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 11019 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the high limit of the value of ExValue 4 if the value is lowered/raised by the binary
inputs EXVALUE4 UP (PAGE 440) and EXVALUE4 DOWN (PAGE 443). The ExValue 4 is never raised over
this limit.
Note: This limit is not taken into account if the value ExValue 4 is written remotely from a terminal using
the appropriate command ExValue #n.
ExValue6HiLim
Setpoint group Force value Related FW 1.0.0
Range [units] ExValue6LoLim (page 284)..32000[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 16514 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the high limit of the value of ExValue 6 if the value is lowered/raised by the binary
inputs EXVALUE6 UP (PAGE 441) and EXVALUE6 DOWN (PAGE 443). The ExValue 6 is never raised over
this limit.
Note: This limit is not taken into account if the value ExValue 6 is written remotely from a terminal using
the appropriate command ExValue #n.
ExValue8HiLim
Setpoint group Force value Related FW 1.0.0
Range [units] ExValue8LoLim (page 285)..32000[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 16516 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the high limit of the value of ExValue 8 if the value is lowered/raised by the binary
inputs EXVALUE8 UP (PAGE 441) and EXVALUE8 DOWN (PAGE 444). The ExValue 8 is never raised over
this limit.
Note: This limit is not taken into account if the value ExValue 8 is written remotely from a terminal using
the appropriate command ExValue #n.
ExValue10HiLim
Setpoint group Force value Related FW 1.0.0
Range [units] ExValue10LoLim (page 286)..32000[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 16518 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the high limit of the value of ExValue 10 if the value is lowered/raised by the binary
inputs EXVALUE10 UP (PAGE 441) and EXVALUE10 DOWN (PAGE 444). The ExValue 10 is never raised
over this limit.
Note: This limit is not taken into account if the value ExValue 10 is written remotely from a terminal
using the appropriate command ExValue #n.
ExValue12HiLim
Setpoint group Force value Related FW 1.0.0
Range [units] ExValue12LoLim (page 287)..32000[X]
Force
Default value 0 valueAlternative NO
config
Step 1
Comm object 16520 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the high limit of the value of ExValue 12 if the value is lowered/raised by the binary
inputs EXVALUE12 UP (PAGE 442) and EXVALUE12 DOWN (PAGE 445). The ExValue 12 is never raised
over this limit.
Note: This limit is not taken into account if the value ExValue 12 is written remotely from a terminal
using the appropriate command ExValue #n.
ExValue2 rate
Setpoint group Force value Related FW 1.0.0
Range [units] 1..10000[X/s]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 11021 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the rate pre second at which the ExValue 2 is beeing changed while the input
EXVALUE2 UP (PAGE 440) or EXVALUE2 DOWN (PAGE 442) is active.
ExValue4 rate
Setpoint group Force value Related FW 1.0.0
Range [units] 1..10000[X/s]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 11023 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the rate pre second at which the ExValue 4 is beeing changed while the input
EXVALUE4 UP (PAGE 440) or EXVALUE4 DOWN (PAGE 443) is active.
ExValue6 rate
Setpoint group Force value Related FW 1.0.0
Range [units] 1..10000[X/s]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 16530 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the rate pre second at which the ExValue 6 is being changed while the input
EXVALUE6 UP (PAGE 441) or EXVALUE6 DOWN (PAGE 443) is active.
ExValue8 rate
Setpoint group Force value Related FW 1.0.0
Range [units] 1..10000[X/s]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 16532 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the rate pre second at which the ExValue 8 is being changed while the input
EXVALUE8 UP (PAGE 441) or EXVALUE8 DOWN (PAGE 444) is active.
ExValue10 rate
Setpoint group Force value Related FW 1.0.0
Range [units] 1..10000[X/s]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 16534 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the rate pre second at which the ExValue 10 is being changed while the input
EXVALUE10 UP (PAGE 441) or EXVALUE10 DOWN (PAGE 444) is active.
ExValue12 rate
Setpoint group Force value Related FW 1.0.0
Range [units] 1..10000[X/s]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 16536 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the rate per second at which the ExValue 12 is being changed while the input
EXVALUE12 UP (PAGE 442) or EXVALUE12 DOWN (PAGE 445) is active.
ExValue2deflt
Setpoint group Force value Related FW 1.0.0
Range [units] -32000..32000[x]
Force
Default value 0 valueAlternative YES
config
Step 1
Comm object 11009 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the reset (initial) value of the ExValue 2. This initial value is applied either when the
controller is powered-on or when the ExValue 2 is reset by the binary input EXVALUE2RESET (PAGE 446).
ExValue4deflt
Setpoint group Force value Related FW 1.0.0
Range [units] -32000..32000[x]
Force
Default value 100 valueAlternative YES
config
Step 1
Comm object 11011 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the reset (initial) value of the ExValue 4. This initial value is applied either when the
controller is powered-on or when the ExValue 4 is reset by the binary input EXVALUE4RESET (PAGE 446).
ExValue6deflt
Setpoint group Force value Related FW 1.0.0
Range [units] ExValue6LoLim..ExValue6HiLim[x]
Force
Default value 100 valueAlternative YES
config
Step 1
Comm object 16522 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the reset (initial) value of the ExValue 6. This initial value is applied either when the
controller is powered-on or when the ExValue 6 is reset by the binary input EXVALUE6RESET (PAGE 447).
ExValue8deflt
Setpoint group Force value Related FW 1.0.0
Range [units] ExValue8LoLim..ExValue8HiLim[x]
Force
Default value 100 valueAlternative YES
config
Step 1
Comm object 16524 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the reset (initial) value of the ExValue 8. This initial value is applied either when the
controller is powered-on or when the ExValue 8 is reset by the binary input EXVALUE8RESET (PAGE 448).
ExValue10deflt
Setpoint group Force value Related FW 1.0.0
Range [units] ExValue10LoLim..ExValue10HiLim[x]
Force
Default value 100 valueAlternative YES
config
Step 1
Comm object 16526 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the reset (initial) value of the ExValue 10. This initial value is applied either when
the controller is powered-on or when the ExValue 10 is reset by the binary input EXVALUE10RESET (PAGE
448).
ExValue12deflt
Setpoint group Force value Related FW 1.0.0
Range [units] ExValue12LoLim..ExValue12HiLim[x]
Force
Default value 100 valueAlternative YES
config
Step 1
Comm object 16528 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the reset (initial) value of the ExValue 12. This initial value is applied either when
the controller is powered-on or when the ExValue 12 is reset by the binary input EXVALUE12RESET (PAGE
449).
Timer channel 2
Setpoint group Timer settings Related FW 1.0.0
Range [units] [-]
Force
Default value OFF valueAlternative NO
config
Step -
Comm object 10970 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the mode of the Timer channel #2. Output from this channel is available in the
combined output TIMERACT 1-4 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers
Timer channel 4
Setpoint group Timer settings Related FW 1.0.0
Range [units] [-]
Force
Default value OFF valueAlternative NO
config
Step -
Comm object 10973 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the mode of the Timer channel #4. Output from this channel is available in the
combined output TIMERACT 1-4 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers
Timer channel 6
Setpoint group Timer settings Related FW 1.0.0
Range [units] [-]
Force
Default value OFF valueAlternative NO
config
Step -
Comm object 10975 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the mode of the Timer channel #6. Output from this channel is available in the
combined output TIMERACT 5-8 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers
Timer channel 8
Setpoint group Timer settings Related FW 1.0.0
Range [units] [-]
Force
Default value OFF valueAlternative NO
config
Step -
Comm object 10977 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the mode of the Timer channel #8. Output from this channel is available in the
combined output TIMERACT 5-8 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers
Timer channel 10
Setpoint group Timer settings Related FW 1.0.0
Range [units] [-]
Force
Default value OFF valueAlternative NO
config
Step -
Comm object 10979 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the mode of the Timer channel #10. Output from this channel is available in the
combined output TIMERACT 9-12 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers
Timer channel 12
Setpoint group Timer settings Related FW 1.0.0
Range [units] [-]
Force
Default value OFF valueAlternative NO
config
Step -
Comm object 10981 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the mode of the Timer channel #12. Output from this channel is available in the
combined output TIMERACT 9-12 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers
Timer channel 14
Setpoint group Timer settings Related FW 1.0.0
Range [units] [-]
Force
Default value OFF valueAlternative NO
config
Step -
Comm object 10983 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the mode of the Timer channel #14. Output from this channel is available in the
combined output TIMERACT 13-16 (PAGE 558).
Note: See the chapter General purpose timers (page 148) for more details about timers
Timer channel 16
Setpoint group Timer settings Related FW 1.0.0
Range [units] [-]
Force
Default value OFF valueAlternative NO
config
Step -
Comm object 10985 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint adjusts the mode of the Timer channel #16. Output from this channel is available in the
combined output TIMERACT 13-16 (PAGE 558).
Note: See the chapter General purpose timers (page 148) for more details about timers
Alarm only
Setpoint group Act. calls/SMS Related FW 1.0.0
Range [units] DISABLED, ENABLED[-]
Force
Default value DISABLED valueAlternative YES
config
Step -
Comm object 10567 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint is used to enable sending SMS and/or e-mail alerts when a "protection" configured as Alarm
only occurs. See the chapter Protections and Alarm management (page 169) for more information
about protection types.
Cool down
Setpoint group Act. calls/SMS Related FW 1.0.0
Range [units] DISABLED, ENABLED [-]
Force
Default value DISABLED valueAlternative YES
config
Step -
Comm object 8485 Related applications Allspeed
Config level Standard
Setpoint visibility Always
Description
Enables or disables active calls/SMS to selected phone or mobile numbers when a Cool down alarm
occurs.
ShutdownOvr
Setpoint group Act. calls/SMS Related FW 1.0.0
Range [units] DISABLED, ENABLED[-]
Force
Default value DISABLED valueAlternative YES
config
Step -
Comm object 11413 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint is used to enable sending SMS and/or e-mail alerts when a Sd Override-type alarm occurs.
See the chapter Protections and Alarm management (page 169) for more information about protection
types.
AcallCH1-Addr
Setpoint group Act. calls/SMS Related FW 1.0.0
Range [units] - [-]
Force
Default value valueAlternative NO
config
Step -
Comm object 9597 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint is used to specify the recipient address for the active calls - channel 1. The content of the
address must correspond to the selected alert type (e.g. it must contain e-mail address if the alert type is
e-mail). See the chapter Protections and Alarm management (page 169) for more details.
AcallCH2-Addr
Setpoint group Act. calls/SMS Related FW 1.0.0
Range [units] - [-]
Force
Default value valueAlternative NO
config
Step -
Comm object 9598 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint is used to specify the recipient address for the active calls - channel 2. The content of the
address must correspond to the selected alert type (e.g. it must contain e-mail address if the alert type is
e-mail). See the chapter Protections and Alarm management (page 169) for more details.
AcallCH3-Addr
Setpoint group Act. calls/SMS Related FW 1.0.0
Range [units] - [-]
Force
Default value valueAlternative NO
config
Step -
Comm object 9599 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint is used to specify the recipient address for the active calls - channel 2. The content of the
address must correspond to the selected alert type (e.g. it must contain e-mail address if the alert type is
e-mail). See the chapter Protections and Alarm management (page 169) for more information about
protection types.
AcallCH5-Type
Setpoint group Act. calls/SMS Related FW 1.0.0
DISABLED, DATA-ANA, DATA-GSM, DATA-ISDN, DATA-CDMA, SMS-GSM,
Range [units]
SMS-CDMA, IB-E-MAIL, IB-EML-SMS [-]
Force
Default value DISABLED valueAlternative NO
config
Step -
Comm object 13275 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint is used to specify the alert type of the active calls - channel 5. See the chapter Protections
and Alarm management (page 169) for more details.
AcallCH5-Addr
Setpoint group Act. calls/SMS Related FW 1.0.0
Range [units] - [-]
Force
Default value valueAlternative NO
config
Step -
Comm object 13277 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint is used to specify the recipient address for the active calls - channel 5. The content of the
address must correspond to the selected alert type (e.g. it must contain e-mail address if the alert type is
e-mail). See the chapter Protections and Alarm management (page 169) for more details.
ActCallAttempt
Setpoint group Act. calls/SMS Related FW 1.0.0
Range [units] 1..250[-]
Force
Default value 5 valueAlternative NO
config
Step 1
Comm object 24505 Related applications all
Config level Standard
Setpoint visibility Always
Description
This setpoint is used to adjust the maximum number of consequent attempts to perform an active data
call. The next attempt is performed 120s after the previous unsuccessful attempt.
Group: Date/Time
Time stamp act
Setpoint group Date/Time Related FW 1.0.0
Range [units] DISABLED, ENGINE RUNNING, ALWAYS[-]
Force
Default value ENGINE RUNNING valueAlternative NO
config
Step -
Comm object 10532 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint selects the Time stamp function mode.
#SummerTimeMod
Setpoint group Date/Time Related FW 1.0.0
Range [units] DISABLED, WINTER, SUMMER, WINTER-S, SUMMER-S[-]
Force
Default value DISABLED valueAlternative NO
config
Step -
Comm object 8727 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint is used to select the mode of automatic daylight saving time change.
DISABLED The automatic change to daylight saving time and back is disabled.
The automatic change is enabled, the current season is winter and the controller is
WINTER
located in the northern hemisphere.
The automatic change is enabled, the current season is summer and the controller
SUMMER
is located in the northern hemisphere.
The automatic change is enabled, the current season is winter and the controller is
WINTER-S
located in the southern hemisphere.
The automatic change is enabled, the current season is summer and the controller
SUMMER-S
is located in the southern hemisphere.
#Time
Setpoint group Date/Time Related FW 1.0.0
Range [units] [HH:MM:SS]
Force
Default value 0:00:00 valueAlternative NO
config
Step -
Comm object 24554 Related applications all
Config level Standard
Setpoint visibility Always
Description
The setpoint shows the current time from the internal RTC clock of the controller and can be also used to
readjust it.
Note: If the controller is connected to other controllers via the CAN2 bus, the setpoints #Time and #Date
are automatically synchronized each hour with the controller that has lowest address. If date/time is
changed at one controller it is automatically updated also in all other controllers in the group.
AUTOMATIC - mixer position is controlled automatically according to adjusted starting, running and low
power positions and then according to adjusted Sensor and power characteristics.
MixManOffset
Setpoint group AFR Control Related FW 1.0.0
Range [units] -100,00...100,00 [%]
Force
Default value 0,00 valueAlternative YES
config
Step 0,01
Comm object 15086 Related applications all
Config level Standard
Setpoint visibility Always
Description
Adjustable setpoint for offset between two mixers. Offset is usable only if the Setpoint AFRValve
MODE (page 327) is in position MANUAL.
This Setpoint specify the offset of the second mixer in case of using two mixer control.
Note: Mixer position output speed doesn't depend on AFRvalve gain (page 329) setting.
AFRvalve der
Setpoint group AFR Control Related FW 1.0.0
Range [units] 0...100 [%]
Force
Default value 5 valueAlternative YES
config
Step 1
Comm object 10083 Related applications all
Config level Standard
Setpoint visibility Always
Description
Derivative factor for AFR control loop
MATreference
Setpoint group AFR Control Related FW 1.0.0
Range [units] Sensor range [Dim]
Default value 30 Force valueAlternative config NO
Step 1
Comm object 15055 Related applications all
Config level Standard
Setpoint visibility Always
Description
Setpoint defines the reference Value for what is AFR Sensor curve adjusted.
IMPORTANT: Range and resolution of the setpoint is defined by setting of LAI:MAT A (PAGE
430).
SensorCorrLim
Setpoint group AFR Control Related FW 1.0.0
Range [units] Sensor range [Dim]
Force
Default value 0 valueAlternative YES
config
Step 1
Comm object 12083 Related applications all
Config level Standard
Setpoint visibility Always
Description
Setpoint defines maximum allowable change of Sensor required Value due to the MATcorrection (page
333) algorithm.
Use this Setpoint to block the MATcorrection (page 333) contribution in case the MAT Value varies
significantly from the MATreference (page 332).
AFRPIDmulti
Setpoint group AFR Control Related FW 1.0.0
Range [units] 1...10 [-]
Default value 1 Force valueAlternative config NO
Step 1
Comm object 14455 Related applications all
Config level Standard
Setpoint visibility Always
Description
Value from this setpoint will multiply integral part of regulation and results will be used for AFR PID control.
MisfSensReduct
Setpoint group AFR Control Related FW 1.2.0
Range [units] Sensor range [Dim]
Default value 0 Force valueAlternative config NO
Step 1
Comm object 10084 Related applications all
Config level Standard
Setpoint visibility Always
Description
When the LBI: MISFIRING (PAGE 477) is active the Value AFRSensReqA (page 415) is reduced.
Misfiring del
Setpoint group AFR Control Related FW 1.2.0
Range [units] MisfLdRed del (page 336)...600 [s]
Force
Default value 30 valueAlternative NO
config
Step 1
Comm object 10086 Related applications all
Config level Standard
Setpoint visibility Always
Description
Slow stop protection is activated after delay given by this Setpoint when LBI MISFIRING (PAGE 477) is
active.
KnockingReduct
Setpoint group AFR Control Related FW 1.0.0
Range [units] 0,00..100,00 [%]
Force
Default value 0,00 valueAlternative YES
config
Step 0,01
Comm object 15760 Related applications all
Config level Standard
Setpoint visibility Always
Description
Setpoint value is reference for Power reduction based on LBI:DxLoad Reduct.
Activation of LBI:DxLoadReduct reduce the actual power to the power set by this setpoint. If the actual
power is lower than the value presented bysSetpoint KnockingReduct Controller stays on lowest required
value. "Wrn Knocking" has to be active while the LBI:DxLoadReduct=1.
EndStrtPosA
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force valueAlternative
Default value 35,00 YES
config
Step 0,01
Comm object 15026 Related applications all
Config level Standard
Setpoint visibility Always
Description
Mixer starts on the StartPositionA (page 339) and during the cranking phase starts to move. This
Setpoint defines the end position of the mixer during the cranking phase.
RunPositionA
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force
Default value 30,00 valueAlternative YES
config
Step 0,01
Comm object 10065 Related applications all
Config level Standard
Setpoint visibility Always
Description
Mixer fixed position for reaching the Nominal RPM (page 203). Position is activated after Idle time
(page 238) is counted down and stays active till the clutch is closed.
During the unload phase is the RunPosition activated when the clutch is opened and till the engine stops.
Power1A
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] 0,0...Power2A (page 343) [kW]
Force valueAlternative
Default value 10,0 NO
config
Step 0,1
Comm object 8420 Related applications all
Config level Standard
Setpoint visibility Always
Description
The first Sensor characteristic specification: engine power for Sensor Value and kW power limit for AFR.
MixPos1A
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force valueAlternative
Default value 10,00 NO
config
Step 0,01
Comm object 8408 Related applications all
Config level Standard
Setpoint visibility Always
Description
First required mixer position for actual power and from that related Sensor value.
Sensor2A
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] Sensor range [Dim]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 8433 Related applications all
Config level Standard
Setpoint visibility Always
Description
Range and dimension of the sensor is taken over from LAI SENSORA (PAGE 431) settings.
Second point of required sensor Value characteristic related to Power2A (page 343).
MixPos2A
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force valueAlternative
Default value 20,00 NO
config
Step 0,01
Comm object 8409 Related applications all
Config level Standard
Setpoint visibility Always
Description
Second required mixer position for actual power and from that related Sensor value.
Power3A
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] Power2A (page 343)...Power4A (page 346) [kW]
Force valueAlternative
Default value 20,0 NO
config
Step 0,1
Comm object 8422 Related applications all
Config level Standard
Setpoint visibility Always
Description
The third Sensor characteristic specification: engine power for Sensor Value and kW power limit for AFR.
MixPos3A
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force
Default value 30,00 valueAlternative NO
config
Step 0,01
Comm object 8410 Related applications all
Config level Standard
Setpoint visibility Always
Description
Third required mixer position for actual power and from that related Sensor value.
Sensor4A
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] Sensor range [Dim]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 8435 Related applications all
Config level Standard
Setpoint visibility Always
Description
Range and dimension of the sensor is taken over from LAI SENSORA (PAGE 431) settings.
Fourth point of required sensor Value characteristic related to Power4A (page 346).
MixPos4A
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force
Default value 40,00 valueAlternative NO
config
Step 0,01
Comm object 8411 Related applications all
Config level Standard
Setpoint visibility Always
Description
Fourth required mixer position for actual power and from that related Sensor value.
Power5A
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] Power4A (page 346)...3200,0 [kW]
Force valueAlternative
Default value 30,0 NO
config
Step 0,1
Comm object 8424 Related applications all
Config level Standard
Setpoint visibility Always
Description
The fifth Sensor characteristic specification: engine power for Sensor Value and kW power limit for AFR.
Sensor5A
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] Sensor range [Dim]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 8436 Related applications all
Config level Standard
Setpoint visibility Always
Description
Range and dimension of the sensor is taken over from LAI SENSORA (PAGE 431) settings.
Fifth point of required sensor Value characteristic related to Power5A (page 347).
MixPos5A
Setpoint group AFR MIX A Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force
Default value 60,00 valueAlternative NO
config
Step 0,01
Comm object 8412 Related applications all
Config level Standard
Setpoint visibility Always
Description
Fifth required mixer position for actual power and from that related Sensor value.
LBI:
GASAB 0 1
(PAGE 465)
RunPositionB (page 357) -
Dif1 StartPositionA (page 339)
StartPositionB (page 355)
LoPwrPositionA (page 341) - LoPwrPositionB (page 357) -
Dif2
StartPositionA (page 339) StartPositionB (page 355)
StartPositionB
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force
Default value 35,00 valueAlternative YES
config
Step 0,01
Comm object 10064 Related applications all
Config level Standard
Setpoint visibility Always
Description
Mixer fix position for Engine start.
MixStartRampB
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] 0...240 [s]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 15029 Related applications all
Config level Standard
Setpoint visibility Always
Description
Setpoint defines the ramp for mixer moving from StartPositionB (page 355) during the cranking
procedure to reach the EndStrtPosB (page 356).
LoPwrPositionB
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force
Default value 25,00 valueAlternative YES
config
Step 0,01
Comm object 11575 Related applications all
Config level Standard
Setpoint visibility Always
Description
Mixer fixed position after the clutch is closed until the compressor reaches the first point of Sensor1B
(page 358) and Power1B (page 358) value.
Sensor1B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] Sensor range [Dim]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 8468 Related applications all
Config level Standard
Setpoint visibility Always
Description
Range and dimension of the sensor is taken over from LAI SENSORB (PAGE 431) settings.
First point of required sensor Value characteristic related to Power1B (page 358).
MixPos1B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force
Default value 10,00 valueAlternative NO
config
Step 0,01
Comm object 8742 Related applications all
Config level Standard
Setpoint visibility Always
Description
First required mixer position for actual power and from that related Sensor value.
Power2B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] Power1B (page 358)...Power3B (page 361) [kW]
Force valueAlternative
Default value 15,0 NO
config
Step 0,1
Comm object 8457 Related applications all
Config level Standard
Setpoint visibility Always
Description
The second Sensor characteristic specification: engine power for Sensor Value and kW power limit for
AFR.
Sensor2B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] Sensor range [Dim]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 8469 Related applications all
Config level Standard
Setpoint visibility Always
Description
Range and dimension of the sensor is taken over from LAI SENSORB (PAGE 431) settings.
Second point of required sensor Value characteristic related to Power2B (page 359).
MixPos2B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force
Default value 20,00 valueAlternative NO
config
Step 0,01
Comm object 8743 Related applications all
Config level Standard
Setpoint visibility Always
Description
Thirds required mixer position for actual power and from that related Sensor value.
Sensor3B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] Sensor range [Dim]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 8470 Related applications all
Config level Standard
Setpoint visibility Always
Description
Range and dimension of the sensor is taken over from LAI SENSORB (PAGE 431) settings.
Third point of required sensor Value characteristic related to Power3B (page 361).
MixPos3B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force
Default value 30,00 valueAlternative NO
config
Step 0,01
Comm object 8744 Related applications all
Config level Standard
Setpoint visibility Always
Description
Third required mixer position for actual power and from that related Sensor value.
Power4B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] Power3B (page 361)...Power5B (page 364) [kW]
Force valueAlternative
Default value 25,0 NO
config
Step 0,1
Comm object 8459 Related applications all
Config level Standard
Setpoint visibility Always
Description
The fourth Sensor characteristic specification: engine power for Sensor Value and kW power limit for
AFR.
Sensor4B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] Sensor range [Dim]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 8471 Related applications all
Config level Standard
Setpoint visibility Always
Description
Range and dimension of the sensor is taken over from LAI SENSORB (PAGE 431) settings.
Fourth point of required sensor Value characteristic related to Power4B (page 362).
MixPos4B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force
Default value 40,00 valueAlternative NO
config
Step 0,01
Comm object 8745 Related applications all
Config level Standard
Setpoint visibility Always
Description
Fourth required mixer position for actual power and from that related Sensor value.
Sensor5B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] Sensor range [Dim]
Force
Default value 1 valueAlternative YES
config
Step 1
Comm object 8472 Related applications all
Config level Standard
Setpoint visibility Always
Description
Range and dimension of the sensor is taken over from LAI SENSORB (PAGE 431) settings.
Fifth point of required sensor Value characteristic related to Power5B (page 364).
MixPos5B
Setpoint group AFR MIX B Related FW 1.0.0
Range [units] 0,00...100,00 [%]
Force
Default value 60,00 valueAlternative NO
config
Step 0,01
Comm object 8746 Related applications all
Config level Standard
Setpoint visibility Always
Description
Fifth required mixer position for actual power and from that related Sensor value.
LBI: Gas
0 1
AB
RunPositionA (page 340) - RunPositionB (page 357) -
Dif1
StartPositionA (page 339) StartPositionB (page 355)
LoPwrPositionA (page 341) - LoPwrPositionB (page 357) -
Dif2
StartPositionA (page 339) StartPositionB (page 355)
BI Speed ramp
1.0.0
Setpoint group Basic settings Related FW configured ECON-4 extension
module
Range [units] 1.0 - 100.0 [s]
Force value
Default value 50 s NO
Alternative config
Step 1.0 s
Comm object 7170 Related applications All
Config level Standard
Setpoint visibility Always
Description
Define how fast changes the requested engine speed if the binary inputs SPEED UP or SPEED DOWN are
active. BI Speed ramp is actually time that the ramp needs to go from Nominal RPM (page 377) - 8%
toNominal RPM (page 377) + 8% and vice versa. The ramping speed is the same for both up and down
directions.
Note: If possible, use binary control for CB request and wire terminal S4.1 and S4.2 to feedback signal.
This will assure fastest reaction of ECON4 when breaker is closed or opened. This is crucial to avoid
over speed in case of opening GCB (clutch) under load for example.
Overspeed
1.0.0
Setpoint group Basic settings Related FW configured ECON-4 extension
module
Range [units] 0 - 2500 [RPM]
Force value
Default value 1800 RPM NO
Alternative config
Step 1 RPM
Comm object 7168 Related applications All
Config level Standard
Setpoint visibility Always
Description
Maximum acceptable speed of the engine. If the actual engine speed is higher, ECON-4 immediately closes
the actuator. Normal function is restored after detection of zero engine speed.
Force value
Default value DATA NO
Alternative config
Step -
Comm object 7171 Related applications All
Config level Standard
Setpoint visibility Always
Description
The setpoint defines source of the Speed reference of the engine.
Idle-Nom ramp
1.0.0
Setpoint group Basic settings Related FW configured ECON-4 extension
module
Range [units] 0 - 100 [s]
Force value
Default value 10 s NO
Alternative config
Step 1s
Comm object 7169 Related applications All
Config level Standard
Setpoint visibility Always
Description
Define how fast changes the requested engine speed during transition from Idle RPM (page 372) to
Nominal RPM (page 377) and vice versa. Idle-Nom ramp is directly time that the ramp needs to go from
Idle RPM (page 372) to Nominal RPM (page 377) and vice versa. The ramping speed is the same for both
up and down directions.
Group: ECON4-EngStart
Fuel ramp time
Setpoint group Basic settings Related FW 1.0.0
Range [units] Start RPM - Nominal RPM
Force value
Default value 10 s NO
Alternative config
Step 1s
Comm object 7174 Related applications All
Config level Standard
Setpoint visibility Always
Description
Time the actuator needs to move from the InitStart dose to MaxStart dose.
InitStart dose
Setpoint group Basic settings Related FW 1.0.0
Range [units] Start RPM - Nominal RPM
Force value
Default value 10% NO
Alternative config
Step 1%
Comm object 7172 Related applications All
Config level Standard
Setpoint visibility Always
Description
Initial position of the actuator during start
RPM StartRamp
Setpoint group Basic settings Related FW 1.0.0
Range [units] Start RPM - Nominal RPM
Force value
Default value 10 s NO
Alternative config
Step 1s
Comm object 7175 Related applications All
Config level Standard
Setpoint visibility Always
Description
This setpoint defines speed of ramp from Starting RPM to Idle RPM. It is directly the time of ramp from.
Starting RPM
Setpoint group Basic settings Related FW 1.0.0
Range [units] Start RPM - Nominal RPM
Force value
Default value 350 RPM NO
Alternative config
Step 1 RPM
Comm object 7189 Related applications All
Config level Standard
Setpoint visibility Always
Description
If ECON-4 detects speed higher then Starting RPM, it terminates the starting sequence end starts normal
speed regulation.
Note: ECON-4 can work only if Starting RPM < Idle RPM < Nominal RPM. If this condition is not met, ECON-4
activates bit Invalid setpoints in Transmit PDO 1, see description of CAN protocol. It is not possible to run the
engine if the bit Invalid setpoint is signalized.
Group: ECON4-MainPID
Act position
1.0.0
Setpoint group Force value Related FW configured ECON-4
extension module
Range [units] 0.0 – 100.0 %
Force value Alternative
Default value 30% NO
config
Step 0.1 %
Comm object 7191 Related applications All
Config level Standard
Setpoint visibility Always
Description
Adjusts the actuator position in the Econ-4 Mode = MAN.
Note: In case there is chosen the ActuatorType 2-4, the function is still evaluated from the setting in
ActuatorType1.
ECON-4 mode
1.0.0
Setpoint group Force value Related FW configured ECON-4 extension
module
Range [units] -
Force value
Default value AUTO NO
Alternative config
Step -
Comm object 7190 Related applications All
Config level Standard
Setpoint visibility Always
Description
ECON-4 must be in AUTO for normal operation. Mode MAN can be used during installation to check the
function of the actuator and linkage. If ECON-4 is in MAN mode, it sets the actuator to position Act position.
It can be switched to MAN mode only any time even engine is running. This allows measurement of
transition curve to calculate PID parameters.
Note: ECON-4 when engine is running set the same value to setpoint Act position as position where throttle is.
It assure bump less transition.
IMPORTANT: Even Overspeed protection is active in all modes, be carefull when setting throttle
position manualy. Engine can accelerate when breaker opens or when throttle position is too
high.Make sure ECON-4 mode is in Auto positon before you leave installation.
Note: Set this setpoint after engine is running on Nominal speed (no load) according to the real position of
Actuator lever
Load der
1.0.0
Setpoint group Force value Related FW configured ECON-4 extension
module
Range [units] 0.0 – 100.0 %
Force value
Default value 0% NO
Alternative config
Step 0.1 %
Comm object 7181 Related applications All
Config level Standard
Setpoint visibility Always
Description
Derivative part of the PID speed regulation loop.
There is 5 different setpoints Load der:
Load der 1
Load der 2
Load der 3
Load der 4
For more information about Load der setting please see Load 1 on page 59 in ECON-4 Global Guide.
Load Int
1.0.0
Setpoint group Force value Related FW configured ECON-4 extension
module
Range [units] 0.0 – 100.0 %
Force value
Default value 10% NO
Alternative config
Step 0.1 %
Comm object 7180 Related applications All
Config level Standard
Setpoint visibility Always
Description
Integration of the PID speed regulation loop.
There is 5 different setpoints Load Int:
Load Int 1
Load Int 2
Load Int 3
Load Int 4
For more information about Load Int setting please see Load 1 on page 59 in ECON-4 Global Guide.
Note: It is also used as coordinate for Speed/Fuel line. See description in chapter Speed governor function in
parallel mode.
PWM rate
1.0.0
Setpoint group Force value Related FW configured ECON-4 extension
module
Range [units] 100 – 10 000 Hz
Force value
Default value 6000 Hz NO
Alternative config
Step 1 Hz
Comm object 7194 Related applications All
Config level Standard
Setpoint visibility Always
Description
Frequency of the PWM signal sent to ACT+ and ACT- outputs.
Note: For Heinzmann actuators adjust the PWM rate to 6000 Hz. For Woodward PWM and current, GAC
actuators adjust the PWM rate to 2000Hz.
SGO HiLim
1.0.0
Setpoint group Force value Related FW configured ECON-4 extension
module
Range [units] ± 10 V
Force value
Default value 10.00 V NO
Alternative config
Step 0.01 V
Comm object 14376 Related applications All
Config level Standard
Setpoint visibility WinScope only
Description
Together with Max Fuel value creates coordinates for second point of Speed/Fuel line. For detailed
description see Speed governor function in parallel mode on page 38 in ECON-4 Global Guide
Speed der
1.0.0
Setpoint group Force value Related FW configured ECON-4 extension
module
Range [units] 0.0 – 100.0 %
Force value
Default value 0% NO
Alternative config
Step 0.1 %
Comm object 7178 Related applications All
Config level Standard
Setpoint visibility Always
Description
Derivative part of the PID speed regulation loop.
Speed int
1.0.0
Setpoint group Force value Related FW configured ECON-4 extension
module
Range [units] 0.0 – 100.0 %
Force value
Default value 10% NO
Alternative config
Step 0.1 %
Comm object 7177 Related applications All
Config level Standard
Setpoint visibility Always
Description
Integration of the PID speed regulation loop..
For full list of values go to the chapter List of values (page 389).
6 back to Controller objects
6 back to Controller
objects
T Cyl aver
Value group Engine values Related FW 1.0.0
Resolution [units] °C
Comm object 9620 Related applications all
Description
The value contains average cylinder temperature, i.e. average of all configured logical analog inputs CYL
TEMP 1 (PAGE 422) ... CYL TEMP 32 (PAGE 428)
T Cyl max
Value group Engine values Related FW 1.0.0
Resolution [units] °C
Comm object 10526 Related applications all
Description
The value contains the maximum of all cylinder temperatures, i.e. maximum of all configured logical
analog inputs CYL TEMP 1 (PAGE 422) ... CYL TEMP 32 (PAGE 428)
Note: The value is intended for creating the "high cylinder temperature" alarm using an universal analog
protection. There is a special wizard at the I/O tab in GenConfig which makes the configuration of
cylinder temperatures easy.
T Cyl min
Value group Engine values Related FW 1.0.0
Resolution [units] ?C
Comm object 10527 Related applications all
Description
The value contains the minimus of all cylinder temperatures, i.e. maximum of all configured logical
analog inputs CYL TEMP 1 (PAGE 422) ... CYL TEMP 32 (PAGE 428)
Note: The value is intended for creating the "misfiring cylinder" alarm using an universal analog
protection.
Speed request
Value group Sync/Load ctrl Related FW 1.0.0
Resolution [units] %
Comm object 10137 Related applications all
Description
This value contains the speed control signal expressed in %. This value is used for digital interfacing (via
a communication bus) with ECUs that require the requested speed in %. The relation between Speed
request (page 392) is following:
0% is sent for SpeedRegOut = -10V
100% is sent for SpeedRegOut = 10V
Note: Most of ECU units use the J1939 TSC1 frame for speed control, where the requested speed is
expressed directly in RPM. Use the value SpeedReq RPM (page 393) for this purpose.
SpeedReq RPM
Value group Sync/Load ctrl Related FW 1.0.0
Resolution [units] RPM
Comm object 10006 Related applications all
Description
This value contains the speed which is currently requested by the controller from the attached ECU. This
value is used for digital interfacing (via a communication bus) with ECUs that require the requested
speed directly in RPM. The relation between SpeedReq RPM (page 393) and Speed request (page
392) is following:
0.3 * Nominal RPM is sent for 0%
1.1 * Nominal RPM is sent for 100%
SpeedReqRPMx8
Value group Sync/Load ctrl Related FW 1.0.0
Resolution [units] RPM
Comm object 14592 Related applications all
Description
Value is dedicated for ECON-4.
The Speed Request is recalculated to an absolute value in RPM and multiplied by 8 for more accurate
regulation in the ECON unit.
ReqEngineSpeed
Value group Sync/Load ctrl Related FW 1.0.0
Resolution [units] RPM
Comm object 11833 Related applications all
Description
This value contains an exact copy of the required speed which is beeing sent to the ECU (e.g. in the
TSC1 frame). It is intended for checking if the speed regulation chain is configured properly.
ExValue2
Value group Force value Related FW 1.0.0
Resolution [units] -
Comm object 11005 Related applications all
Description
This data object is intended for remote control of the Controller via the communication if some kind of
data is to be passed into the controller.
This object can be written via the communication (e.g. Modbus) without any limitation. Use GenConfig
function Generate Cfg Image to get the communication object number or register number of this particular
value object. See an example at the object ExValue1 (page 394).
ExValue4
Value group Force value Related FW 1.0.0
Resolution [units] X
Comm object 11007 Related applications all
Description
This data object is intended for remote control of the Controller via the communication if some kind of
data is to be passed into the controller.
This object can be written via the communication (e.g. Modbus) without any limitation. Use GenConfig
function Generate Cfg Image to get the communication object number or register number of this particular
value object. See an example at the object ExValue1 (page 394).
ExValue5
Value group Force value Related FW 1.0.0
Resolution [units] X
Comm object 16497 Related applications all
Description
This data object is intended for remote control of the Controller via the communication if some kind of
data is to be passed into the controller.
This object can be written via the communication (e.g. Modbus) without any limitation. Use GenConfig
function Generate Cfg Image to get the communication object number or register number of this particular
value object. See an example at the object ExValue1 (page 394).
ExValue7
Value group Force value Related FW 1.0.0
Resolution [units] X
Comm object 16499 Related applications all
Description
This data object is intended for remote control of the Controller via the communication if some kind of
data is to be passed into the controller.
This object can be written via the communication (e.g. Modbus) without any limitation. Use GenConfig
function Generate Cfg Image to get the communication object number or register number of this particular
value object. See an example at the object ExValue1 (page 394).
ExValue8
Value group Force value Related FW 1.0.0
Resolution [units] X
Comm object 16500 Related applications all
Description
This data object is intended for remote control of the Controller via the communication if some kind of
data is to be passed into the controller.
This object can be written via the communication (e.g. Modbus) without any limitation. Use GenConfig
function Generate Cfg Image to get the communication object number or register number of this particular
value object. See an example at the object ExValue1 (page 394).
ExValue10
Value group Force value Related FW 1.0.0
Resolution [units] X
Comm object 16502 Related applications all
Description
This data object is intended for remote control of the Controller via the communication if some kind of
data is to be passed into the controller.
This object can be written via the communication (e.g. Modbus) without any limitation. Use GenConfig
function Generate Cfg Image to get the communication object number or register number of this particular
value object. See an example at the object ExValue1 (page 394).
ExValue11
Value group Force value Related FW 1.0.0
Resolution [units] X
Comm object 16503 Related applications all
Description
This data object is intended for remote control of the Controller via the communication if some kind of
data is to be passed into the controller.
This object can be written via the communication (e.g. Modbus) without any limitation. Use GenConfig
function Generate Cfg Image to get the communication object number or register number of this particular
value object. See an example at the object ExValue1 (page 394).
Group: Analog CU
UBat
Value group Analog CU Related FW 1.0.0
Resolution [units] V
Comm object 8213 Related applications all
Description
Voltage at the controller power supply terminals.
D+
Value group Analog CU Related FW 1.0.0
Resolution [units] V
Comm object 10603 Related applications all
Description
Voltage measured at the D+ terminal. If this voltage is > 80% of the UBat (page 398) the D+ terminal is
evaluated as active and the engine is evaluated as running. See also the chapter Start sequence (page
137).
AIN CU-1
Value group Analog CU Related FW 1.0.0
Resolution [units] configurable
Comm object 9155 Related applications all
Description
This is the value of the analog input 1 of the controller. Analog inputs are fully configurable so the name
and units depend on configuration. In the default configuration the input is used for oil pressure
measurement.
AIN CU-3
Value group Analog CU Related FW 1.0.0
Resolution [units] configurable
Comm object 9157 Related applications all
Description
This is the value of the analog input 3 of the controller. Analog inputs are fully configurable so the name
and units depend on configuration. In the default configuration the input is used for fuel level
measurement.
AIN CU-4
Value group Analog CU Related FW 1.0.0
Resolution [units] configurable
Comm object 9158 Related applications all
Description
This is the value of the analog input 4 of the controller. Analog inputs are fully configurable so the name
and units depend on configuration. In the default configuration the input is used for fuel level
measurement.
Note: Click on button with "..." to get a clear list of BI names with their corresponding values.
Note: Click on button with "..." to get a clear list of BI names with their corresponding values.
Note: Click on button with "..." to get a clear list of BI names with their corresponding values.
LogBout 2
Value group Log bout Related FW 1.0.0
Resolution [units] -
Comm object 9144 Related applications all
Description
This is a bit array containing status of logical binary outputs 17-32 of the controller. Bit0 represents
LBO17, bit1 represents LBO18 etc..
Note: All terminals display binary values in "human-readable" form - from left to right. That means the
bit 0 is displayed in the most left position. This is different from common use in computer science, where
binary values are displayed from right to left.
Note: Click on button with "..." to get a clear list of BI names with their corresponding values.
LogBout 3
Value group Log bout Related FW 1.0.0
Resolution [units] -
Comm object 9145 Related applications all
Description
This is a bit array containing status of logical binary outputs 33-48 of the controller. Bit0 represents
LBO33, bit1 represents LBO34 etc..
Note: All terminals display binary values in "human-readable" form - from left to right. That means the
bit 0 is displayed in the most left position. This is different from common use in computer science, where
binary values are displayed from right to left.
Note: Click on button with "..." to get a clear list of BI names with their corresponding values.
Note: Click on button with "..." to get a clear list of BI names with their corresponding values.
LogBout 5
Value group Log bout Related FW 1.0.0
Resolution [units] -
Comm object 9147 Related applications all
Description
This is a bit array containing status of logical binary outputs 65-80 of the controller. Bit0 represents
LBO65, bit1 represents LBO66 etc..
Note: All terminals display binary values in "human-readable" form - from left to right. That means the
bit 0 is displayed in the most left position. This is different from common use in computer science, where
binary values are displayed from right to left.
Note: Click on button with "..." to get a clear list of BI names with their corresponding values.
LogBout 6
Value group Log bout Related FW 1.0.0
Resolution [units] -
Comm object 9148 Related applications all
Description
This is a bit array containing status of logical binary outputs 81-96 of the controller. Bit0 represents
LBO81, bit1 represents LBO82 etc..
Note: All terminals display binary values in "human-readable" form - from left to right. That means the
bit 0 is displayed in the most left position. This is different from common use in computer science, where
binary values are displayed from right to left.
Note: Click on button with "..." to get a clear list of BI names with their corresponding values.
RemoteControl
Value group Log bout Related FW 1.0.0
Resolution [units] -
Comm object 10627 Related applications all
Description
This is a bit array containing status of the binary outputs REMOTECONTROL 1 (PAGE 552) ...
REMOTECONTROL 8 (PAGE 554).
ModbusSw1
Value group Log bout Related FW 1.0.0
Resolution [units] -
Comm object 13267 Related applications all
Description
This is a bit array containing status of logical binary outputs which are controlled via direct writing to
Modbus.
For this is reserved register 46337.
Note: All terminals display binary values in "human-readable" form - from left to right. That means the
bit 0 is displayed in the most left position. This is different from common use in computer science, where
binary values are displayed from right to left.
Group: Info
Controller mode
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 9574 Related applications all
Description
This value contains actual controller mode. The controller mode is selected by the setpoint
ControllerMode (page 203) but the setpoint position can be overriden by binary inputs REMOTE OFF
(PAGE 483), REMOTE RUN (PAGE 484).
Build date
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 24211 Related applications all
Description
Build date of the appropriate SW version in the format according to ISO8601 (YYYY-MM-DD).
SW Version
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 24339 Related applications all
Description
Identification of firmware version. These are 4 numbers separated by a period.
Format is M.N.P.B where,
M. N. P - The first three numbers identify the version of this software Major.Minor.Patch
B - The last number identifies the build sequence number of this version
Application
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 8480 Related applications all
Description
Code of the application type. E.g. 1 for SPtM, 2 for SPI, 3 for MINT etc. The value is intended for
diagnostic purposes.
SW Branch
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 8707 Related applications all
Description
Firmware branch code. Contains 1 in case of standard branches.
PasswordDecode
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 9090 Related applications all
Description
This value contains encrypted serial number of the controller and administrator password and is intended
for retrieving of the lost password. Send this number together with controller serial number to your
distributor if you need to retrieve your password.
CAN16
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 8546 Related applications all
Description
Bits of this value show "1" if the controller receives messages from the controller which has address
corresponding with the bit position. Bit 0 represents address 1 etc. This value contains information about
controllers with addresses 1-16.
Note: The bit which corresponds to the own controller is always set to "1".
Engine state
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 9244 Related applications all
Description
Code of the current state of the engine control. The text representation of each code can be obtained
following way:
1. Open the archive in GenConfig and use the function File -> Generate Cfg Image -> Comm. objects to
create a list of all communication objects.
2. Open the file, find the row containing this value and look for the column "Type". The column "Type"
contains reference to a list of codes and their representations located in the bottom part of the file.
Timer text
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 10040 Related applications all
Description
Code of the currently running system process timer. The text representation of each code can be
obtained by the procedure described at the value Engine state (page 406).
Remaining time of the timer is available in the value Timer val (page 406).
Timer val
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 8955 Related applications all
Description
The value contains remaining time of the currently running system process timer. The name of the timer
is available in the value Timer text (page 406).
NextTime1-4
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 10927 Related applications all
Description
This value contains time of next activation of the timer block 1-4 (i.e. of the output TIMERACT 1-4 (PAGE
557)). The related date is available in the value NextDate1-4 (page 407).
Note: More information about timers is available in the chapter General purpose timers (page 148).
NextDate1-4
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 10931 Related applications all
Description
This value contains date of next activation of the timer block 1-4 (i.e. of the output TIMERACT 1-4 (PAGE
557)). The related time is available in the value NextTime1-4 (page 407).
Note: More information about timers is available in the chapter General purpose timers (page 148).
NextTime5-8
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 10928 Related applications all
Description
This value contains time of next activation of the timer block 5-8 (i.e. of the output TIMERACT 5-8 (PAGE
557)). The related date is available in the value NextDate5-8 (page 408).
Note: More information about timers is available in the chapter General purpose timers (page 148).
NextTime9-12
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 10929 Related applications all
Description
This value contains time of next activation of the timer block 9-12 (i.e. of the output TIMERACT 9-12
(PAGE 557)). The related date is available in the value NextDate9-12 (page 408).
Note: More information about timers is available in the chapter General purpose timers (page 148).
NextDate9-12
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 10933 Related applications all
Description
This value contains date of next activation of the timer block 9-12 (i.e. of the output TIMERACT 9-12
(PAGE 557)). The related time is available in the value NextTime9-12 (page 408).
Note: More information about timers is available in the chapter General purpose timers (page 148).
NextTime13-16
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 10930 Related applications all
Description
This value contains time of next activation of the timer block 13-16 (i.e. of the output TIMERACT 13-16
(PAGE 558)). The related date is available in the value NextDate13-16 (page 409).
Note: More information about timers is available in the chapter General purpose timers (page 148).
AirGate ID
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 24345 Related applications all
Description
If the controller is connected to the AirGate server this value displays the ID string assigned by the
server. This ID string is to be used in ComAp PC tools (e.g. InteliMonitor) to specify the respective
controller when the connection is opened.
AirGate status
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 15573 Related applications all
Description
This value displays actual status of the connection to the AirGate server.
Code Description
0 Not connected to AirGate.
1 Connected, registered, waiting for autorization.
2 Registration denied.
3 Can not register, no free capacity in the server.
4 Can not register, other reason.
5 Connected, registered, authorized.
Longitude
Value group Info Related FW 1.0.0
Resolution [units] -
Comm object 11679 Related applications all
Description
This value contains longitude of the controller. This value is obtained from connected IB-NT with active
GPS. Time is automatically synchronized as well when succesfull GPS fix is established. If no valid
value is available from InternetBridge-NT, value ##### is displayed.
Group: Statistics
Run Hours
Value group Statistics Related FW 1.0.0
Resolution [units] h
Comm object 8206 Related applications all
Description
Engine operation hours counter. If an ECU is configured and it provides engine hours value, the value is
taken from ECU. If the value is not available from the ECU or ECU is not configured, the engine hours
are incremented in the controller while the engine is running.
Note: The counter can be readjusted/reset from InteliMonitor menu Monitor -> Set statistics.
Run minutes
Value group Statistics Related FW 1.2.0
Resolution [units] min
Comm object 15118 Related applications all
Description
Engine operation minutes counter. If an ECU is configured and it provides engine minutes value, the
value is taken from ECU. If the value is not available from the ECU or ECU is not configured, the engine
minutes are incremented in the controller while the engine is running.
Note: The counter can't be readjusted/reset from InteliMonitor menu Monitor -> Set statistics.
Num starts
Value group Statistics Related FW 1.0.0
Resolution [units] -
Comm object 8207 Related applications all
Description
Engine start commands counter. The counter is increased by 1 even if the particular start command will
take more than one attempt.
Note: The counter can be readjusted/reset from InteliMonitor menu Monitor -> Set statistics.
NumUnsc start
Value group Statistics Related FW 1.0.0
Resolution [units] -
Comm object 10149 Related applications all
Description
Unsuccessful starts counter. The counter is incremented always when Start fail alarm is issued.
Note: The counter can be readjusted/reset from InteliMonitor menu Monitor -> Set statistics.
Service time 1
Value group Statistics Related FW 1.0.0
Resolution [units] h
Comm object 14397 Related applications all
Description
This is maintenance countdown timer #1. The timer is located in values (group Statistics).
Initial Value is given by the Setpoint Service time 1 (page 260).
Value is decremented while the Controller is running.
The alarm WrnServiceTime is issued as soon as the timer counts down to zero.
When the particular maintenance works have been performed, readjust the appropriate counter again to
the period of next regular maintenance cycle by pressing the Reset button in the Service timer dialog
window in InteliMonitor or by configured display command. The counter will then count down again.
Service time 3
Value group Statistics Related FW 1.0.0
Resolution [units] h
Comm object 14400 Related applications all
Description
This is maintenance countdown timer #3. The timer is located in values (group Statistics).
Initial Value is given by the Setpoint Service time 3 (page 262).
Value is decremented while the Controller is running.
The alarm WrnServiceTime is issued as soon as the timer counts down to zero.
When the particular maintenance works have been performed, readjust the appropriate counter again to
the period of next regular maintenance cycle by pressing the Reset button in the Service timer dialog
window in InteliMonitor or by configured display command. The counter will then count down again.
ServiceTimeSd
Value group Statistics Related FW 1.0.0
Resolution [units] h
Comm object 15802 Related applications all
Description
This is maintenance countdown timer #4.
Initial Value is given by Setpoint ServiceTimeSd (page 1).
Value is decremented while the Controller is running. The alarm SdServiceTime is issued as soon as the
timer counts down to zero.
When the particular maintenance works have been performed, readjust the appropriate counter again to the
period of next regular maintenance cycle by pressing the Reset button in the Service timer dialog window in
InteliMonitor or by configured display command. The counter will then count down again.
PulseCounter 2
Value group Statistics Related FW 1.0.0
Resolution [units] -
Comm object 10987 Related applications all
Description
This is the value of PulseCounter #2 module. See the binary input PULSECOUNTER 2 (PAGE 480).
PulseCounter 3
Value group Statistics Related FW 1.0.0
Resolution [units] -
Comm object 10988 Related applications all
Description
This is the value of PulseCounter #3 module. See the binary input PULSECOUNTER 3 (PAGE 480).
PulseCounter 4
Value group Statistics Related FW 1.0.0
Resolution [units] -
Comm object 10989 Related applications all
Description
This is the value of PulseCounter #4 module. See the binary input PULSECOUNTER 4 (PAGE 481).
PulseCounter 5
Value group Statistics Related FW 1.0.0
Resolution [units] -
Comm object 15338 Related applications all
Description
This is the value of PulseCounter #5 module. See the binary input PULSECOUNTER 5 (PAGE 481).
PulseCounter 7
Value group Statistics Related FW 1.0.0
Resolution [units] -
Comm object 15340 Related applications all
Description
This is the value of PulseCounter #7 module. See the binary input PULSECOUNTER 7 (PAGE 482).
PulseCounter 8
Value group Statistics Related FW 1.0.0
Resolution [units] -
Comm object 15341 Related applications all
Description
This is the value of PulseCounter #8 module. See the binary input PULSECOUNTER 8 (PAGE 482).
AFRVlvOffsetA
Value group AFR Control Related FW 1.0.0
Resolution [units] %
Comm object 13570 Related applications all
Description
Required mixer value calculated from characteristic adjusted by Setpoints MixPos1A (page 342),
MixPos2A (page 344), MixPos3A (page 345), MixPos4A (page 347), MixPos5A (page 348).
AFRVlvRegA
Value group AFR Control Related FW 1.0.0
Resolution [units] %
Comm object 13572 Related applications all
Description
Output value from PID regulation as part of general requested Value for MIXPOSA (page 414).
This Value is limited with Setpoint LimPos (page 331).
Value is set to zero when the Sensor Value goes over the SensorValTolA (page 351) for longer time
than TAFROFFA (page 349).
AFRSensReqA
Value group AFR Control Related FW 1.0.0
Resolution [units] Bar/mV/°C
Comm object 10091 Related applications all
Description
Required Sensor Value related to Sensor characteristic adjusted via Setpoints Sensor1A (page 342),
Sensor2A (page 343), Sensor3A (page 345), Sensor4A (page 346), Sensor5A (page 348).
AFRSensActA
Value group AFR Control Related FW 1.0.0
Resolution [units] Bar/mV/°C
Comm object 10093 Related applications all
Description
Actual Value of Sensor. Dimension and range depends on the settings of the LAI: SENSORA (PAGE 431).
MIXFeedbackA
Value group AFR Control Related FW 1.0.0
Resolution [units] %
Comm object 10092 Related applications all
Description
Actual feedback Value of mixer
AFRVlvOffsetB
Value group AFR Control Related FW 1.0.0
Resolution [units] %
Comm object 15022 Related applications all
Description
Required mixer value calculated from characteristic adjusted by Setpoints MixPos1B (page 359),
MixPos2B (page 360), MixPos3B (page 362), MixPos4B (page 363), MixPos5B (page 365).
AFRVlvRegB
Value group AFR Control Related FW 1.0.0
Resolution [units] %
Comm object 15023 Related applications all
Description
Output value from PID regulation as part of general requested Value for MIXPOSB (page 416).
This Value is limited with Setpoint LimPos (page 331).
Value is set to zero when the Sensor Value goes over the SensorValTolB (page 368) for longer time
than TAFROFFB (page 366).
AFRSensReqB
Value group AFR Control Related FW 1.0.0
Resolution [units] Bar/mV/°C
Comm object 15024 Related applications all
Description
Required Sensor Value related to Sensor characteristic adjusted via Setpoints Sensor1B (page 358),
Sensor2B (page 360), Sensor3B (page 361), Sensor4B (page 363), Sensor5B (page 364).
MIXFeedbackB
Value group AFR Control Related FW 1.0.0
Resolution [units] %
Comm object 13140 Related applications all
Description
Actual feedback Value of mixer.
CH4offsetA
Value group AFR Control Related FW 1.0.0
Resolution [units] %
Comm object 15639 Related applications all
Description
This value can be useful in case of needs for extended PLC logic when Ana CH4A (page 354) is set to
ENA-FIX or ENA-STEP mode.
ENA-FIX mode
In this mode will Value show the actual recalculated Value which depends on the analog Value LAI: ANA
CH4A (PAGE 420) and Setpoints: MxPos40%CH4A (page 352) and MxPos60%CH4A (page 353).
Value is visible also when the Controller is running above the LowPwr values.
ENA-STEP mode
In this mode will Value show the actual recalculated Value.
This means:
StartingPosition: LAI: ANA CH4A (PAGE 420) + MxPos40%CH4A (page 352) and
MxPos60%CH4A (page 353)
RunningPosition: (RunPositionA (page 340) - StartPositionA (page 339)) + (LAI: ANA CH4A
(PAGE 420) + MxPos40%CH4A (page 352) and MxPos60%CH4A (page 353))
LowPowerPosition: (LoPwrPositionA (page 341) - StartPositionA (page 339)) + (LAI: ANA CH4A
(PAGE 420) + MxPos40%CH4A (page 352) and MxPos60%CH4A (page 353))
LowPower Value will be shown also when the Controller is running above the LowPwr values.
ENA-FIX mode
In this mode will Value show the actual recalculated Value which depends on the analog Value LAI: ANA
CH4B (PAGE 420) and Setpoints: MxPos40%CH4B (page 369) and MxPos60%CH4B (page 370).
Value is visible also when the Controller is running above the LowPwr values.
ENA-STEP mode
In this mode will Value show the actual recalculated Value.
This means:
StartingPosition: LAI: ANA CH4B (PAGE 420) + MxPos40%CH4B (page 369) and
MxPos60%CH4B (page 370)
RunningPosition: (RunPositionB (page 357) - StartPositionB (page 355)) + (LAI: ANA CH4B
(PAGE 420) + MxPos40%CH4B (page 369) and MxPos60%CH4B (page 370))
LowPowerPosition: (LoPwrPositionB (page 357) - StartPositionB (page 355)) + (LAI: ANA CH4B
(PAGE 420) + MxPos40%CH4B (page 369) and MxPos60%CH4B (page 370))
LowPower Value will be shown also when the Controller is running above the LowPwr values.
For full list of Logical analog inputs go to the chapter List of LAI (page 419).
6 back to Controller objects
Cold temp 2
Related FW 1.0.0 Related applications
Description
If there is an additional terminal board between a thermocouple and the IS-AIN8 module and there is a
significant temperature difference between this terminal board and the module, it is necessary to
measure the temperature at this terminal board and use this temperature for the thermocouple
compensation instead of the internal temperature of the module.
This analog input is intended for measuement of this thermocouple compensation temperature for the IS-
AIN8 module with index #2.
Note: Thermocouples without internal compensation "Thermo(nc)..." must be used for this case.
Cold temp 3
Related FW 1.0.0 Related applications
Description
If there is an additional terminal board between a thermocouple and the IS-AIN8 module and there is a
significant temperature difference between this terminal board and the module, it is necessary to
measure the temperature at this terminal board and use this temperature for the thermocouple
compensation instead of the internal temperature of the module.
This analog input is intended for measuement of this thermocouple compensation temperature for the IS-
AIN8 module with index #3.
Note: Thermocouples without internal compensation "Thermo(nc)..." must be used for this case.
Cyl temp 1
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #1. Used for computing of values T Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 2
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #2. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 3
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #3. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 4
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #4. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 5
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #5. Used for computing of values T Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 6
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #6. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 7
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #7. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 8
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #8. Used for computing of values T Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 9
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #9. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 11
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #11. Used for computing of valuesT Cyl aver (page 391)
Note: Available in IS-NT only.
Cyl temp 12
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #12. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 13
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #13. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 14
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #14. Used for computing of values T Cyl aver (page 391),
T Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 16
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #16. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 17
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #17. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 18
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #18. Used for computing of values T Cyl aver (page 391),
T Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 19
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #19. Used for computing of values T Cyl aver (page 391),
T Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 21
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #21. Used for computing of values T Cyl aver (page 391),
T Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 22
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #22. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 23
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #23. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 24
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #24. Used for computing of values T Cyl aver (page 391),
T Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 26
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #26. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 27
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #27. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 28
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #28. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 29
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #29. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 31
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #31. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Cyl temp 32
Related FW 1.0.0 Related applications
Description
Logical analog input for cylinder temperature #32. Used for computing of valuesT Cyl aver (page 391), T
Cyl max (page 391), T Cyl min (page 391).
Note: Available in IS-NT only.
Engine Torque
Related FW 1.0.0 Related applications
Description
Input for external torque measurement from which the total instantaneous mechanical power is calculated in
the controller.
The calculation formula to which the logic input is connected assumes an analog value in Nm (newton
meter).
Engine Torque%
Related FW 1.0.0 Related applications
Description
Input for external torque measurement from which the total instantaneous mechanical power is calculated in
the controller.
The input analog value is in % (percent) - it is a relative number relative to the torque reference of the motor
(possible to use maximum torque).
For use in a power formula, this relative input needs to be recalculated (the formula counts with units of Nm).
We will use the setpoint RefEngTorque for the conversion.
, where
M(rel) = LAI Engine Torque%
RefEngTorq = setpoint
LAI: L
LCD brightness
Related FW 1.0.0 Related applications
Description
This functional input is used to adjust the backlight intensity of the IG-NT built-in terminal (display) by an
analog input (e.g. a potentiometer). If this input is configured to a physical analog input or other value, the
brightness adjusted by buttons at the terminal is overriden by this analog input.
MAT B
Related FW 1.0.0 Related applications
Description
This functional input is used for AFR functionality.
MAT is second condition for correct configuration of AFR functionality.
IMPORTANT: In case this sensor is not configured alarm message AFRcontrolFLS is
activated.
LAI: O
Oil press
Related FW 1.0.0 Related applications
Description
This functional input is used as an additional information whether the engine is running or not. If you want
to use this additional feature configure this input onto the physical analog input where the oil pressure
sensor is connected and adjust the setpoint Starting POil (page 234) to cca 50 % of typical engine oil
pressure at idle speed.
Note: See also the chapter Engine control (page 136) for more details.
LAI: R
Requested RPM
Related FW 1.0.0 Related applications
Description
Analog input influences directly Speed request (page 1) register when configured without ramp. In the case
of sensor fail (out of range) is Speed request = 0.0 % for and 50.0 % (=Nominal RPM) for . There is expected
range of values 0.0 … 100.0 % for this Logical Analog input.
LAI: S
SensorA
Related FW 1.0.0 Related applications all
Description
This functional input is used for AFR functionality.
With using AFR functionality is requirement to configure type of Sensor.
Defaultly can be choosen from Bar, mV, °C type of sensor.
His configuration has an influence on format of all Setpoints or Values which are related to this LAI.
Example: Sensor1A (page 342), Sensor1B (page 358), SensorValTolA (page 351),
SensorValTolB (page 368), MATcorrection (page 333), DeadBand (page 335).
SensorB
Related FW 1.0.0 Related applications
Description
This functional input is used for AFR functionality.
With using AFR functionality is requirement to configure type of Sensor.
Defaultly can be choosen from Bar, mV, °C type of sensor.
His configuration has an influence on format of all Setpoints or Values which are related to this LAI.
Example: Sensor1A (page 342), Sensor1B (page 358), SensorValTolA (page 351),
SensorValTolB (page 368), MATcorrection (page 333), DeadBand (page 335).
For full list of Logical binary inputs go to the chapter List of LBI (page 433).
6 back to Controller objects
AccessLock D#3
Related FW 1.0.0 Related applications all
Description
This input forces the external local terminal or IntelliVision (display) #3 into monitoring mode.
Note: Local display means that it is connected to dedicated RS485. There is possibility to connect up to
external displays via dedicated RS485 terminal to InteliDrive BaseBox.
AccessLock ext
Related FW 1.0.0 Related applications all
Description
This input forces all external remote terminals into monitoring mode.
Setpoints changes are disabled.
Executing commands is disabled.
Change of controller mode is disabled.
An external remote terminal is any device, which reads and/or writes data from/into the controller and is
connected to the controller via any other communication bus than the dedicated terminal RS485 bus.
Note: An example of such terminal is a PC with InteliMonitor, any kind of remote display connected via
CAN2 or a PLC connected to the RS485 and communicating via MODBUS.
LBI: C
ClutchBlocking
Related FW 1.0.0 Related applications Allspeed
Description
ClutchBlocking can block Clutch Connect. Active input is indicated in Alarm list as “Clutch Blocking”
message.
CtrlHBeat sens
Related FW 1.0.0 Related applications all
Description
This input is used at a redundant controller to sense the "heart beat" from the main controller. The input is
to be connected to the output CTRL HEART BEAT (PAGE 508) of the main controller.
If the redundant controller does not sense the heart beat from the main one, it will activate the binary
output CTRL HBEAT FD (PAGE 508), which has to be wired such a way, that it disconnects the dead main
controller from the Controller, connects the redundant controller instead and activates it.
Note: Learn more about redundancy in separate chapter Controller redundancy (page 142).
CylDifEvalBlk
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily evaluation of the alarms caused by cylinder temperatures
deviations.
LBI: D
DxLoadReduct
Related FW 1.2.0 Related applications all
Description
Input activates engine knocking protection.
LBI: E
ECUComFailBlck
Related FW 1.0.0 Related applications all
Description
The input disables issuing of the ECU communication failure alarm and all other alarms related to values
that are beeing read from the ECU.
ECU StoppedEng
Related FW 1.0.0 Related applications all
Description
When this input is activated, the Controller will be stopped immdiately without unloading and cooling
phase, however no alarm will be issued.
This input is intended for situations, where the Controller is controller by an ECU or other device which
also includes engine protections and can stop the engine itself. In such case the controller would issue
an Underspeed alarm. Connecting this input to an appropriate ECU output, which provides information,
that the engine has been stopped by the ECU, prevents the controller from issuing the underspeed alarm.
Logical Binary Outputs that are deactivated (directly or indirectly) when Emerg. manual is active:
Starter
Fuel solenoid
Prestart
Cooling pump
Stop solenoid
Stop pulse
Speed up
Speed dn
AVR up
AVR dn
Ignition
Ventilation
Idle/Nominal
Prelubr pump
ECU PwrRelay
Ready for load
Stand-by ready
Operational
Ready
Not Ready
CranckProcedure
Starting
Idle run
Running
Cooling
Stopping
Crancking
Emergency Stop
Related FW 1.0.0 Related applications all
Description
If the input is activated, engine shutdown is immediately performed. However, the controller behavior is
slightly different compared to other shutdown alarms:
Outputs IGNITION (PAGE 512), VENTILATION (PAGE 566), COOLING PUMP (PAGE 506) and PRELUBR
PUMP (PAGE 551) are deactivated as well.
This input cannot be overridden with the input SD OVERRIDE (PAGE 484).
Note: Because of safety reasons it is recommended to configure this input as Normally closed and use a
NC switch.
ExValue1 up
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 1 is continuously beeing increased at the rate of ExValue1
rate (page 294) until it reaches ExValue1HiLim (page 288).
Note: If this input is used (configured), the ExValue 1 can't be written remotely from a remote terminal using
the command ExValue 1.
Note: If this input is used (configured), the ExValue 2 can't be written remotely from a remote terminal using
the command ExValue 2.
ExValue3 up
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 3 is continuously being increased at the rate of ExValue3 rate
(page 295) until it reaches ExValue3HiLim (page 289).
Note: If this input is used (configured), the ExValue 3 can't be written remotely from a remote terminal
using the command ExValue 3.
ExValue4 up
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 4 is continuously being increased at the rate of ExValue4
rate (page 295) until it reaches ExValue4HiLim (page 289).
Note: If this input is used (configured), the ExValue 4 can't be written remotely from a remote terminal
using the command ExValue 4.
ExValue5 up
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 5 is continuously being increased at the rate of ExValue5
rate (page 296) until it reaches ExValue5HiLim (page 290).
Note: If this input is used (configured), the ExValue 5 can't be written remotely from a remote terminal
using the command ExValue 5.
ExValue7 up
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 7 is continuously being increased at the rate of ExValue7 rate
(page 297) until it reaches ExValue7HiLim (page 291).
If this input is used (configured), the ExValue 7 can't be written remotely from a remote terminal using the
command ExValue 7.
ExValue8 up
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 8 is continuously being increased at the rate of ExValue8 rate
(page 297) until it reaches ExValue8HiLim (page 291).
If this input is used (configured), the ExValue 8 can't be written remotely from a remote terminal using the
command ExValue 8.
ExValue9 up
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 9 is continuously being increased at the rate of ExValue9 rate
(page 298) until it reaches ExValue9HiLim (page 292).
If this input is used (configured), the ExValue 9 can't be written remotely from a remote terminal using the
command ExValue 9.
ExValue10 up
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 10 is continuously being increased at the rate of
ExValue10 rate (page 298) until it reaches ExValue10HiLim (page 292).
Note: If this input is used (configured), the ExValue 10 can't be written remotely from a remote terminal
using the command ExValue 10.
ExValue11 up
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 11 is continuously being increased at the rate of
ExValue11 rate (page 299) until it reaches ExValue11HiLim (page 293).
Note: If this input is used (configured), the ExValue 11 can't be written remotely from a remote terminal
using the command ExValue 11.
ExValue12 up
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 12 is continuously being increased at the rate of
ExValue12 rate (page 299) until it reaches ExValue12HiLim (page 293).
Note: If this input is used (configured), the ExValue 12 can't be written remotely from a remote terminal
using the command ExValue 12.
ExValue1 down
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 1 is continuously beeing decreased at the rate of ExValue1
rate (page 294) until it reaches ExValue1LoLim (page 282).
Note: If this input is used (configured), the ExValue 1 can't be written remotely from a remote terminal using
the command ExValue 1.
ExValue2 down
Related FW 1.0.0 Related applications all
Description
IS-NT specific function
While this input is active the value of ExValue 2 is continuously beeing decreased at the rate of ExValue2
rate (page 294) until it reaches ExValue2LoLim (page 282).
Note: If this input is used (configured), the ExValue 2 can't be written remotely from a remote terminal using
the command ExValue 2.
ExValue4 down
Related FW 1.0.0 Related applications all
Description
While this input is active the value of ExValue 4 is continuously beeing decreased at the rate of ExValue4
rate (page 295) until it reaches ExValue4LoLim (page 283).
Note: If this input is used (configured), the ExValue 4 can't be written remotely from a remote terminal
using the command ExValue 4.
ExValue5 down
Related FW 1.0.0 Related applications all
Description
IS-NT specific function
While this input is active the value of ExValue 5 is continuously being decreased at the rate of ExValue5
rate (page 296) until it reaches ExValue5LoLim (page 284).
Note: If this input is used (configured), the ExValue 5 can't be written remotely from a remote terminal using
the command ExValue 5.
ExValue6 down
Related FW 1.0.0 Related applications all
Description
IS-NT specific function
While this input is active the value of ExValue 6 is continuously being decreased at the rate of ExValue6
rate (page 296) until it reaches ExValue6LoLim (page 284).
Note: If this input is used (configured), the ExValue 6 can't be written remotely from a remote terminal using
the command ExValue 6.
Note: If this input is used (configured), the ExValue 7 can't be written remotely from a remote terminal using
the command ExValue 7.
ExValue8 down
Related FW 1.0.0 Related applications all
Description
IS-NT specific function
While this input is active the value of ExValue 8 is continuously being decreased at the rate of ExValue8
rate (page 297) until it reaches ExValue8LoLim (page 285).
Note: If this input is used (configured), the ExValue 8 can't be written remotely from a remote terminal using
the command ExValue 8.
ExValue9 down
Related FW 1.0.0 Related applications all
Description
IS-NT specific function
While this input is active the value of ExValue 9 is continuously being decreased at the rate of ExValue9
rate (page 298) until it reaches ExValue9LoLim (page 286).
Note: If this input is used (configured), the ExValue 9 can't be written remotely from a remote terminal using
the command ExValue 9.
ExValue10 down
Related FW 1.0.0 Related applications all
Description
IS-NT specific function
While this input is active the value of ExValue 10 is continuously being decreased at the rate of ExValue10
rate (page 298) until it reaches ExValue10LoLim (page 286).
Note: If this input is used (configured), the ExValue 10 can't be written remotely from a remote terminal
using the command ExValue 10.
Note: If this input is used (configured), the ExValue 11 can't be written remotely from a remote terminal
using the command ExValue 11.
ExValue12 down
Related FW 1.0.0 Related applications all
Description
IS-NT specific function
While this input is active the value of ExValue 12 is continuously being decreased at the rate of ExValue12
rate (page 299) until it reaches ExValue12LoLim (page 287).
Note: If this input is used (configured), the ExValue 12 can't be written remotely from a remote terminal
using the command ExValue 12.
ExValue1reset
Related FW 1.0.0 Related applications all
Description
The ExValue 1 is reset to it's default value when this input is activated and held there until the input is
deactivated. The default value is given by the setpoint ExValue1deflt (page 300).
While the reset input is active:
The value does not respond to up and down inputs.
The value does not accept new data that are written remotely from a remote terminal using the
ExValue command.
Note: Configuring of the reset input does not block writing the ExValue remotely, in comparison to the up
and down inputs, which does. However, if the reset input is active, the remotely written data are not
accepted.
ExValue3reset
Related FW 1.0.0 Related applications all
Description
The ExValue 3 is reset to it's default value when this input is activated and held there until the input is
deactivated. The default value is given by the setpoint ExValue3deflt (page 301).
While the reset input is active:
The value does not respond to up and down inputs.
The value does not accept new data that are written remotely from a remote terminal using the
ExValue command.
Note: Configuring of the reset input does not block writing the ExValue remotely, in comparison to the up
and down inputs, which does. However, if the reset input is active, the remotely written data are not
accepted.
ExValue4reset
Related FW 1.0.0 Related applications all
Description
The ExValue 4 is reset to it's default value when this input is activated and held there until the input is
deactivated. The default value is given by the setpoint ExValue4deflt (page 301).
While the reset input is active:
The value does not respond to up and down inputs.
The value does not accept new data that are written remotely from a remote terminal using the
ExValue command.
Note: Configuring of the reset input does not block writing the ExValue remotely, in comparison to the up
and down inputs, which does. However, if the reset input is active, the remotely written data are not
accepted.
ExValue6reset
Related FW 1.0.0 Related applications all
Description
The ExValue 6 is reset to it's default value when this input is activated and held there until the input is
deactivated. The default value is given by the setpoint ExValue6deflt (page 302).
While the reset input is active:
The value does not respond to up and down inputs.
The value does not accept new data that are written remotely from a remote terminal using the
ExValue command.
Note: Configuring of the reset input does not block writing the ExValue remotely, in comparison to the up
and down inputs, which does. However, if the reset input is active, the remotely written data are not
accepted.
ExValue7reset
Related FW 1.0.0 Related applications all
Description
The ExValue 7 is reset to it's default value when this input is activated and held there until the input is
deactivated. The default value is given by the setpoint ExValue7deflt (page 303).
While the reset input is active:
The value does not respond to up and down inputs.
The value does not accept new data that are written remotely from a remote terminal using the
ExValue command.
Note: Configuring of the reset input does not block writing the ExValue remotely, in comparison to the up
and down inputs, which does. However, if the reset input is active, the remotely written data are not
accepted.
ExValue9reset
Related FW 1.0.0 Related applications all
Description
The ExValue 9 is reset to it's default value when this input is activated and held there until the input is
deactivated. The default value is given by the setpoint ExValue9deflt (page 304).
While the reset input is active:
The value does not respond to up and down inputs.
The value does not accept new data that are written remotely from a remote terminal using the
ExValue command.
Note: Configuring of the reset input does not block writing the ExValue remotely, in comparison to the up
and down inputs, which does. However, if the reset input is active, the remotely written data are not
accepted.
ExValue10reset
Related FW 1.0.0 Related applications all
Description
The ExValue 10 is reset to it's default value when this input is activated and held there until the input is
deactivated. The default value is given by the setpoint ExValue10deflt (page 304).
While the reset input is active:
The value does not respond to up and down inputs.
The value does not accept new data that are written remotely from a remote terminal using the
ExValue command.
Note: Configuring of the reset input does not block writing the ExValue remotely, in comparison to the up
and down inputs, which does. However, if the reset input is active, the remotely written data are not
accepted.
ExValue12reset
Related FW 1.0.0 Related applications all
Description
The ExValue 12 is reset to it's default value when this input is activated and held there until the input is
deactivated. The default value is given by the setpoint ExValue12deflt (page 305).
While the reset input is active:
The value does not respond to up and down inputs.
The value does not accept new data that are written remotely from a remote terminal using the
ExValue command.
Note: Configuring of the reset input does not block writing the ExValue remotely, in comparison to the up
and down inputs, which does. However, if the reset input is active, the remotely written data are not
accepted.
LBI: F
FaultResButton
Related FW 1.0.0 Related applications all
Description
This input is used for an external FAULT RESET button mounted on the switchboard. The function of the
input is identical as function of the fault reset button on the controller front panel.
The input is enabled only if the setpoint Local buttons (page 204) is set to position EXTBUTTONS or
BOTH.
Force block 1
Related FW 1.0.0 Related applications all
Description
This is one of three binary inputs used for user-defined blocking of protections. If the input is active, all
the protections that have Protection block type configured as Force block 1 block type are blocked (i.e.
temporarily disabled).
Force block 2
Related FW 1.0.0 Related applications all
Description
This is one of three binary inputs used for user-defined blocking of protections. If the input is active, all
the protections that have Protection block type configured as Force block 2 block type are blocked (i.e.
temporarily disabled).
Force block 3
Related FW 1.0.0 Related applications all
Description
This is one of three binary inputs used for user-defined blocking of protections. If the input is active, all
the protections that have Protection block type configured as Force block 3 block type are blocked (i.e.
temporarily disabled).
Force block 4
Related FW 1.0.0 Related applications all
Description
This is one of three binary inputs used for user-defined blocking of protections. If the input is active, all
the protections that have Protection block type configured as Force block 4 block type are blocked (i.e.
temporarily disabled).
Force block 6
Related FW 1.0.0 Related applications all
Description
This is one of three binary inputs used for user-defined blocking of protections. If the input is active, all
the protections that have Protection block type configured as Force block 6 block type are blocked (i.e.
temporarily disabled).
Note: Watch a training video about force value function here: https://www.comap-
control.com/training/online-training.
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn 3
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #3 block. If the input is active, the value of the setpoint, to which the
Force value #3 block is configured, will be overriden by value of the alternative setpoint assigned to the
Force value #3 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn 4
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #4 block. If the input is active, the value of the setpoint, to which the
Force value #4 block is configured, will be overriden by value of the alternative setpoint assigned to the
Force value #4 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn 5
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #5 block. If the input is active, the value of the setpoint, to which the
Force value #5 block is configured, will be overriden by value of the alternative setpoint assigned to the
Force value #5 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn 6
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #6 block. If the input is active, the value of the setpoint, to which the
Force value #6 block is configured, will be overriden by value of the alternative setpoint assigned to the
Force value #6 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn 8
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #8 block. If the input is active, the value of the setpoint, to which the
Force value #8 block is configured, will be overriden by value of the alternative setpoint assigned to the
Force value #8 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn 9
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #9 block. If the input is active, the value of the setpoint, to which the
Force value #9 block is configured, will be overriden by value of the alternative setpoint assigned to the
Force value #9 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn10
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #10 block. If the input is active, the value of the setpoint, to which
the Force value #10 block is configured, will be overriden by value of the alternative setpoint assigned to
the Force value #10 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn11
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #11 block. If the input is active, the value of the setpoint, to which
the Force value #11 block is configured, will be overriden by value of the alternative setpoint assigned to
the Force value #11 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn13
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #13 block. If the input is active, the value of the setpoint, to which
the Force value #13 block is configured, will be overriden by value of the alternative setpoint assigned to
the Force value #13 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn14
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #14 block. If the input is active, the value of the setpoint, to which
the Force value #14 block is configured, will be overriden by value of the alternative setpoint assigned to
the Force value #14 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn15
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #15 block. If the input is active, the value of the setpoint, to which
the Force value #15 block is configured, will be overriden by value of the alternative setpoint assigned to
the Force value #15 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn16
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #16 block. If the input is active, the value of the setpoint, to which
the Force value #16 block is configured, will be overriden by value of the alternative setpoint assigned to
the Force value #16 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn18
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #18 block. If the input is active, the value of the setpoint, to which
the Force value #18 block is configured, will be overridden by value of the alternative setpoint assigned to
the Force value #18 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn19
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #19 block. If the input is active, the value of the setpoint, to which
the Force value #19 block is configured, will be overridden by value of the alternative setpoint assigned to
the Force value #19 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn20
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #20 block. If the input is active, the value of the setpoint, to which
the Force value #20 block is configured, will be overridden by value of the alternative setpoint assigned to
the Force value #20 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn21
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #21 block. If the input is active, the value of the setpoint, to which
the Force value #21 block is configured, will be overridden by value of the alternative setpoint assigned to
the Force value #21 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn23
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #23 block. If the input is active, the value of the setpoint, to which
the Force value #23 block is configured, will be overridden by value of the alternative setpoint assigned to
the Force value #23 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn24
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #24 block. If the input is active, the value of the setpoint, to which
the Force value #24 block is configured, will be overridden by value of the alternative setpoint assigned to
the Force value #24 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn25
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #16 block. If the input is active, the value of the setpoint, to which
the Force value #25 block is configured, will be overridden by value of the alternative setpoint assigned to
the Force value #25 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn26
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #26 block. If the input is active, the value of the setpoint, to which
the Force value #26 block is configured, will be overriden by value of the alternative setpoint assigned to
the Force value #26 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn28
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #28 block. If the input is active, the value of the setpoint, to which
the Force value #28 block is configured, will be overriden by value of the alternative setpoint assigned to
the Force value #28 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn29
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #29 block. If the input is active, the value of the setpoint, to which
the Force value #29 block is configured, will be overriden by value of the alternative setpoint assigned to
the Force value #29 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn30
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #30 block. If the input is active, the value of the setpoint, to which
the Force value #30 block is configured, will be overriden by value of the alternative setpoint assigned to
the Force value #30 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
ForceValueIn31
Related FW 1.0.0 Related applications all
Description
This input activates the Force value #31 block. If the input is active, the value of the setpoint, to which
the Force value #31 block is configured, will be overriden by value of the alternative setpoint assigned to
the Force value #31 block.
Note: If there are more than one force value blocks configured onto one setpoint then the highest priority
has the block with the lowest index (i.e. the first active block according to the list displayed in GenConfig
in the Force value window at the related setpoint).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
Note: See an example in the description of the binary input FORCEVALUEIN 1 (PAGE 452).
LBI: G
GasAB
Related FW 1.0.0 Related applications all
Description
Input is used for selection of gas types. With activation of this input controller will work with Setpoints
from AFR MIX B group.
GasVTestOK
Related FW 1.0.0 Related applications all
Description
Binary input from Gas Valve test unit that indicates OK result of Gas valve test.
LBI: H
HornResButton
Related FW 1.0.0 Related applications all
Description
This input is used for an external HORN RESET button mounted on the switchboard. The function of the
input is identical as function of the horn reset button on the controller front panel.
The input is enabled only if the setpoint Local buttons (page 204) is set to position EXTBUTTONS or
BOTH.
IssueActCallC2
Related FW 1.0.0 Related applications all
Description
This input forces the controller to issue an active call/e-mail/SMS via the channel #2. Type of the channel
is to be adjusted by the setpoint AcallCH2-Type (page 318).
This input can be used to inform a remote user about a specific non-alarm situation, e.g. mains failure
and/or mains return:
1. Select a binary signal in the controller, which indicates, that the particular situation occurred, about
which you want to be informed remotely. There are many predefined binary information provided
directly by the controller or use PLC functions to create the desired binary signal.
2. Configure an universal protection block to the binary signal mentioned above and select protection
type AL indication.
3. Configure the binary signal mentioned above onto the logical binary input IssueActCallC2.
IssueActCallC4
Related FW 1.0.0 Related applications all
Description
This input forces the controller to issue an active call/e-mail/SMS via the channel #4. Type of the channel
is to be adjusted by the setpoint AcallCH4-Type (page 320).
This input can be used to inform a remote user about a specific non-alarm situation, e.g. mains failure
and/or mains return:
1. Select a binary signal in the controller, which indicates, that the particular situation occurred, about
which you want to be informed remotely. There are many predefined binary information provided
directly by the controller or use PLC functions to create the desired binary signal.
2. Configure an universal protection block to the binary signal mentioned above and select protection
type AL indication.
3. Configure the binary signal mentioned above onto the logical binary input IssueActCallC4.
IssueActCallC5
Related FW 1.0.0 Related applications all
Description
This input forces the controller to issue an active call/e-mail/SMS via the channel #5. Type of the channel
is to be adjusted by the setpoint AcallCH5-Type (page 320).
This input can be used to inform a remote user about a specific non-alarm situation, e.g. mains failure
and/or mains return:
1. Select a binary signal in the controller, which indicates, that the particular situation occurred, about
which you want to be informed remotely. There are many predefined binary information provided
directly by the controller or use PLC functions to create the desired binary signal.
2. Configure an universal protection block to the binary signal mentioned above and select protection
type AL indication.
3. Configure the binary signal mentioned above onto the logical binary input IssueActCallC5.
ImpCountSet1
Related FW 1.0.0 Related applications all
Description
This input sets the actual value of PulseCounter 1PulseCounter (page 413) to the Value given by
Setpoint ImpCountDef1 (page 213).
ImpCountSet2
Related FW 1.0.0 Related applications all
Description
This input sets the actual value of PulseCounter 2 (page 413) to the Value given by Setpoint
ImpCountDef2 (page 213).
ImpCountSet3
Related FW 1.0.0 Related applications all
Description
This input sets the actual value of PulseCounter 3 (page 413) to the Value given by Setpoint
ImpCountDef3 (page 214).
ImpCountSet4
Related FW 1.0.0 Related applications all
Description
This input sets the actual value of PulseCounter 4 (page 413) to the Value given by Setpoint
ImpCountDef4 (page 214).
ImpCountSet5
Related FW 1.0.0 Related applications all
Description
This input sets the actual value of PulseCounter 5 (page 413) to the Value given by Setpoint
ImpCountDef5 (page 215).
ImpCountSet6
Related FW 1.0.0 Related applications all
Description
This input sets the actual value of PulseCounter 6 (page 414) to the Value given by Setpoint
ImpCountDef6 (page 215).
ImpCountSet8
Related FW 1.0.0 Related applications all
Description
This input sets the actual value of PulseCounter 8 (page 414) to the Value given by Setpoint
ImpCountDef8 (page 216).
LBI: L
Lang sel int A
Related FW 1.0.0 Related applications all
Description
This is one of three binary inputs LANG SEL INT A (PAGE 469), LANG SEL INT B (PAGE 470), LANG SEL
INT C (PAGE 471), used for selecting language of the terminal (display) #1, which is supposed to be
directly attached to the controller or mounted close to it.
Note: Using these inputs for language selection is an option only. If the inputs are not configured, the
language can be selected using the menus on the terminal.
Note: "0" in the table means the input is not active or not configured.
Note: Language index 0 selects the default language of the terminal, i.e. the language, which is adjusted
in the terminal using it's menus.
Note: The reaction on changes of these inputs is delayed about 1 sec to ensure the new combination is
valid (e.g. if a rotary selector switch is used).
IMPORTANT: Each language change causes the reinitialization of the display. Function of
the controller is not influenced.
Note: "0" in the table means the input is not active or not configured.
Note: Language index 0 selects the default language of the terminal, i.e. the language, which is adjusted
in the terminal using it's menus.
Note: The reaction on changes of these inputs is delayed about 1 sec to ensure the new combination is
valid (e.g. if a rotary selector switch is used).
IMPORTANT: Each language change causes the reinitialization of the display. Function of
the controller is not influenced.
Note: "0" in the table means the input is not active or not configured.
Note: Language index 0 selects the default language of the terminal, i.e. the language, which is adjusted
in the terminal using it's menus.
Note: The reaction on changes of these inputs is delayed about 1 sec to ensure the new combination is
valid (e.g. if a rotary selector switch is used).
IMPORTANT: Each language change causes the reinitialization of the display. Function of
the controller is not influenced.
Note: "0" in the table means the input is not active or not configured.
Note: Language index 0 selects the default language of the terminal, i.e. the language, which is adjusted
in the terminal using it's menus.
Note: The reaction on changes of these inputs is delayed about 1 sec to ensure the new combination is
valid (e.g. if a rotary selector switch is used).
IMPORTANT: Each language change causes the reinitialization of the display. Function of
the controller is not influenced.
Note: "0" in the table means the input is not active or not configured.
Note: Language index 0 selects the default language of the terminal, i.e. the language, which is adjusted
in the terminal using it's menus.
Note: The reaction on changes of these inputs is delayed about 1 sec to ensure the new combination is
valid (e.g. if a rotary selector switch is used).
IMPORTANT: Each language change causes the reinitialization of the display. Function of
the controller is not influenced.
Note: "0" in the table means the input is not active or not configured.
Note: Language index 0 selects the default language of the terminal, i.e. the language, which is adjusted
in the terminal using it's menus.
Note: The reaction on changes of these inputs is delayed about 1 sec to ensure the new combination is
valid (e.g. if a rotary selector switch is used).
IMPORTANT: Each language change causes the reinitialization of the display. Function of
the controller is not influenced.
Note: "0" in the table means the input is not active or not configured.
Note: Language index 0 selects the default language of the terminal, i.e. the language, which is adjusted
in the terminal using it's menus.
Note: The reaction on changes of these inputs is delayed about 1 sec to ensure the new combination is
valid (e.g. if a rotary selector switch is used).
IMPORTANT: Each language change causes the reinitialization of the display. Function of
the controller is not influenced.
Note: "0" in the table means the input is not active or not configured.
Note: Language index 0 selects the default language of the terminal, i.e. the language, which is adjusted
in the terminal using it's menus.
Note: The reaction on changes of these inputs is delayed about 1 sec to ensure the new combination is
valid (e.g. if a rotary selector switch is used).
IMPORTANT: Each language change causes the reinitialization of the display. Function of
the controller is not influenced.
Note: "0" in the table means the input is not active or not configured.
Note: Language index 0 selects the default language of the terminal, i.e. the language, which is adjusted
in the terminal using it's menus.
Note: The reaction on changes of these inputs is delayed about 1 sec to ensure the new combination is
valid (e.g. if a rotary selector switch is used).
IMPORTANT: Each language change causes the reinitialization of the display. Function of
the controller is not influenced.
Loaded
Related FW 1.0.0 Related applications all
Description
Binary input function for loaded engine indication.
LBI: M
Misfiring
Related FW 1.2.0 Related applications all
Description
Misfiring binary input activates engine misfiring protection.
Misfiring is detected from external misfiring unit.
start engine unloading after MisfLdRed del (page 336) with rate given by Load Ramp to Value Min
Power PtM.
Note: Wrn Misfire and LOP MisfLdRed is activated
Activates engine slow stop after delay given by Setpoint Misfiring del (page 336).
Engine shut down is activated in case the Misfiring unload protection is activated 5 times in one hour.
The internal counter is reseted after one hour without any Misfiring activation or after engine Stop.
MICFaultReset
Related FW 1.0.0 Related applications all
Description
Fault reset function specially designed for ignition controllers MIC. The rising edge of the input signal
activates the reset sequence through electronic communication. A confirmation command 6 is sent for 1
second and then command 5 is sent for another 1 second. When the timer expires, zero is sent again. Works
in conjunction with the ECU MIC.
LBI: O
Oil press
Related FW 1.0.0 Related applications all
Description
This input is to be configured to the physical binary input where engine oil pressure binary sensor is
connected. It provides following alarms:
The input must not be active at stopped engine. If it is active, the controller issues Sd Oil press B
alarm.
The input must be active at running engine at latest in the moment when the alarm blocking delay
RunOnlyBlkDel1 (page 248) has elapsed. If it is not active, the controller issues Sd Oil press B
alarm.
Note: If you use this logical binary input you do not need to configure any other protection onto the
respective physical binary input.
LBI: P
PrestartBypass
Related FW 1.0.0 Related applications all
Description
Use this input to bypass the prestart phase of the start-up procedure and activate the STARTER (PAGE
555) output immediately after start command has been issued.
This input is typically used to skip preglowing of the engine when the engine is already warm. A built-in
PLC module Comparator with hysteresis attached to the engine temperature value can be used to
provide the "engine warm" binary signal, which is then internally configured onto this logical binary input.
Note: The counter value can be reset in the InteliMonitor statistics window.
PulseCounter 2
Related FW 1.0.0 Related applications all
Description
This is the input of the PulseCounter #2 module. The module counts pulses at the input and if the input
pulses counter reaches value given by the setpoint ConvCoefPulse2 (page 209), the counter value
PulseCounter 2 (page 413) (in the group Statistic) is increased by 1 and input pulses conter is reset to
0. Both counter value and input pulses counter are stored in the nonvolatile memory.
The PulseCounter modules are intended e.g. for connecting external energy or fuel meters with pulse
outputs.
Note: Minimal pulse width as well as minimal pause between two succesive pulses is 100ms.
Note: The counter value can be reset in the InteliMonitor statistics window.
PulseCounter 3
Related FW 1.0.0 Related applications all
Description
This is the input of the PulseCounter #3 module. The module counts pulses at the input and if the input
pulses counter reaches value given by the setpoint ConvCoefPulse3 (page 210), the counter value
PulseCounter 3 (page 413) (in the group Statistic) is increased by 1 and input pulses conter is reset to
0. Both counter value and input pulses counter are stored in the nonvolatile memory.
The PulseCounter modules are intended e.g. for connecting external energy or fuel meters with pulse
outputs.
Note: Minimal pulse width as well as minimal pause between two succesive pulses is 100ms.
Note: The counter value can be reset in the InteliMonitor statistics window.
Note: The counter value can be reset in the InteliMonitor statistics window.
PulseCounter 5
Related FW 1.0.0 Related applications all
Description
This is the input of the PulseCounter #5 module. The module counts pulses at the input and if the input
pulses counter reaches value given by the setpoint ConvCoefPulse5 (page 211), the counter value
PulseCounter 5 (page 413) (in the group Statistic) is increased by 1 and input pulses conter is reset to
0. Both counter value and input pulses counter are stored in the nonvolatile memory.
The PulseCounter modules are intended e.g. for connecting external energy or fuel meters with pulse
outputs.
Note: Minimal pulse width as well as minimal pause between two succesive pulses is 100ms.
Note: The counter value can be reset in the InteliMonitor statistics window.
PulseCounter 6
Related FW 1.0.0 Related applications all
Description
This is the input of the PulseCounter #6 module. The module counts pulses at the input and if the input
pulses counter reaches value given by the setpoint ConvCoefPulse6 (page 211), the counter value
PulseCounter 6 (page 414) (in the group Statistic) is increased by 1 and input pulses conter is reset to
0. Both counter value and input pulses counter are stored in the nonvolatile memory.
The PulseCounter modules are intended e.g. for connecting external energy or fuel meters with pulse
outputs.
Note: Minimal pulse width as well as minimal pause between two succesive pulses is 100ms.
Note: The counter value can be reset in the InteliMonitor statistics window.
Note: The counter value can be reset in the InteliMonitor statistics window.
PulseCounter 8
Related FW 1.0.0 Related applications all
Description
This is the input of the PulseCounter #8 module. The module counts pulses at the input and if the input
pulses counter reaches value given by the setpoint ConvCoefPulse8 (page 212), the counter value
PulseCounter 8 (page 414) (in the group Statistic) is increased by 1 and input pulses conter is reset to
0. Both counter value and input pulses counter are stored in the nonvolatile memory.
The PulseCounter modules are intended e.g. for connecting external energy or fuel meters with pulse
outputs.
Note: Minimal pulse width as well as minimal pause between two succesive pulses is 100ms.
Note: The counter value can be reset in the InteliMonitor statistics window.
LBI: R
Rem Clutch
Related FW 1.0.0 Related applications all
Description
If active closes binary output Clutch Connect.
RunIndication 2
Related FW 1.0.0 Related applications all
Description
This input is one of three inputs used for indication, that the engine is running, and has following
functions:
If the input is active when the engine is expected to be stopped, then the Stop fail alarm is issued and
start is blocked.
If the input becomes active while cranking, the engine is considered as started and the start-up
procedure continues to the next phase (idle).
Note: Learn more in the separate chapter Start sequence (page 137).
RunIndication 3
Related FW 1.0.0 Related applications all
Description
This input is one of three inputs used for indication, that the engine is running, and has following
functions:
If the input is active when the engine is expected to be stopped, then the Stop fail alarm is issued and
start is blocked.
If the input becomes active while cranking, the engine is considered as started and the start-up
procedure continues to the next phase (idle).
Note: Learn more in the separate chapter Start sequence (page 137).
Remote OFF
Related FW 1.0.0 Related applications all
Description
The controller is forced into OFF mode while this input is active. This input can be used, among others,
for following purposes:
In combination with a timer module for periodic testing of the engine.
Remote RUN
Related FW 1.0.0 Related applications all
Description
The controller is forced into RUN mode while this input is active.
LBI: S
Sd override
Related FW 1.0.0 Related applications all
Description
If the input is closed, all 2nd level protections are overriden to allow engine run in an emergency situation,
e.g. when the Controller works as a power supply for fire extinguishing equipment.
All protections are displayed in Alarmlist and recorded into history, however the controller leaves the
Controller in operation. If there are any protections still active or not reset in the moment when the input is
deactivated, the controller will react to them in a standard way.
Following protections are not overriden by this input:
Emergency stop
Overspeed
Underspeed (only if Fuel Solenoid = GAS ENGINE)
Binary and analog protections configured as Sd override type. In fact this protection type means
"Unoverridable shutdown", i.e. it works the same way as standard shutdown protection, however it
can not be overriden (blocked) by the SD OVERRIDE (PAGE 484) input.
Startblocking
Related FW 1.0.0 Related applications all
Description
Engine start is disabled while this input is active. NotReady state is displayed on the controller main
screen and the message Start blocking is displayed in the Alarmlist.
Use this input to disable temporarily the Controller to be started e.g. from an higher-level automation
device such as PLC.
Note: The Controller will not be stopped if the input is activated while the Controller is running.
StartButton
Related FW 1.0.0 Related applications all
Description
This input is used for an external START button mounted on the switchboard. The function of the input is
identical as function of the start button on the controller front panel.
The input is enabled only if the setpoint Local buttons (page 204) is set to position EXTBUTTONS or
BOTH.
StopButton
Related FW 1.0.0 Related applications all
Description
This input is used for an external STOP button mounted on the switchboard. The function of the input is
identical as function of the stop button on the controller front panel.
The input is enabled only if the setpoint Local buttons (page 204) is set to position EXTBUTTONS or
BOTH.
SafetyFunct1NO
Related FW 1.0.0 Related applications all
Description
The function will allow users to configure any pair of binary inputs to serve as a safety monitoring of a
binary state (e.g. excess heat, gas leakage).
This safety monitoring ensures that the protection reacts even if there is mismatch on the indicating BIs.
Note: LBI NO = Normally open LBI (i.e. the protection is active when this LBI is Closed, LBI=1)
Note: LBI NC = Normally closed LBI (i.e. the protection is active when this LBI is Opened, LBI=0)
The mismatch alarm is issued when there are both LBIs from one pair in the same state (both = 0 or both
= 1) for a time longer than the delay.
If only one of LBIs from the pair is configured the function automatically issues alarm SafetyFnXMism
(where X is an integer according to the pair with invalid configuration).
If none of the LBIs from one pair is configured the function is not evaluated at all.
IMPORTANT: This function is not suitable for inputs from sources with longer refresh delay
(e.g. extension modules)
Note: LBI NC = Normally closed LBI (i.e. the protection is active when this LBI is Opened, LBI=0)
The mismatch alarm is issued when there are both LBIs from one pair in the same state (both = 0 or both
= 1) for a time longer than the delay.
If only one of LBIs from the pair is configured the function automatically issues alarm SafetyFnXMism
(where X is an integer according to the pair with invalid configuration).
If none of the LBIs from one pair is configured the function is not evaluated at all.
IMPORTANT: This function is not suitable for inputs from sources with longer refresh delay
(e.g. extension modules)
SafetyFunct2NO
Related FW 1.0.0 Related applications all
Description
The function will allow users to configure any pair of binary inputs to serve as a safety monitoring of a
binary state (e.g. excess heat, gas leakage).
This safety monitoring ensures that the protection reacts even if there is mismatch on the indicating BIs.
Note: LBI NO = Normally open LBI (i.e. the protection is active when this LBI is Closed, LBI=1)
Note: LBI NC = Normally closed LBI (i.e. the protection is active when this LBI is Opened, LBI=0)
The mismatch alarm is issued when there are both LBIs from one pair in the same state (both = 0 or both
= 1) for a time longer than the delay.
If only one of LBIs from the pair is configured the function automatically issues alarm SafetyFnXMism
(where X is an integer according to the pair with invalid configuration).
If none of the LBIs from one pair is configured the function is not evaluated at all.
IMPORTANT: This function is not suitable for inputs from sources with longer refresh delay
(e.g. extension modules)
Note: LBI NC = Normally closed LBI (i.e. the protection is active when this LBI is Opened, LBI=0)
The mismatch alarm is issued when there are both LBIs from one pair in the same state (both = 0 or both
= 1) for a time longer than the delay.
If only one of LBIs from the pair is configured the function automatically issues alarm SafetyFnXMism
(where X is an integer according to the pair with invalid configuration).
If none of the LBIs from one pair is configured the function is not evaluated at all.
IMPORTANT: This function is not suitable for inputs from sources with longer refresh delay
(e.g. extension modules)
SafetyFunct3NO
Related FW 1.0.0 Related applications all
Description
The function will allow users to configure any pair of binary inputs to serve as a safety monitoring of a
binary state (e.g. excess heat, gas leakage).
This safety monitoring ensures that the protection reacts even if there is mismatch on the indicating BIs.
Note: LBI NO = Normally open LBI (i.e. the protection is active when this LBI is Closed, LBI=1)
Note: LBI NC = Normally closed LBI (i.e. the protection is active when this LBI is Opened, LBI=0)
The mismatch alarm is issued when there are both LBIs from one pair in the same state (both = 0 or both
= 1) for a time longer than the delay.
If only one of LBIs from the pair is configured the function automatically issues alarm SafetyFnXMism
(where X is an integer according to the pair with invalid configuration).
If none of the LBIs from one pair is configured the function is not evaluated at all.
IMPORTANT: This function is not suitable for inputs from sources with longer refresh delay
(e.g. extension modules)
Note: LBI NC = Normally closed LBI (i.e. the protection is active when this LBI is Opened, LBI=0)
The mismatch alarm is issued when there are both LBIs from one pair in the same state (both = 0 or both
= 1) for a time longer than the delay.
If only one of LBIs from the pair is configured the function automatically issues alarm SafetyFnXMism
(where X is an integer according to the pair with invalid configuration).
If none of the LBIs from one pair is configured the function is not evaluated at all.
IMPORTANT: This function is not suitable for inputs from sources with longer refresh delay
(e.g. extension modules)
SafetyFunct4NO
Related FW 1.0.0 Related applications all
Description
The function will allow users to configure any pair of binary inputs to serve as a safety monitoring of a
binary state (e.g. excess heat, gas leakage).
This safety monitoring ensures that the protection reacts even if there is mismatch on the indicating BIs.
Note: LBI NO = Normally open LBI (i.e. the protection is active when this LBI is Closed, LBI=1)
Note: LBI NC = Normally closed LBI (i.e. the protection is active when this LBI is Opened, LBI=0)
The mismatch alarm is issued when there are both LBIs from one pair in the same state (both = 0 or both
= 1) for a time longer than the delay.
If only one of LBIs from the pair is configured the function automatically issues alarm SafetyFnXMism
(where X is an integer according to the pair with invalid configuration).
If none of the LBIs from one pair is configured the function is not evaluated at all.
IMPORTANT: This function is not suitable for inputs from sources with longer refresh delay
(e.g. extension modules)
Note: LBI NC = Normally closed LBI (i.e. the protection is active when this LBI is Opened, LBI=0)
The mismatch alarm is issued when there are both LBIs from one pair in the same state (both = 0 or both
= 1) for a time longer than the delay.
If only one of LBIs from the pair is configured the function automatically issues alarm SafetyFnXMism
(where X is an integer according to the pair with invalid configuration).
If none of the LBIs from one pair is configured the function is not evaluated at all.
IMPORTANT: This function is not suitable for inputs from sources with longer refresh delay
(e.g. extension modules)
Speed Down
Related FW 1.0.0 Related applications All
Description
Speed request (page 392) is decreased / increased when the binary input is closed. Speed Down has
higher priority when both Up and Down inputs are active. RPM inc/dec rate is defined by BI Speed Ramp
(page 245).
Engine speed can be set by REQUESTED RPM (PAGE 430) or by SPEED UP (PAGE 490) and SPEED DOWN
(PAGE 489).
Following Speed Request initialization is valid when REQUESTED RPM (PAGE 430) is not configured.
Speed Request (Idle) = 0.0 %. Inputs are active in LOC (Local) mode.
Speed Request (Running) = 50.0 % for AUX (ECU 50 % = Nominal RPM).
Speed Request (Running) = 0.0 % for PRP.
See Engine Values: PRP and AUX/EME/HRB modes.
Note: Minimal Speed Up and Speed Down pulse duration is 110 ms to be accepted by controller.
Note: Minimal Speed Up and Speed Down pulse duration is 110 ms to be accepted by controller.
LBI: T
Timer block 1
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #1.
Note: See also the setpoint Timer channel 1 (page 306) and output TIMERACT 1-4 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 2
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #2.
Note: See also the setpoint Timer channel 2 (page 306) and output TIMERACT 1-4 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 4
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #4.
Note: See also the setpoint Timer channel 4 (page 307) and output TIMERACT 1-4 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 5
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #5.
Note: See also the setpoint Timer channel 5 (page 308) and output TIMERACT 5-8 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 6
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #6.
Note: See also the setpoint Timer channel 6 (page 308) and output TIMERACT 5-8 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 7
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #7.
Note: See also the setpoint Timer channel 7 (page 309) and output TIMERACT 5-8 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 9
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #9.
Note: See also the setpoint Timer channel 9 (page 310) and output TIMERACT 9-12 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 10
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #10.
Note: See also the setpoint Timer channel 10 (page 310) and output TIMERACT 9-12 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 11
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #11.
Note: See also the setpoint Timer channel 11 (page 311) and output TIMERACT 9-12 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 12
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #12.
Note: See also the setpoint Timer channel 12 (page 311) and output TIMERACT 9-12 (PAGE 557).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 14
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #14.
Note: See also the setpoint Timer channel 14 (page 312) and output TIMERACT 13-16 (PAGE 558).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 15
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #15.
Note: See also the setpoint Timer channel 15 (page 313) and output TIMERACT 13-16 (PAGE 558).
Note: See the chapter General purpose timers (page 148) for more details about timers.
Timer block 16
Related FW 1.0.0 Related applications all
Description
This input is used to disable temporarily the output from the Timer channel #16.
Note: See also the setpoint Timer channel 16 (page 313) and output TIMERACT 13-16 (PAGE 558).
Note: See the chapter General purpose timers (page 148) for more details about timers.
E.g. this function can be used to "swap" between two different screen instruments when certain
conditions are fulfilled. Logical binary inputs Mask 1..8 can be used to define any custom condition for
this "swapping" function.
User mask 2
Related FW 1.0.0 Related applications all
Description
This input allows user to activate chosen function in ScreenEditor (tool for GenConfig) for particular
screen instrument. User may choose from the following functions:
E.g. this function can be used to "swap" between two different screen instruments when certain
conditions are fulfilled. Logical binary inputs Mask 1..8 can be used to define any custom condition for
this "swapping" function.
E.g. this function can be used to "swap" between two different screen instruments when certain
conditions are fulfilled. Logical binary inputs Mask 1..8 can be used to define any custom condition for
this "swapping" function.
User mask 4
Related FW 1.0.0 Related applications all
Description
This input allows user to activate chosen function in ScreenEditor (tool for GenConfig) for particular
screen instrument. User may choose from the following functions:
E.g. this function can be used to "swap" between two different screen instruments when certain
conditions are fulfilled. Logical binary inputs Mask 1..8 can be used to define any custom condition for
this "swapping" function.
LBI: W
Watchdog Test
Related FW 1.0.0 Related applications all
Description
Rising edge of this input will provide reset of controller processor.
For full list of Logical binary outputs go to the chapter List of LBO (page 497).
6 back to Controller objects
PeriphCommErr 547
LBO: T
Power1A 548
T cyl differ 557
Power2A 548
TimerAct 1-4 557
Power3A 548
TimerAct 5-8 557
Power4A 549
TimerAct 9-12 557
Power5A 549
TimerAct 13-16 558
Power1B 549
TimerActiveCom 558
Power2B 550
Power3B 550
LBO: U
Power4B 550
User Button 1 558
Power5B 551
User Button 2 559
Prelubr pump 551
User Button 3 559
Prestart 551
User Button 4 560
AFR DBA
Related FW 1.0.0 Related applications all
Description
Output is activated when the sensor Value stays in range of deadband defined by Setpoint DeadBand
(page 335).
AFR ErrA
Related FW 1.0.0 Related applications all
Description
Output is activated when the sensor Value goes over the tolerance level defined by Setpoint
SensorValTolA (page 351) and stays there for time defined by Setpoint TAFRERRA (page 350).
Output stays active as long the sensor Value stays above the tolerance level and for time TAFRERRA
(page 350) when the sensor Value is back in the tolerance level.
AFR limB
Related FW 1.0.0 Related applications all
Description
Output is activated when the mixer Value AFRVlvRegB (page 416) reaches the limit Value adjusted
with Setpoint LimPos (page 331)
AFR DBB
Related FW 1.0.0 Related applications all
Description
Output is activated when the sensor Value stays in range of deadband defined by Setpoint DeadBand
(page 335).
AFR ErrB
Related FW 1.0.0 Related applications all
Description
Output is activated when the sensor Value goes over the tolerance level defined by Setpoint
SensorValTolB (page 368) and stays there for time defined by Setpoint TAFRERRB (page 367).
Output stays active as long the sensor Value stays above the tolerance level and for time TAFRERRB
(page 367) when the sensor Value is back in the tolerance level.
Alarm flashing
Related FW 1.0.0 Related applications all
Description
This is the flashing alternative of the output ALARM (PAGE 502), i.e. the output flashes with period 1s/1s
while the output ALARM (PAGE 502) is closed.
LBO: B
Bin selector 1
Related FW 1.0.0 Related applications all
Description
Output is closed or opened according to the setpoint Bin selector 1 (page 246).
Note: The output is intended for ECU-controlled engines to switch on/off some particular ECU function
by a controller setpoint if the function can be controlled by a binary value over the J1939 bus.
Bin selector 3
Related FW 1.0.0 Related applications all
Description
Output is closed or opened according to the setpoint Bin selector 3 (page 246).
Note: The output is intended for ECU-controlled engines to switch on/off some particular ECU function
by a controller setpoint if the function can be controlled by a binary value over the J1939 bus.
Bin selector 4
Related FW 1.0.0 Related applications all
Description
Output is closed or opened according to the setpoint Bin selector 4 (page 247).
Note: The output is intended for ECU-controlled engines to switch on/off some particular ECU function
by a controller setpoint if the function can be controlled by a binary value over the J1939 bus.
LBO: C
Clutch Connect
Related FW 1.0.0 Related applications all
Description
Output is closed if binary input Rem Clutch is active or controller I/0 button is pressed (command sent) and
actual engine RPM is between: ClutchMinSpeed and ClutchMaxSpeed.
Output stays closed even if the RPM goes out of limits above.
Can’t be opened by button when binary input Rem Clutch is closed.
CommonActLev 1
Related FW 1.0.0 Related applications all
Description
The output is closed while there is at least one 1st level (yellow) alarm present in the alarm list. The alarm
can be in any state, i.e. active unconfirmed, active confirmed or inactive unconfirmed. See the chapter
Protections and Alarm management (page 169) for more information.
CommonAlLev 1
Related FW 1.0.0 Related applications all
Description
This output is active if there is at least one unconfirmed 1st-level (yellow) alarm present in the alarm list.
See the chapter Protections and Alarm management (page 169) forr more information.
CommonActLev 2
Related FW 1.0.0 Related applications all
Description
The output is closed while there is at least one 2nd level (red) alarm present in the alarm list. The alarm
can be in any state, i.e. active unconfirmed, active confirmed or inactive unconfirmed.See the chapter
Protections and Alarm management (page 169) for more information.
CommonAlLev 2
Related FW 1.0.0 Related applications
Description
This output is active if there is at least one unconfirmed 2nd-level (red) alarm present in the alarm list.
See the chapter Protections and Alarm management (page 169) for more information.
Common Fls
Related FW 1.0.0 Related applications all
Description
The output is closed while there is at least one alarm of the Sensor fail type present in the alarm list. The
alarm can be in any state, i.e. active unconfirmed, active confirmed or inactive unconfirmed.See the
chapter Protections and Alarm management (page 169) for more information.
Common Hst
Related FW 1.0.0 Related applications all
Description
The output is closed for 1s when any alarm of History record type appears. See the chapter Protections
and Alarm management (page 169) for more information.
Common Wrn
Related FW 1.0.0 Related applications all
Description
The output is closed while there is at least one alarm of the Warning type present in the alarm list. The
alarm can be in any state, i.e. active unconfirmed, active confirmed or inactive unconfirmed. See the
chapter Protections and Alarm management (page 169) for more information.
Common Sd
Related FW 1.0.0 Related applications all
Description
The output is closed while there is at least one alarm of the Shutdown type present in the alarm list. The
alarm can be in any state, i.e. active unconfirmed, active confirmed or inactive unconfirmed. See the
chapter Protections and Alarm management (page 169) for more information.
Cooling
Related FW 1.0.0 Related applications all
Description
The output is closed during the Cooling phase.
Cooling Pump
Related FW 1.0.0 Related applications all
Description
This output is used for control of an external electric motor-driven cooling pump. The output closes when
the Controller is started (i.e. at the end of the Starting period) and opens at the end of the Aftercooling
period, which takes place after the engine has been fully stopped. Duration of the aftercooling period is
adjusted by the setpoint AfterCool time (page 239).
The output opens immediately when EMERGENCY STOP (PAGE 439) is activated or if the controller is
switched to OFF mode.
CrankProcedure
Related FW 1.0.0 Related applications all
Description
The output is closed while the engine is cranking and during pauses between crank attemps. The output
is opened either when the Controller is started or failed to start. See the diagram in the descrition of the
output CRANKING (PAGE 507) for differencies between outputs CRANKPROCEDURE (PAGE 506),
CRANKING (PAGE 507) and STARTER (PAGE 555).
Unsuccesfull start
CtrlHeartBeatF
Related FW 1.0.0 Related applications all
Description
External Watchdog relay support. Logical binary output can be connected to pulse input of external
WatchDog relay.
CtrlHBeat FD
Related FW 1.0.0 Related applications all
Description
This output is used at a redundant controller to disconnect the main controller from the Controller,
connect the redundant one instead and activate it.
The output is closed:
If the input CTRL HBEAT SENS (PAGE 436) is configured onto any input terminal and the
redundancy controller does not sense the "heart beat" signal from the main controller at that
terminal.
If the redundant controller has not received two consequent messages from the main controller.
The address of the main controller for the particular redundant one is selected by the the setpoint
WatchedContr (page 208)WatchedContr (page 208).
Note: Learn more about redundancy in separate chapter Controller redundancy (page 142).
ECU PwrRelay
Related FW 1.0.0 Related applications all
Description
This output is used for control of the "Keyswitch" ECU input. The output is closed at the beginning of the
prestart phase, remains closed while the engine is running, and is opened when the engine has to be
stopped. The keyswitch input may be also labeled as "15" according to cable numbering convention used
in vehicles.
If this input is used (configured), the evaluation of ECU communication fault alarm and other ECU-
related alarms is enabled only while the engine is beeing started or is running. The reason is that most
of ECUs go to sleep mode and do not communicate while the keyswitch input is deactivated.
Note: It is recommended to adjust the Prestart time (page 235) to at least 3 sec to allow the
ECU to wake-up and begin the communication prior to the ECU communication fault alarm is
enabled.
If this input is not configured the evaluation of ECU-related alarms is enabled all the time.
Note: If your ECU does not have the keyswitch input, however you want the ECU-related alarms to be
disabled while the engine is not running, configure the output onto a virtual IO module (VPIO).
IMPORTANT: This output should not be used for disconnecting of main power supply from
the ECU. Disconnecting of the main power supply while the engine is running might cause
the ECU will not be able to record eventual trouble codes into it's nonvolatile memory.
FltResButnEcho
Related FW 1.0.0 Related applications all
Description
This output provides 1s pulse when:
Fault reset button is pressed on the controller front panel or
Fault reset button is pressed on any of external local/remote terminals or
fault reset command is received via communication line or
the input FAULT RESBUTTON (PAGE 450) is activated.
LBO: G
GasVTest run
Related FW 1.0.0 Related applications
Description
Output for Gas valve test activation. Configure this output in case you want to run the Gas valve check
before each start of engine.
Setpoint GasVTest (page 242) has to be ENABLED.
LBO: H
Horn
Related FW 1.0.0 Related applications all
Description
The output closes together with the output ALARM (PAGE 502). It opens when the output ALARM (PAGE
502) is opened or Horn reset button is pressed or Horn Timeout (page 247) has elapsed.
HrnResButnEcho
Related FW 1.0.0 Related applications all
Description
This output provides 1s pulse when:
Horn reset button is pressed on the controller front panel or
Horn reset button is pressed on any of external local/remote terminals or
horn reset command is received via communication line or
the input HORNRESBUTTON (PAGE 465) is activated.
LBO: I
Idle run
Related FW 1.0.0 Related applications all
Description
This output is closed while the timer Idle time (page 238) is counting down. This timer begins to count
down when the engine is considered as started and the starter motor is deenergized. See also description
of the output STARTER (PAGE 555).
Idle/Nominal
Related FW 1.0.0 Related applications all
Description
This output is intended for switching of the speed governor reference from idle to nominal speed and vice
versa. The output is opened when the engine is required to run at idle speed and it is closed when the
engine is required to run at nominal speed.
The output is opened while the engine is not running and also during start.
The output is closed after the engine has been started when the timer Idle time (page 238) elapses.
The output remains closed while the engine is running.
The output is opened while stopping either at the beginning or at the end of the cooling phase. This is
selectable by the setpoint Cooling speed (page 238).
Note: Some governors do not support speed reference switching.
Initialized
Related FW 1.0.0 Related applications all
Description
This LBO indicates that the controller finished the reboot after the restart. It can be used in internal PLC
for blocking some binary inputs to avoid the hazards after restart of the controller.
LBO: K
kWh pulse
Related FW 1.0.0 Related applications all
Description
This output generates 100ms pulse always when the internal kWh counter incremented.
LBO: L
LambdaHeatedA
Related FW 1.0.0 Related applications all
Description
Output is activated when the time of Setpoint StartTimeAFRA (page 338) is counted down.
LambdaHeatedB
Related FW 1.0.0 Related applications all
Description
Output is activated when the time of Setpoint StartTimeAFRB (page 355) is counted down.
Loaded
Related FW 1.0.0 Related applications all
Description
The output is closed while the Controller is loaded and the load is beeing regulated according to selected
mode (baseload, import/export, power management etc.) or is not beeing regulated in single island
operation.
Logical 1
Related FW 1.0.0 Related applications all
Description
This output is always closed. It may be used in functions (e.g. ECU outputs or PLC modules inputs)
where continuously active binary value is required.
LBO: M
MODES: Off mode
Related FW 1.0.0 Related applications all
Description
The output is closed while the controller is currently in OFF mode (either switched by the mode selector
on the front panel or by the input REMOTE OFF (PAGE 483)).
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
Register for writing Modbus register number Value for back-reading Modbus register number
ModbusSw1 46337 ModbusSw1 40547
ModbusSw2 46338 ModbusSw2 40548
MixUpA
Related FW 1.0.0 Related applications all
Description
Binary output for Up Mixer control.
This output is result of PID control, so it's pulse length is not fixed.
MixUpB
Related FW 1.0.0 Related applications all
Description
Binary output for Up Mixer control.
This output is result of PID control, so it's pulse length is not fixed.
MixDnB
Related FW 1.0.0 Related applications all
Description
Binary output for Down Mixer control.
LBO: N
Not ready
Related FW 1.0.0 Related applications all
Description
The output is closed while the Controller is not in operation, however it is not ready to be put into
operation. The output is closed while:
the Controller is not running and
the controller is in OFF mode or
there is an alarm blocking start of the Controller.
LBO: O
Operational
Related FW 1.0.0 Related applications all
Description
The output is closed when the Controller is ready for operation or is currently in operation.
LBO: P
PeriphCommErr
Related FW 1.0.0 Related applications all
Description
The output is closed while there is an error in the communication with any peripheral unit (e.g. IS-AIN8,
IGS-PTM, ...).
Power1A
Related FW 1.0.0 Related applications all
Description
Binary output which serves as indication which part of characteristic of AFR regulation is active.
Power2A
Related FW 1.0.0 Related applications all
Description
Binary output which serves as indication which part of characteristic of AFR regulation is active.
Power3A
Related
Related FW 1.0.0 all
applications
Description
Binary output which serves as indication which part of characteristic of AFR regulation is active.
Power5A
Related FW 1.0.0 Related applications all
Description
Binary output which serves as indication which part of characteristic of AFR regulation is active.
Power1B
Related
Related FW 1.0.0 all
applications
Description
Binary output which serves as indication which part of characteristic of AFR regulation is active.
Power3B
Related
Related FW 1.0.0 all
applications
Description
Binary output which serves as indication which part of characteristic of AFR regulation is active.
Power4B
Related
Related FW 1.0.0 all
applications
Description
Binary output which serves as indication which part of characteristic of AFR regulation is active.
Prelubr pump
Related FW 1.0.0 Related applications all
Description
This output can be used for periodic lubrication of the engine while the engine is not running. The output is
periodically closed for Prelubr time (page 235) and then opened for Prelubr pause (page 236).
The output opens immediately when EMERGENCY STOP (PAGE 439) is activated or if the controller is
switched to OFF mode.
Note: The engine must be equipped with an external electric motor-driven oil pump to allow this function.
Prestart
Related FW 1.0.0 Related applications all
Description
This output can be used for control of any device, which has to be activated just before start, i.e. glow
plugs. The output is closed for time period of Prestart time (page 235) prior to activating of the starter
motor and remains closed during cranking and also during pause between cranking attempts.
Note: Learn more in the separate chapter Start sequence (page 137).
RemoteControl1
Related FW 1.0.0 Related applications all
Description
This is a general purpose output, which can be closed and opened remotely, e.g. from InteliMonitor using
the "Remote switches" tool or via MODBUS using the register #46361 and command #26.
Note: See the Remote switches chapter in the InteliMonitor help for details about how to control the
output from InteliMonitor and the Modbus chapter in the latest communication guide for information about
control the output using Modbus.
RemoteControl2
Related FW 1.0.0 Related applications all
Description
This is a general purpose output, which can be closed and opened remotely, e.g. from InteliMonitor using
the "Remote switches" tool or via MODBUS using the register #46361 and command #26.
Note: See the Remote switches chapter in the InteliMonitor help for details about how to control the
output from InteliMonitor and the Modbus chapter in the latest communication guide for information about
control the output using Modbus.
RemoteControl4
Related FW 1.0.0 Related applications all
Description
This is a general purpose output, which can be closed and opened remotely, e.g. from InteliMonitor using
the "Remote switches" tool or via MODBUS using the register #46361 and command #26.
Note: See the Remote switches chapter in the InteliMonitor help for details about how to control the
output from InteliMonitor and the Modbus chapter in the latest communication guide for information about
control the output using Modbus.
RemoteControl5
Related FW 1.0.0 Related applications all
Description
This is a general purpose output, which can be closed and opened remotely, e.g. from InteliMonitor using
the "Remote switches" tool or via MODBUS using the register #46361 and command #26.
Note: See the Remote switches chapter in the InteliMonitor help for details about how to control the
output from InteliMonitor and the Modbus chapter in the latest communication guide for information about
control the output using Modbus.
RemoteControl6
Related FW 1.0.0 Related applications all
Description
This is a general purpose output, which can be closed and opened remotely, e.g. from InteliMonitor using
the "Remote switches" tool or via MODBUS using the register #46361 and command #26.
Note: See the Remote switches chapter in the InteliMonitor help for details about how to control the
output from InteliMonitor and the Modbus chapter in the latest communication guide for information about
control the output using Modbus.
RemoteControl8
Related FW 1.0.0 Related applications all
Description
This is a general purpose output, which can be closed and opened remotely, e.g. from InteliMonitor using
the "Remote switches" tool or via MODBUS using the register #46361 and command #26.
Note: See the Remote switches chapter in the InteliMonitor help for details about how to control the
output from InteliMonitor and the Modbus chapter in the latest communication guide for information about
control the output using Modbus.
Running
Related FW 1.0.0 Related applications all
Description
This output is closed at the end of the IDLE RUN (PAGE 511) phase when the output IDLE/NOMINAL (PAGE
511) is closed to switch the Controller to nominal speed. The output is opened when the Controller goes
to cooling phase or performs a shutdown.
LBO: S
Speed dn
Related FW 1.0.0 Related applications all
Description
This output together with the complementary output SPEED UP (PAGE 555) are designed for speed and
power control at Controllers where the speed governor does not support analogue control.
Note: The governor is recommended to be configured for droop function when these outputs are used for
power control.
Note: The alarm Wrn SpdRegLim is disabled when this output is used (configured onto any controller
terminal or virtual output).
Note: The alarm Wrn SpdRegLim is disabled when this output is used (configured onto any controller
terminal or virtual output).
Starter
Related FW 1.0.0 Related applications all
Description
The output is used to energize the starter motor. The output closes at the begining of start sequence after
prestart has been completed and opens when the engine is started.
Note: Learn more in the separate chapter Start sequence (page 137).
Starting
Related FW 1.0.0 Related applications all
Description
The output is closed at the beginning of the prestart phase and remains closed during prestart, cranking
and starting phases. The output is opened either when the Controller goes to running phase or when it
failed to start. See the diagram in the descrition of the output CRANKING (PAGE 507) for details.
Start Blocked
Related FW 1.0.0 Related applications all
Description
In some conditions given by non-sense setings of setpoints is this LBO closed and start of engine is
blocked. The start is blocked and LBO START BLOCKED (PAGE 555) is closed when LBI
STARTBLOCKING (PAGE 484)STARTBLOCKING (PAGE 484) is active as well.
Stop Pulse
Related FW 1.0.0 Related applications all
Description
One second pulse is issued at this output when the engine is required to stop (i.e. this pulse does not
commence stopping sequence but it is rather an actual command to engine physical stopping). The
output is especially intended to be used as stop command for ECU-controlled engines, which support
stop command via the communication bus (e.g. J1939).
Stop Solenoid
Related FW 1.0.0 Related applications all
Description
This output is used at diesel engines equipped with fuel valve, which must be energized to stop the
engine.
The output is closed when the engine has to stop, remains closed while the engine is stopping and is
opened back if the engine has successfully stopped and Stop time (page 240) elapsed. For other
stopping sequences please refer to Stop sequence (page 140) chapter.
The total time this output is continuously active is never shorter than Stop time (page 240), i.e. if the
Controller stops quickly, the output may remain closed even though all symptoms indicate the engine is
stopped.
This output is also closed if the engine begins to rotate unexpectedly, i.e. if it is started manually directly
on the engine. To allow the engine to be operated manually without intervention from the controller,
switch the controller to the emergency manual mode using the input EMERG. MANUAL (PAGE 438).
Note: Learn more about this topic in the separate chapter Stop sequence (page 140).
StartButnEcho
Related FW 1.0.0 Related applications all
Description
This output provides 1s pulse when:
Start button is pressed on the controller front panel or
Start button is pressed on any of external local/remote terminals or
start command is received via communication line or
the input START BUTTON (PAGE 484) is activated.
Stopping
Related FW 1.0.0 Related applications all
Description
The output closes when the command to stop the engine has been issued, i.e. the output FUEL
SOLENOID (PAGE 510) has been deactivated. It opens when the engine is fully stopped. The output also
closes if the engine begins to rotate spontaneously.
This output is closed for the whole time of the stopping sequence (regardless of the repeated opening of
the STOP SOLENOID (PAGE 556)). It is deactivated immediately when the engine is considered stopped.
LBO: T
T cyl differ
Related FW 1.0.0 Related applications all
Description
The output is closed while the alarm cylinder temperature difference alarm is active.
TimerAct 1-4
Related FW 1.0.0 Related applications all
Description
This is combined output from timer channels 1-4. The output is closed if at least one of the channels is
active.
Note: See the chapter General purpose timers (page 148) for more details about timers.
TimerAct 5-8
Related FW 1.0.0 Related applications all
Description
This is combined output from timer channels 5-8. The output is closed if at least one of the channels is
active.
Note: See the chapter General purpose timers (page 148) for more details about timers.
TimerAct 9-12
Related FW 1.0.0 Related applications all
Description
This is combined output from timer channels 9-12. The output is closed if at least one of the channels is
active.
Note: See the chapter General purpose timers (page 148) for more details about timers.
TimerActiveCom
Related FW 1.0.0 Related applications all
Description
This is combined output from all timer channels. The output is active if at least one timer channel is
active.
Note: See the chapter General purpose timers (page 148) for more details about timers.
LBO: U
User Button 1
Related FW 1.0.0 Related applications all
Description
This output can be specified for example on buttons on IV-5/8 or in SCADA diagram in InteliMonitor. Its
state depends on function assigned to the related button.
It is possible to lock UserButton commands in configuration to specific user level. Buttons 1-8 and 9-16
are locked separately.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
User Button 3
Related FW 1.0.0 Related applications all
Description
This output can be specified for example on buttons on IV-5/8 or in SCADA diagram in InteliMonitor. Its
state depends on function assigned to the related button.
It is possible to lock UserButton commands in configuration to specific user level. Buttons 1-8 and 9-16
are locked separately.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
User Button 5
Related FW 1.0.0 Related applications all
Description
This output can be specified for example on buttons on IV-5/8 or in SCADA diagram in InteliMonitor. Its
state depends on function assigned to the related button.
It is possible to lock UserButton commands in configuration to specific user level. Buttons 1-8 and 9-16
are locked separately.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
User Button 7
Related FW 1.0.0 Related applications all
Description
This output can be specified for example on buttons on IV-5/8 or in SCADA diagram in InteliMonitor. Its
state depends on function assigned to the related button.
It is possible to lock UserButton commands in configuration to specific user level. Buttons 1-8 and 9-16
are locked separately.
Pressing the button changes the state of log. binary output User button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
User Button 9
Related FW 1.0.0 Related applications all
Description
This output can be specified for example on buttons on IV-5/8 or in SCADA diagram in InteliMonitor. Its
state depends on function assigned to the related button.
It is possible to lock UserButton commands in configuration to specific user level. Buttons 1-8 and 9-16
are locked separately.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
User Button 11
Related FW 1.0.0 Related applications all
Description
This output can be specified for example on buttons on IV-5/8 or in SCADA diagram in InteliMonitor. Its
state depends on function assigned to the related button.
It is possible to lock UserButton commands in configuration to specific user level. Buttons 1-8 and 9-16
are locked separately.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
User Button 13
Related FW 1.0.0 Related applications all
Description
This output can be specified for example on buttons on IV-5/8 or in SCADA diagram in InteliMonitor. Its
state depends on function assigned to the related button.
It is possible to lock UserButton commands in configuration to specific user level. Buttons 1-8 and 9-16
are locked separately.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
User Button 15
Related FW 1.0.0 Related applications all
Description
This output can be specified for example on buttons on IV-5/8 or in SCADA diagram in InteliMonitor. Its
state depends on function assigned to the related button.
It is possible to lock UserButton commands in configuration to specific user level. Buttons 1-8 and 9-16
are locked separately.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
Pressing the button changes the state of log. binary output User Button X to closed. When the output is closed and
ON
the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened. When the output is opened
OFF
and the button is pressed state is not changed.
Pressing the button changes the state of log. binary output User Button X to opened or closed depending on
ON/OFF
previous state (it is changed to the opposite state).
Pressing the button issues log. binary output User Button X to close for time given by setpoint UserBtn pulse
Pulse (page 208) .
ON Note: Repeated pressing of button during the closed period causes issuing another puls to be generated from
the moment of button pushing.
LBO: V
Ventilation
Related FW 1.0.0 Related applications all
Description
The output is intended for control of an engine room ventilation fan or engine container ventilation fan.
Intended for the engine ventilator control. The output is closed at the beginning of the start procedure
together with PRESTART (PAGE 551) output and opens together with STOP SOLENOID (PAGE 556) after the
engine is fully stopped.
The output opens immediately when EMERGENCY STOP (PAGE 439) is activated or if the controller is
switched to OFF mode.
LBO: W
Wrn Stop fail
Related FW 1.0.0 Related applications all
Description
Output is activated when the alarm message Wrn stop fail occurs.
This output is activated when the Controller indicates that it is rotating although it has to be stopped.
In this case is the Gas Valves and Ignition outputs stays closed till the engine drops to 0 RPM.
During this situation is only alarm message and this Log Bout initiated.
Sync/Load ctrl:
Speed gov bias = 6,00 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 4 V
SpeedGovHiLim = 8 V
Sync/Load ctrl:
Speed gov bias = 6,00 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 4 V
SpeedGovHiLim = 8 V
Sync/Load ctrl:
Speed gov bias = 5,10 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0 V
SpeedGovHiLim = 10 V
Caterpillar ADEM
Sync/Load ctrl:
Speed gov bias = 5,10 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0 V
SpeedGovHiLim = 10 V
Sync/Load ctrl:
Speed gov bias = 5,10 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0 V
SpeedGovHiLim = 10 V
Caterpillar PEEC
Sync/Load ctrl:
SpeedGovPWM rate = 500 Hz
Caterpillar PEEC
Sync/Load ctrl:
SpeedGovPWM rate = 500 Hz
Sync/Load ctrl:
Speed gov bias = 5,10 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0 V
SpeedGovHiLim = 10 V
Cummins ECPG
Sync/Load ctrl:
Speed gov bias = 2,50 V
SpeedRegChar = POSITIVE
Sync/Load ctrl:
Speed gov bias = 6,40 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 5 V
SpeedGovHiLim = 7,8 V
Spurious operation of the controller push buttons is caused by excessive interference from the
speed controller when capacitor is not connected between power supply terminals 1 and 2.
Cummins GCS
Sync/Load ctrl:
Speed gov bias = 5,00 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 2,5 V
SpeedGovHiLim = 7,5 V
Cummins ONAN
Sync/Load ctrl:
Speed gov bias = 2,50 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0V
SpeedGovHiLim = 5 V
Cummins QSL9
Sync/Load ctrl:
Speed gov bias = 3,50 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 2,5 V
SpeedGovHiLim = 5 V
Cummins QST30
Sync/Load ctrl:
Speed gov bias = 5,00 V
SpeedRegChar = POSITIVE
Sync/Load ctrl:
Speed gov bias = 2,50 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 2,5 V
SpeedGovHiLim = 7,5 V
ECON 4
Sync/Load ctrl:
Speed gov bias = 5,1 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0,0 V
SpeedGovHiLim = 10 V
Sync/Load ctrl:
Speed gov bias = 5,00 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 4 V
SpeedGovHiLim = 6 V
Sync/Load ctrl:
Speed gov bias = 5,00 V
SpeedRegChar = POSITIVE
Sync/Load ctrl:
Speed gov bias = 5,00 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 4 V
SpeedGovHiLim = 6 V
Heinzmann E6
Sync/Load ctrl:
Speed gov bias = 5,00 V
SpeedRegChar = POSITIVE
Heinzmann E16
Sync/Load ctrl:
Speed gov bias = 0,00 V
SpeedRegChar = POSITIVE
Heinzmann KG-1-03F
Sync/Load ctrl:
Speed gov bias = 0,00 V
SpeedRegChar = POSITIVE
Sync/Load ctrl:
Speed gov bias = 5 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0,8 V
For connection w/o resistor refer to the
next setting
Sync/Load ctrl:
Speed gov bias = 2,7 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0 V
SpeedGovHiLim = 6 V
Sync/Load ctrl:
Speed gov bias = 4,90 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0 V
SpeedGovHiLim = 10 V
Sync/Load ctrl:
Speed gov bias = 2,50 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0,8V
SpeedGovHiLim = 4,5 V
Sync/Load ctrl:
Speed gov bias = 2,50 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0,5 V
SpeedGovHiLim = 4,5 V
Above mentioned pin numbers refer to the Customer Interface Connector. The J1 connector
on ECM has the following numbering:
20 = J1/3; 24 = J1/17
Sync/Load ctrl:
Speed gov bias = 2,50 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 2,5 V
SpeedGovHiLim = 7,5 V
Sync/Load ctrl:
Speed gov bias = 4,00 V
SpeedRegChar = POSITIVE
Sync/Load ctrl:
Speed gov bias = 5,00 V
SpeedRegChar = POSITIVE
Sync/Load ctrl:
Speed gov bias = 5,00 V
SpeedRegChar = POSITIVE
Sync/Load ctrl:
Speed gov bias = 5,00 V
SpeedRegChar = POSITIVE
Sync/Load ctrl:
Speed gov bias = 2,50 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0 V
SpeedGovHiLim = 5 V
Sync/Load ctrl:
Speed gov bias = 3,1 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 6,5V
SpeedGovHiLim = 0,0 V
WOODWARD EPG
Sync/Load ctrl:
Speed gov bias = 0,00 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = - 3 V
SpeedGovHiLim = 3 V
For Woodward EPG speed governor (revision F) are limits:
SpeedGovLowLim = -3 V
SpeedGovHiLim = + 2 V
Speed gov bias = - 0,5 V
Sync/Load ctrl:
Speed gov bias = 0,00 V
WOODWARD L - series
Sync/Load ctrl:
Speed gov bias = 2,50 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = 0 V
SpeedGovHiLim = 5 V
WOODWARD Proact II
Sync/Load ctrl:
Speed gov bias = 0,00 V
SpeedRegChar = POSITIVE
SpeedGovLowLim = - 2,5V
SpeedGovHiLim = 2,5 V
9.3.8 InternetBridge-NT
I-CB (Communication bridge) is CAN bus interface between Controller and Engine Control Unit (ECU) for
ECUs which don't support standard J1939 communication (MTU, CAT etc.). Engine values (RPM, Oil pressure
and other) are received from ECU via CAN and corresponding sensors are not needed on controller. Use
ICBEdit software for I-CB configuration (included in installation package).
1 - 2 n.o.
1 - 3 n.c.
One unit contains two parts (separate PCBs). There are 8 relays on each part which is located on common
plastic base.
I-RB16 is 60 mm high from DIN rail base.
Note: I-RB contains two separate boards, 8 relays on each. It can be ordered as I-RB8 as well.
9.3.14 I-AOUT8
General Description
I-AOUT8 is an extension unit with 8 Analog outputs. Each analog output can be switched by jumper for.
0 to 20 mA
0 to 10 VDC
PWM (Pulse With Modulation on 1,2 kHz)
I-AOUT8 modules is connected on CAN 1 (peripheral) bus. The corresponding module Address 1 to 4 (default 1)
must be set on module (by Adr.1 and Adr.2 jumpers) and in controller configuration. Communication fail is
indicated in controller Alarm list and by binary output. Use GenConfig PC tool for controller configuration.
It is possible to connect up to four I-AOUT8 units to one controller.
I-AOUT8 unit can be mounted on DIN rail (35 mm).
CAN 1 terminating 120 Ω resistor jumper is connected in default. AGND terminals are on the same potential.
I 0 to 20 mA
U 0 to 10 VDC
LED Indication
Green LED is located near the power supply connector.
9.3.15 I-LBA
For the connections with 12 V DC power supply an I-LBA module can be connected to controller power
terminals in order to allow the controller to continue operation during cranking if the battery voltage dip occurs.
Controllers which may be supplied from I-LBA module.
IG-NT or IG-NTC
IS- NT- BB / IS-
Controller / IG-NT-BB or IG- IS-NT IG-CU IS-CU IL-CU/ IL-NT
NTC-BB
NTC-BB
Connection
YES YES NO YES NO YES
applicable
The I-LBA unit is intended to supply one controller unit only at the same time.
It is not recommended to use +PWR BOUT outputs on the controller as a source for relays, as their
consumption would exhaust I-LBA capacitors very fast.
It is also not recommended to supply any kind of above controllers with LT (Low Temperature) display because
of the high current consumption of the LT display.
See also chapter Power supply fusing.
6 back to Extensional modules