Manual MTU

MTU_ValueService
Technical Documentation
Electronic
Dialog System
DiaSys®2.40SP1
Functional Description
E531920/04E
Printed in Germany
© 2008 Copyright MTU Friedrichshafen GmbH
This Publication is protected by copyright and may not be used in any way whether in whole or in part without the
prior written permission of MTU Friedrichshafen GmbH. This restriction also applies to copyright, distribution,
translation, microfilming and storage or processing on electronic systems including data bases and online services.
This handbook is provided for use by maintenance and operating personnel in order to avoid malfunctions or
damage during operation.
Subject to alterations and amendments.
Table of Contents 01
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 03
1.1 General information on the DiaSys program .................................. 03
2 First steps .................................................................... 09
2.1 Preparations ............................................................ 09
2.2 Device description ....................................................... 12
3 DiaSys used with governors ..................................................... 43
3.1 Overview of “Available functions” .......................................... 43
3.2 Measurement data ....................................................... 47
3.3 Parameters ............................................................. 58
3.4 Injector code ............................................................ 61
3.5 Send changed data to controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.6 Transmit to controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.7 Logfiles ................................................................ 71
3.8 Extras ................................................................. 77
3.9 Injector exchange (DiaSys 2.52 SP1 and higher) ............................... 99
3.10 To menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.11 Engine history data ...................................................... 103
3.12 Maintenance forecast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4 MEM module programming ...................................................... 111
4.1 Prepare for BDM programming ............................................. 111
4.2 Programming mode ...................................................... 120
5 Templates .................................................................... 125
5.1 Templates .............................................................. 125
5.2 Index .................................................................. 131
E531920/04E 2008-08 © MTU

02 Table of Contents
E531920/04E 2008-08 © MTU

Introduction 03
1 Introduction
1.1 General information on the DiaSys program
Use
The DiaSys program is required to communicate with various MTU controllers, RCS-5 remote
control systems and MCS-5 monitoring systems.
The main functions of the DiaSys program are:
• data interchange with the central database
• adjusting the controller parameters
• data recorder function
Note: For the most part, this manual contains information concerning the use of DiaSys together
with governors. The functions described presuppose a hardware key level 1B (service/distributor).
Menu screen functions are not described in this manual.
Neither the requirements of DiaSys software on the hardware (PC) nor the installation of
this software is described in this document.
Terms and definitions

Term Meaning
ADEC Advanced Diesel Engine Controller

This term is not used in this document; instead, the term “ECU-7” is always used
MDEC MTU Diesel Engine Controller

This term is not used in this document; instead, the term “ECU-4” is always used
Online mode The serial or the CAN interface of the PC is connected to the controller and the
data connection to the controller is established.
Refer to the figure below (online mode)
Offline mode 1. The controller is not connected to the serial or CAN interface of the PC. The
data connection to the controller has been disconnected (office mode).
Refer to the figure below (offline mode)
2. The controller is connected to the serial or CAN interface of the PC. The data
connection to the controller has been disconnected (programming mode).
Functional software (FSW) Operating software of the controller.

Without FSW in the controller, DiaSys can not switch to online mode.
Engine parameter set (MPS) These are operating parameters of the governor.
Local database Files or databases that are stored locally on the PC for an engine number. The
data can be determined for the controller or for the central database.
Central database For each engine number, the data (FSW and MPS) is stored centrally in a
database in Friedrichshafen, Germany. Other identical designation: controller
database.
TIM ID: 0000022787 – 001
CCS Compatibility Check System

Is used for checking the dependencies between objects (software and/or
hardware) and to display object features.
E531920/04E 2008-08 © MTU

04 Introduction
Online mode
Offline mode
Hardware key
The hardware key
• contains a range of owner-specific information (refer to chapter “Hardware Key Info”).
• has a period of validity. Three months before expiration of the validity, a message is issued
to the user every time the DiaSys program is started.
Setting the CAN hardware used

To connect the ECU-7, the CAN adapter used from the IXXAT company must be communicated to the
DiaSys program. This is normally done once in “Start | Settings | System control | IXXAT Interfaces”.
TIM ID: 0000022787 – 001
Here, the adapter must be marked and the “Default HW” button clicked.
If DiaSys does not detect the adapter then the process must be repeated.
E531920/04E 2008-08 © MTU

Introduction 05
Key combinations
Key Action Explanation
combination
Ctrl + Alt + P Displays the Additional information depending on the active window.
properties window
Ctrl + P Print The active window is printed - if possible.
Ctrl + B Binary display In the single parameter window, parameters with the “digit” unit can be
displayed as binary values.
Ctrl + G Go to In the single parameter window, you can search for a certain parameter
number.
Ctrl + Shift + A Prepare to export In the offline Y(t) display, measured values can be exported in a file in
the measured csv format.
values For more detailed explanations, please see below.
F3 Restart recorder If you press the F3 key during a recording, then the previous recording
is automatically stored together with its consecutive number using a
standard name (current date) and a new measured data recording
sequence is started.
Explanations on Ctrl + Shift + A:

Ctrl + Shift + A opens the offline Y(t) screen display:
Ctrl + Shift + S stores the values of the current cursor. On moving the cursor and repressing Ctrl + Shift + S, the
next value is measured. Ctrl + Shift + O end the measurement and stores it via a file selection dialog box.
Note:
• If the key combinations are already assigned by the system then these combinations have no effect within DiaSys.
TIM ID: 0000022787 – 001
Program info
This window appears after starting the program.
It displays the version number, the copyright, and the date and time.
E531920/04E 2008-08 © MTU

06 Introduction
After clicking the “Ok” button, a general safety message appears notifying the user of the dangers
of incorrect operation and programming of the connected devices.
TIM ID: 0000022787 – 001
E531920/04E 2008-08 © MTU

Introduction 07
Clicking the “Ok” button moves you to the next program window. The program is quit on clicking the “Cancel” button.
TIM ID: 0000022787 – 001
E531920/04E 2008-08 © MTU

08 Introduction
TIM ID: 0000022787 – 001
E531920/04E 2008-08 © MTU

First steps 09
2 First steps
2.1 Preparations
Starting the program

To start DiaSys successfully, the following steps must be taken:
Program start...
• Select the user group
• Select the device type
• Create a new device description or open one
To work in online mode...
• Establish connection to the controller (“connect”)
To work in offline mode...
• Establish connection to the controller (“disconnect”)
Type of activity
Selection of the type of activity (activity group). Depending on the level of the hardware
plugged-in, the number of selectable user groups can be increased or decreased. The functions
offered by DiaSys depend on the user group selected
The following describes those functions available when selecting the “product support” user group. Only
a limited number of functions are available in the “customer” user group.
Select device type

Select device type This window is only activated if “No standard device type” is selected in the Options window.
TIM ID: 0000022788 – 001
E531920/04E 2008-08 © MTU

10 First steps
Using the small buttons“ ”, a graphical representation of the appropriate device or the system
can be called up in each case in order to facilitate identification.
TIM ID: 0000022788 – 001
E531920/04E 2008-08 © MTU

First steps 11
The screen once more vanishes when the mouse pointer is moved away from the figure or
if you press the “ESC” button on the keyboard.
Note:
• depending on the device type, various functions may be available in DiaSys.
TIM ID: 0000022788 – 001
E531920/04E 2008-08 © MTU

12 First steps
2.2 Device description

Enables you to select between create, open and edit device description. Opening a device description is a
prerequisite for working with DiaSys, to be able to use the functions from the “DiaSys used with governors” chapter.
For controllers ECU-1, ECU-4, ECU-7, ECU-183, CDS/CR the settings are saved in the central database. From
there they can be loaded into the local database on the computer using a modem or through the MTU-Network
connection (LAN) and then into the controller. If parameters are changed in the controller, then the changed
data record is to be saved back to the central database so that the current status of the controller remains
current. The “Establish connection to central database” function is available for data interchange.
With the “Options” button, the language (German or English) can be set for DiaSys as well as other settings.
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

First steps 13
The selection shown for the functions in the “Device description” window can vary
depending on the controller connected.
Functions in DEVICE DESCRIPTION with Level E E E E E E C C R

1B Hardware Key, depending on the controller C C C C C C D D 0
U U U U S U S S 8
- - - - - - / / 2
7 4 2 1 U 1 C C
N 8 R
I 3
Create device description X X X X X X X X X
Open device description X X X X X X X X X
Edit device description X X X X X X X X X
Establish connection to central database X X — X — X X — —
Transfer data using files X X — X — X X — —
Edit engine data in the local database X X — X — X — — —
Data in the local database — — — — — — X — —
Retrieve “ECU7info” from the central database X — — — — — — — —
Options X X X X X X X X X
X = function available
— = function not available
Create new device description

Creating a new device description means assigning a certain order number one or more engine numbers.
The DiaSys program will then create folders in which the data will be stored.
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

14 First steps
After clicking on the “New” button, the following window appears (see fig.) for inputting an engine number.
TIM ID: 0000022822 – 001
Note:
• Every order number must be linked to at least one engine number.
The “Available functions” window can only be accessed via this function and the “Open device
description” function (see chapter “DiaSys used with governors”).
E531920/04E 2008-08 © MTU

First steps 15
Open device description

Open device description means using an already saved device description again.
The “Available functions” window can only be accessed via this function and the “Create new device
description” function (chapter “DiaSys used with governors”).
Edit device description

Shows the available order numbers. The “Delete” function deletes all of the data for the
selected order number or the selected system name.
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

16 First steps
After clicking on the “Delete” button, the following confirmation prompt will appear:
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

First steps 17
Note:
• In this way an entire order (i.e. the entire plant) including all of the data transferred
from the controller to the PC will be deleted.
To remove individual engine numbers, proceed as follows. Engine parameter records in
the local database will not be removed.
After clicking on the “Edit” button, the following window appears:
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

18 First steps
In this window you can either create or delete a new engine number within an order.
After clicking on the “OK” button the window will close.
Establish connection to central database

Notes:
• Only available for controllers ECU-1, ECU-4, ECU-7, ECU-183 and CDS/CR .
• CDS/CR will be described in the next chapter.
After a connection has been established to the central database (either through a modem or the
MTU-network (LAN)), engine data records that are in the local database can be transferred back to the
central database. Furthermore, engine data records can be copied from the central database to the local
database. The engine number clearly identifies the corresponding data records.
Notes:
• The connection to the central database cannot be interrupted. In case of an error, it could take
up to 2 minutes for the DiaSys program to respond to the user’s input.
• If a connection via modem is made, the PC must not be connected to a local PC network
• Contrary to a LAN connection, when using a modem the user must connect to the central
database via the MTU IT Service Directory.
Note ECU-7 only:
TIM ID: 0000022822 – 001
• As soon as a connection is made to the central database and “ECU-7” is selected, the most current
version of “ECU7info” file will be automatically transferred to the PC if necessary.
Attention: Every time a connection is made to the central database, “Load controller” and “Delete and reload
controller” actions made with the ECU-7 controller will be reported back to the central database. Only the
actions are reported, the transfer of data - as usual - must be made by the user.
E531920/04E 2008-08 © MTU

First steps 19
There are two different types of data records in the local database:
Data record Contents of the data record
For controller These are the data that originate from the central database and are for the
(Data for controller) controller.
Actual data Here is where the current controller data are stored. Every changed to the
(Data from controller) controller is recorded. When transferring back the data record to the central
database, it is the “ActuaI data” that are transferred and then deleted from the
local database.
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

20 First steps
There can be two data records per engine number in the central database:
Data record Contents of the data record
Modernized data (specified Modernized date are stored here.

data)
Last actual data from The “Actual data from last transfer” are the data that have been read out of the
controller (actual data from controller. They will only match the current actual data record of the controller if
last transfer) they have been consistently transferred back into the central database.
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

First steps 21
1 Central database 3 Specified data 6 For controller (Data for controller)

2 Engine parameter record (MPS) 4 Actual data from last transfer 7 Local database
+ Functional software (FSW) 5 Actual data (data from controller) 8 Controller
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

22 First steps
Transfer parameter record to central database
Several engine data records can be transferred back to the central database. Mark the corresponding
box in the “Transfer” field for the engine numbers.
The “Next” button takes you directly to the “Retrieve parameter record from central database” window.
Only the actual data from the controller can be transferred to the central database. Clicking
on the “Transfer” button starts the data transfer.
Notes:
• When using a modem the user must connect to the central database via the MTU IT Service
Directory. DiaSys will then be started and the data exchange can be prepared with the
“Establish connection to central database” function.
• If an engine data record is transferred via modem or LAN to the central database, it will be
automatically deleted in the local database after the transfer in finished.
• The “Transfer data using files” function does not delete the engine data record in the local
database when “Export data” is used. After successful transfer of data, the user must delete the
data with the “Edit engine data in the local database” function.
Also see:
• Chapter “Establish connection to central database”
• Chapter “Retrieve parameter record from central database”
TIM ID: 0000022822 – 001
• Chapter “Transfer data using files”

• Chapter “Edit engine data in the local database”
E531920/04E 2008-08 © MTU

First steps 23
Retrieve parameter record from central database
When retrieving a parameter record from the central database the engine number must be entered. Furthermore, it
must be stated whether “Modernized data” or “Last actual data from controller” should be retrieved.
The “Next” button takes you to the next window (see next figure).
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

24 First steps
This contains more information on the parameter record for the engine number entered.
After clicking on the “Retrieve data” button, data transfer is started from the central database
to the local database on the computer.
If the selected data record is not available, the “Retrieve data” button is blocked.
Note: The FSW is also transferred if required.
Also see:
• Chapter “Transfer parameter record to central database”
• Chapter “Delete engine data in local database”
Establish connection to central database (for CDS/CR controllers only)

Note: This chapter only covers the CDS/CR controllers.
Step 1: Display of the number of data records that must be transferred to the central database (transfer back of data).
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

First steps 25
Step 2: Automatic transfer of data to the central database.

Step 3: Window for entering CDS/CR software numbers which are to be transferred from
the central database to the PC (to the local database).
Note:
• Only those users whose hardware key is authorized for this function at MTU can copy over
software from the central database to the PC. Error message: “You do not have the authorization
to load the functional software from the central database!”
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

26 First steps
Transfer data using files

Note: Only available for controllers ECU-1, ECU-4, ECU-7, ECU-183 and CDS/CR .
If data cannot be directly transferred using a modem or LAN then the engine data records can be transferred
using files. These files can be imported into another computer and then transferred via LAN or modem
from that computer to the central database (the opposite direction is also possible).
Export data
After clicking on the “Export files” button, the following window will appear.
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

First steps 27
If the target folder is not empty, then after clicking on the “Yes” button the following window appears:
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

28 First steps
If the start of the export is confirmed, the following window appears:
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

First steps 29
Selection Process
Export to file This shows the name of the file (any name), into which the data are to be
written. A standard name is automatically given.
Direction of data transfer This shows whether “Data for the central database” or “Data for controller” are
to be exported.
Type of data compression This determines whether one large file is to be created and saved to the disc
or if the file should be distributed to several discs. Sever smaller files will then
be created which can be copied onto the discs manually.
After clicking on the “Next” button, the following window appears (not for CDS/CR):
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

30 First steps
Enter which data (i.e. which engine numbers) are to be exported. Clicking on the corresponding
fields in the “Export” columns either selects or deselects the data.
When all engine numbers are selected, the report is started by clicking on the “Export” button. After
the transfer is successfully finished, the following window appears:
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

First steps 31
Import data
Before data can be imported the file must be unpacked. This file will unpack itself. First
copy it to any folder on the dialog unit (e.g. C:\TEMP).
By double clicking on the file (e.g. in WINDOWS™ Explorer), the following window will appear:
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

32 First steps
By clicking on the “Next >” button, the file will be unpacked and the data will be
automatically transferred to the correct folder.
Now the actual import can be started.
After clicking on the “Import data” button (see the “Selection window for export or import of files” figure
in chapter “Transfer data using files”), the following window will appear:
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

First steps 33
This message may only be confirmed with “Yes” if the file has already been unpacked as described earlier.
The following window will appear:
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

34 First steps
Enter which data (i.e. which engine numbers) are to be imported. Clicking on the corresponding
fields in the “Import” columns either selects or deselects the data.
Note: For ECU-7 and CDS/CR this window will not appear because all engine data records will be imported.
When all engine numbers are selected, the transfer is started by clicking on the “Import” button. After
the transfer is successfully finished, the following window appears:
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

First steps 35
Note: For CDS/CR, only data that are specifically for the central database can be exported or imported.
Edit engine data in the local database

Note: Only available for controllers ECU-1, ECU-4, ECU-7 and ECU-183.
Shows the available engine numbers. The “Delete” function deletes the engine data records in the local
database. The engine numbers marked in the “Delete” field will be deleted.
Note:
• Data records will be automatically deleted when transferred using a modem or LAN. There
is no automatic deletion when transferring using files.
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

36 First steps
Also see:
• Chapter “Transfer parameter record to central database”
• Chapter “Retrieve parameter record from central database”
Clicking on the corresponding fields in the “Delete” columns either selects or deselects the data.
As soon as at least one engine number is marked for deletion the “Delete” button will be available.
Data in the local database

Note: Only available for CDS/CR controllers.
The number of CDS/CR engine data records in the local database will be shown.
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

First steps 37
Retrieve “ECU7info” from the central database

Note: Only available for ECU-7 controllers.
Either a connection to the central database must be established or the PC must be connected to the MTU-LAN.
When the button is clicked: A check is made in the central database as to whether the “ECU7info” is more current
than that on the PC. If a more current version is available, this will be immediately copied over to the PC to be used.
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

38 First steps
Options
1 Selection of data to be logged 4 Button for showing the “Log.txt” file 6 Button for restoring standard
2 Setting the standard device type 5 Button for language selection settings
3 Setting the standard path
1. “What is logged”
In the “log.txt” file, the actions/messages are recorded depending on the log level. The “log.txt”
file is a text file designed as a ring memory.
2. “Standard device type”
If a “Standard device type” is given, this controller (or RCS/MCS) will be designated at the
start of the program as the default device type, i.e the device does not have to be manually
selected. The “Selection of device types” window is skipped.
3. “Standard path”
You can set a path different from the disc drive (A:) for various functions (e.g. Restore
maintenance indicator) to/from an external disc drive.
4. “Show ’Log.txt’ file”
TIM ID: 0000022822 – 001
Enables the “log.txt” file to be shown.

5. “Language selection”
Switches the active language for DiaSys user interface:
Click the “Switch language for DiaSys” with the mouse.
E531920/04E 2008-08 © MTU

First steps 39
Click “OK” button.

Confirm message with “OK”.
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

40 First steps
After restarting DiaSys, the desired language (German or English) can be selected:
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

First steps 41
6. “Standard setting”
The following settings will be restored to the default values:
Default value
What is logged “Error”
Standard device type “- No Standard device type -”
Standard path “A:\”

TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

42 First steps
TIM ID: 0000022822 – 001
E531920/04E 2008-08 © MTU

DiaSys used with governors 43
3 DiaSys used with governors
3.1 Overview of “Available functions”

The following figure shows which functions are available for a selected controller. (The windows may be
different depending on the controller connected and the user group selected).
TIM ID: 0000022823 – 001
E531920/04E 2008-08 © MTU

Functions in AVAILABLE FUNCTIONS E E E E E E C C R

with Level 1B Hardware Key, depending C C C C C C D D 0
on the controller
U U U U S U S S 8
- - - - - - / / 2
7 4 2 1 U 1 C C
N 8 R
I 3
Establish connection to controller X X X X X X X X X
Start recording of measurement data X X X X X X X X X
Stop recording of measurement data X X X X X X X X X
Evaluate measurement data X X X X X X X X X
Injector code — X — — — — — — —
TIM ID: 0000022823 – 001
Edit single parameters X X X X X X X X —
Edit 2D parameters X X X X X X X X —
Edit 3D parameters X X X X X X X X —
Send changed data to controller X X X X X X X X —
Logs X X X X X X X X —
E531920/04E 2008-08 © MTU

Functions in AVAILABLE FUNCTIONS E E E E E E C C R

with Level 1B Hardware Key, depending C C C C C C D D 0
on the controller
U U U U S U S S 8
- - - - - - / / 2
7 4 2 1 U 1 C C
N 8 R
I 3
Extras X X X X X X X X X
Operation data X — — — — — — — —
Maintenance indicator — X — X X O — — —
Load controller X X — X — X — — —
Load controller — — — — — — X — —
To menus X X X X X X X X X
X = Function available
- = Function not available
O = Function is available in DiaSys, but controller does not support this function
Establish connection to controller

The controller connected is contacted via a serial interface (COM1, COM2 or COM3) or via CAN. Interfaces that
are not connected, e.g. in this case COM3, remain open and are not linked to any engine number.
By clicking on the “Connect” button (switch closes) and then on the “OK” button, an online
connection to the controller is established (online mode).
If there is no connection or if the connection has been disconnected by clicking the “Disconnect” button, an
offline evaluation (e.g. from measurement data) is only possible (offline mode).
TIM ID: 0000022823 – 001
E531920/04E 2008-08 © MTU

Note:
• As long as the “Establish connection to controller” was not clicked an only the “OK” button was clicked,
most of the buttons in the “Available functions” will be grayed out and therefore not available.
TIM ID: 0000022823 – 001
E531920/04E 2008-08 © MTU

3.2 Measurement data
Start recording measurement

Start recording measurement data without trigger
Selected measurement data can be read-out from the controller. It can be stored and represented graphically.
Note: The following window only appears when it is activated (as required).
If no trigger has been defined or no trigger is to be selected then “No” is to be clicked in the following window.
This window is used for selecting measuring points.

TIM ID: 0000022825 – 001
E531920/04E 2008-08 © MTU

Designation Description
Available Available measuring points of the selected device

measuring points
Group of Here you can select a stored group

measuring points
For data List of the selected measuring points

recording
Select all measuring points
Selects the marked measuring points in “Available measuring points”. Single measuring
points can also be selected by double-clicking.
To mark several measuring points, drag your mouse over the desired measuring points or
click on several measuring points keeping the Ctrl button pressed.
TIM ID: 0000022825 – 001
E531920/04E 2008-08 © MTU

Deselects the marked measuring points in “data recording”. Single measuring points can also
be deselected by double-clicking.
Deselect all measuring points
Templates
Export Available templates for selecting the measuring points to be recorded can be copied into a
project-independent template database from within the current device description. They can
then be accepted at a later point into another device description via “Import”.
Import Templates for the selection of the measuring points to be recorded can be accepted into the
current device description from the project-independent template database.
New Creates a new template name within the current device description. The measuring points
must then be subsequently selected and “Save” must be run.
Delete Templates can be deleted from the current device description.
Save A selected template can be changed. The changes are accepted by “Save”.
Save as If no template is selected then a new template is created by “Save as”.

If a template is selected, then an existing or opened and changed template can be stored
under a new name by “Save as”.
After measuring points have been found for displaying, the sampling time must be entered.
recording begins after clicking the “OK” button!
After setting the sampling time, the measuring points for the measuring data list are selected and
then, analogous to this, the measuring points for the y(t) curve.
Note: The “Available functions” dialog window is minimized before the graphical display of the data. in order,
e.g. to stop the recording of measurement data, the window must again be maximized.
Refer also to:
• “Stop recording measurement data” chapter
• “Evaluate measurement data” chapter
• “Select active trigger” chapter
• “Recording properties” chapter
• “Offline and online Y(t) graphic” chapter
Select an active trigger
Measurement data recording can also be started by trigger conditions. A trigger can be composed
of one or more logically linked start or stop conditions. If the trigger condition is met then the
recording of measurement data starts or stops.
A trigger definition (creating triggers) is only possible in the menu-oriented screen.
The trigger is selected in the following window:
TIM ID: 0000022825 – 001
E531920/04E 2008-08 © MTU

Stop recording measurement data

Stops the data recorder. The recording can be stored under any file name by clicking the “Yes” button.
TIM ID: 0000022825 – 001
E531920/04E 2008-08 © MTU

Evaluate measurement data

Opens stored data for offline processing.
TIM ID: 0000022825 – 001
E531920/04E 2008-08 © MTU

This dialog box is used for selecting measuring points.
TIM ID: 0000022825 – 001
E531920/04E 2008-08 © MTU

Available Available measuring points of the selected recording

measuring points
Stored graphics Here you can select a stored group

or lists
Selected for List of the selected measuring points

display
Select all measuring points
Selects the marked measuring points in “Available measuring points”. Single measuring
points can also be selected by double-clicking.
TIM ID: 0000022825 – 001
E531920/04E 2008-08 © MTU

Deselects marked measuring points in “Selected for display”. Single measuring points can
also be deselected by double-clicking.
Deselect all measuring points
Templates
Export Available templates for selecting the Y(t) display measuring points can be copied into a
project-independent template database from within the current device description. These can
then be accepted at a later point into another device description via “Import”.
Import Templates for the selection of the Y(t) display measuring points can be accepted into the
current device description from the project-independent template database.
Time interval Here you set the time period shown when opening the Y(t) curve.
Note: If the menu window is set under Extras | Settings| Y(t) curve in such a way that the
entire curve is to be displayed on opening then the time interval setting is ineffective..
Additionally, an extra time interval can be defined (“Time interval” button). The data is
shown graphically after clicking the “OK” button.
Refer also to:
• “Start recording measurement data” chapter
• “Stop recording measurement data” chapter
• “Offline and online Y(t) graphic” chapter
Offline and online Y(t) graphic
Window
The temporal course of measurement values is shown in this window.
TIM ID: 0000022825 – 001
E531920/04E 2008-08 © MTU

1 Reference to the measuring-point 2 Unit

list 3 Measuring-point list
TIM ID: 0000022825 – 001
E531920/04E 2008-08 © MTU

Measuring-point list
A All relevant functions have an effect on the marked

measuring points. The colored (shaded) marking
corresponds to the color in which the curve is
displayed in the diagram.
B Reference to axle
C Device number
D Measuring point number
E Name of the measuring point
Note: The print function is called by the key combination Ctrl + P.
Context menu for offline and online Y(t) graphic
4 context menus can be called up on the following areas (PopUp menus, place mouse cursor
on appropriate field and click right mouse button).
TIM ID: 0000022825 – 001
E531920/04E 2008-08 © MTU

1 Axle labeling of Y axle 3 Display range

2 Axle labeling of X axle 4 Measuring-point list
TIM ID: 0000022825 – 001
E531920/04E 2008-08 © MTU

3.3 Parameters
Edit single parameters

First, a window opens where you can select the single parameters.
The selected parameters are then shown in a window. The properties window is opened
by pressing key combination Ctrl + Alt + P.
Notes:
The selection window (edit single parameters, edit 2D parameters and edit 3D parameters) can be changed in width.
The entry windows (single parameters, 2D parameters and 3D parameters) can be changed in height and depth.
When device type “ECU-7” is selected, there are additional special windows for entering single parameters
(refer to the “Edit input and output settings” chapter, “Edit protection/monitoring parameters”)
Refer also to:
• “Edit 2D-parameters” chapter
• “Edit 3D-parameters” chapter
TIM ID: 0000022827 – 001
Edit 2D-parameters
First, a window opens to select the characteristic curve (2D parameter).
E531920/04E 2008-08 © MTU

The selected characteristic curve is then shown in a window.
Edit 3D-parameters
First, a window opens to select a performance map (3D parameter).
TIM ID: 0000022827 – 001
E531920/04E 2008-08 © MTU

The selected performance map is then shown in a window.
TIM ID: 0000022827 – 001
E531920/04E 2008-08 © MTU

3.4 Injector code

If the injector codes have been changed and the “Send” button has been clicked then a window of this type is displayed:
TIM ID: 0000022828 – 001
If the changes are required then the data can be sent to the controller by once more clicking the “Send” button.
E531920/04E 2008-08 © MTU

3.5 Send changed data to controller

When parameters are changed, the following type of window appears:
After clicking on the “Send” button, the changed data start to transfer to the controller.
After clicking on the “Cancel” button, you return to the superordinate window.
ParNo Parameter number
Parameter Parameter designation
Type Types of changed parameters (dimension, axis with index)
PC value New value to be transferred
Active value Old value to be overwritten
Unit Measurement unit of parameter

TIM ID: 0000022851 – 001
For 2D and 3D parameters a query window will be opened (not for ECU-7):
E531920/04E 2008-08 © MTU

Note: If all parameters are identical, the following window will open: Please click the “OK” button.
TIM ID: 0000022851 – 001
E531920/04E 2008-08 © MTU

3.6 Transmit to controller

Notes:
• Only available for controllers ECU-1, ECU-4, ECU-7, ECU-183 and CDS/CR .
• CDS/CR is described in the next chapter!
Engine data records (functional software and engine parameter sets) can be copied to the controller.
They must be available in the local database. Two functions are provided:
• 1. Transmit engine parameter record to the controller
• 2. Delete the controller and retransmit (not available for MDEC-ECU C1)
The first function must always be used.
Exception: The controller hardware has been replaced and must be completely deleted and
retransmitted. The second function may only be used in this case.
Refer also to:

• “Transmitting the engine parameter record to the controller” (only possible online)
• “Deleting and reloading the controller” chapter (only possible offline)
Transmit engine parameter record to the controller
Note: Only available for controllers ECU-1, ECU-4, ECU-7 and ECU-183.
This is the normal function when engine parameter records are to be transmitted
from the local database into the controller.
The requirement for this is that a connection to the controller has been established (online mode). Additionally, the
engine number from the device description and the controller must exist in the local database. The parameters
on the controller are deleted and retransmitted. DiaSys decides whether it is necessary to copy new FSW
onto the controller. If it is determined that the engine parameter record in the local database is older than
that in the engine parameter record then confirmation is explicitly requested from the user:
TIM ID: 0000022829 – 001
E531920/04E 2008-08 © MTU

If the entries in the local database are from a later date then the engine parameter record is immediately copied.
Refer also to:
• “Delete and retransmit to controller”
Delete and retransmit to controller
Note: Only available for controllers ECU-4, ECU-7 and ECU-183.
ECU-4: The load profile data of the controller is deleted by this measure and no longer automatically transmitted
to the controller. The maintenance indicator may only be stored once the engine has stopped.
Careful: All data (operating hours, load profile, etc.) in the controller is deleted. The engine parameter
record and the functional software is then subsequently retransmitted.
The requirement for this is that the engine number exists from the device description in the local database.
The connection to the controller must not be established in this case (offline mode) to ensure that this function
can be addressed (refer to chapter “Establishing a connection to the controller”).
TIM ID: 0000022829 – 001
E531920/04E 2008-08 © MTU

This dialog box must be confirmed with “OK” as shown above in order to establish an offline connection.
The previously shaded out button “Delete and retransmit to controller” is then once more available.
The connecting cable between the computer and the controller must be connected as data is to be
exchanged (programming mode, refer to chapter “Terms and definitions”).
TIM ID: 0000022829 – 001
click the “OK” button to transmit FSW and MPS data to the controller.
E531920/04E 2008-08 © MTU

As shown in the order of the window above, the following steps must be run one after the other:
• Switch off the controller.
• Confirm with OK.
• Switch the controller back on within 30 seconds.
Transmission starts once all requirements have been fulfilled (can be recognized by the following animation):
TIM ID: 0000022829 – 001
E531920/04E 2008-08 © MTU

Note: Please be patient. The duration of the transmission is not known in advance and can take up to 10 minutes.
Note:
• To now completely accept all of the retransmitted data into the controller, it must be subjected
to a “power-on reset”. The controller must therefore be switched off and then back on (not for
ECU-7). This must be confirmed with OK as shown in the figure above.
The controller data that has just been transmitted is now read in and then the controller is in readiness.
TIM ID: 0000022829 – 001
E531920/04E 2008-08 © MTU

Refer also to:

• “Transmit engine parameter record to the controller” chapter
Transmit to controller (here, only the CDS/CR controller)

Note: This chapter only describes the CDS/CR controller.
The function can be carried out in offline mode with a serial connection from the controller to the PC.
After entering the software code number, transfer of data to the controller is started.
TIM ID: 0000022829 – 001
E531920/04E 2008-08 © MTU

TIM ID: 0000022829 – 001
E531920/04E 2008-08 © MTU

3.7 Logfiles
The following figure presents an overview of all existing logfiles.
TIM ID: 0000022830 – 001
E531920/04E 2008-08 © MTU

Functions in LOGFILES with Level E E E E E E C C R

1B Hardware Key, depending on the C C C C C C D D 0
controller
U U U U S U S S 8
- - - - - - / / 2
7 4 2 1 U 1 C C
N 8 R
I 3
Error logfile X X — X X X X O —
Delete error logfile X X — X X X — X —
Export error logfile — X — X X X X X —
Modification logfile X X X X X X X X —
Parameter modified by X X — — X X X X —
TIM ID: 0000022830 – 001
EOL parameter modified by — — — — — — X — —
Display units info — — — — — — X — —
Units ID — X X X X X X X —
E531920/04E 2008-08 © MTU

O = available/not available depending on functional controller software
Error logfile
Note: The screen content looks different on the ECU-7. Not all functional software of the CDS/C supports this function.
Opens a window to display the error messages error logfile). Sorts the error messages chronologically.
A pop-up menu can be opened with the right mouse button:

TIM ID: 0000022830 – 001
E531920/04E 2008-08 © MTU

Delete error logfile

Note: Not all functional software of the CDS/C supports this function.
The content of the error memory in the controller is deleted.
Export error logfile

Note: Not available for ECU-7 controller. Not all functional software of the CDS/C supports this function.
The content of the error memory is exported to Excel.
Modification logfile
Parameter changes are automatically recorded by DiaSys. Opens the window to display the parameter changes.
The parameter changes made via the opened device description are logged.
The following procedures are logged:
• selecting a device
• parameter changes
• import
• opening the device description
TIM ID: 0000022830 – 001
The following is shown in the window:

• date/time
• type of activity (with extensions when required))
E531920/04E 2008-08 © MTU

• description:
Type Description
Use Opened by the user
Dev Device selected
Cha Parameter change
Note: This information is also deleted on deleting the device description.
Parameter changed by...

Note: The screen content looks different on the ECU-7.
parameter changes are logged and stored in the controller. This function opens a window showing the log. The log
stores details of who has made changes to the parameters. The date of the change is also stored.
Note: This information is stored in the controller.
EOL parameter modified by

Displays the history of the changed EOL parameters and the changed engine configuration.
Display units info

Information is displayed on the connected hardware.
Units ID
Shows information on the controller such as, e.g. the number of error messages. Design
and content depends on the respective controller.
TIM ID: 0000022830 – 001
E531920/04E 2008-08 © MTU

TIM ID: 0000022830 – 001
E531920/04E 2008-08 © MTU

3.8 Extras
Displays the active hardware key information, the engine number (the “Extras” windows looks
slightly different, depending on the controller).
Functions in EXTRAS with Level 1B E E E E E E C C R

Hardware Key, depending on the C C C C C C D D 0
controller
U U U U S U S S 8
- - - - - - / / 2
7 4 2 1 U 1 C C
N 8 R
I 3
Export into Excel-file... X X X X X X X X —
Import an Excel-file... — — X X X X X X —
Hardware key info X X X X X X X X X

TIM ID: 0000022842 – 001
Show alive signal X — — — — — — — —
Show ECU-7 “alive” signal X — — — — — — — —
Show engine number X X — — — X O — —
Calibrate actuator — — — — — — — X —
E531920/04E 2008-08 © MTU

Functions in EXTRAS with Level 1B E E E E E E C C R

Hardware Key, depending on the C C C C C C D D 0
controller
U U U U S U S S 8
- - - - - - / / 2
7 4 2 1 U 1 C C
N 8 R
I 3
Test actuator — — — — — — — X —
Delete functions — — — — — — — X —
Standardizing injection volume — — — — — — X — —
Standardizing torque — — — — — — O — —
Edit engine configuration — — — — — — X — —
Data provision — — — — — — X — —
Show load profile — — — — — — X X —
Select language X — — — — — — — —
Show header information X — — — — — — — —
Read out Leakage map X — — — — — — — —
Read out crash recorder X — — — — — — — —
Show CCS info X — — — — — — — —
Show hardware CCS X — — — — — — — —
Show CCS tree X — — — — — — — —
Injector functions O O — — — — O — —
Edit alarm parameters X — — — — — — — —
Edit Input and Output settings X — — — — — — — —
Edit protection-/monitoring parameter X — — — — — — — —
O = depends on the controller hardware and/or functional software of the controller available/not available
Export into Excel-file...

The current
• parameter values
• error messages (for ECU-7, only from DiaSys 2.50)
• data of the maintenance indicator (for ECU-7, only from DiaSys 2.50)
TIM ID: 0000022842 – 001
• modification log
can be exported to any directory as required.
E531920/04E 2008-08 © MTU

Hardware key info

This window shown information on the hardware key.
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

Registered user Registered user
Serial number Serial number of the hardware key
Validity period Shows the date up to which the hardware key is valid.
Qualification level Shows the qualification level released in the hardware key.
Qualified for Shows which device a qualification is released for. The registered user can
only write-access these device types.
Show alive signal

The data content of the signal alive signal of the ECU-7 and of the CAN devices connected
to the CAN bus (field bus) can be displayed.
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

Show ECU-7 “alive” signal

The data content of the “Alive” signal of the ECU-7, which is periodically transmitted via the CAN bus, is shown.
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

Bit Text Meaning
0 Application active 0: application loader is active

1: application is active
1 Engine running 0: engine not running

1: engine running
2 Light mode 0: controller running in normal mode

1: controller running in light mode (at least one parameter record module
does not exist in the controller)
3 Life data Backup active 0: Life data Backup of the ECU is inactive
1: Life data Backup of the ECU is active
4-7 Currently not defined
Source info Here, the content of bit numbers 7 to 0 are shown as decimals.
Even bits not yet defined by DiaSys are shown.
Example:
Bit 0 set
Bit 1 set
Source info is then 3
Variant Shows the variant, edition number and beta number (for released software,
the beta is always 0)
Edition major If the controller software exists in the controller then the variant, etc. of the
Edition minor system software is shown.
If there is no controller software in the controller then the variant, etc. of the
Beta application loader is shown.
TIM ID: 0000022842 – 001
Show engine number

Note: Only available for controllers ECU-4, ECU-7, ECU-183 and CDS/CR .
The engine number is stored internally. This number can be displayed by “Show engine number”.
E531920/04E 2008-08 © MTU

Calibrate actuator
Note: Only available for CDS/C controllers.
Due to the tolerances of injection mechanics, the performance of produced or overhauled (standard)
production engines is rather spread. To compensate for the performance tolerances, all engines are
subjected to performance calibration after production. The user is provided with numerous useful
hints for performing this task via the “Calibrate actuator” button.
Test actuator
The “Test actuator” button is intended for maintenance and customer service mechanics. With its help,
it is possible to move the fuel rack from zero to full throttle position when the engine is at standstill.
Blocking and stiffness of the fuel rack can be identified in this way.
Delete functions
There are the following delete functions:
• Load profile and operating hours
• Cyclical switch
Standardizing the injection volume

The window for standardizing the injection volume is displayed.
Standardizing the torque

The window for standardizing the torque is displayed.
Edit engine configuration

TIM ID: 0000022842 – 001

The window for standardizing the engine configuration is displayed.
Data provision
E531920/04E 2008-08 © MTU

There are two functions available under “Data provision”:

• “controller exchanged”
• “life data”
Data is read-out from the CDS/CR controller and made available so that it can later be transmitted
to the central database. If the data is to be made available after the controller has been
exchanged then “controller exchanged” must be used.
If only the “life data” of the controller is to be made available for the central database then “life data” should be used.
Show load profile

Note: Only available for CDS/C and CDS/CR controllers.
The load profile is shown as a 3D graphic and as a 32*32 matrix in hours (or can also be
switched-over in seconds via the right mouse button).
The load profile can be rotated along all axles using the mouse. In case of a mouse with two buttons,
keep both buttons pressed and rotate the curve by the mouse movement. In case of a mouse with
three buttons, this is done by keeping the middle button pressed.
Select language
The language of the device description (parameter and measuring point texts) can be selected
via this function. DiaSys does not have to be restarted.
Furthermore, the language of the DiaSys interface can also be switched-over. To do this,
you must close DiaSys and then restart it.
Show header information

TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

Window
Function for advanced users

Displays the information from the header of the descriptor module and the parameter module of the engine and plant.
Read out Leakage map

The leakage map can be read out from the controller. This leakage map can not be displayed by DiaSys. After
transmission, a success message is issued detailing the storage path and the file name.
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

Read out crash recorder

The crash recorder module can be read out from the controller. The information contained
in the module can not be displayed by DiaSys 2.40. After transmission, a success message
is issued detailing the storage path and the file name.
Show CCS info

The CCS info of files with CCS structure can be displayed.
Show hardware CCS

TIM ID: 0000022842 – 001
The CCS info of the hardware is displayed.
E531920/04E 2008-08 © MTU

Show CCS tree

The CCS info of the hardware and software of the controller is displayed.
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

Injector functions
Note: Only available for controllers ECU-4, ECU-7 and CDS/CR (which support this function).
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

An injector test function is normally integrated into the controller to detect defective injectors.
This function is activated by the interactive software and run by the controller. The cylinders are
thereby switched off one after the other and the change of speed and the volume is logged. This
allows you to make conclusions regarding a possibly defective injector.
There are two alternative test procedures available (full engine or half engine, i.e. cylinder cutout)
in order to simulate the various border conditions of the system.
The test is started by the “Start test” button. After conclusion of the test by the controller,
the test result can be shown via the “Evaluation” button:
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

The results can be printed and exported from here.
Edit alarm parameters

TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

The alarm parameter to be edited is shown at the top right. You can jump to the previous/next alarm
parameter in steps using the and arrows.
In the “Active” column, you can set the attributes of the selected parameter in the “Name” column.
Edit Input and Output settings

TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

The transistor outputs of engines TO1 to TO4 can be configured here:

• Assignment to a process variable
• Signal inversion: not inverted/inverted
• not inverted: If the value of process variable = 1, then current is applied to TO
• inverted: If the value of process variable = 0, then current is applied to TO
• Wire break/short-circuit monitoring: yes/no
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

The transistor outputs of plants TOP1 to TOP4 can be configured here:

• Signal inversion: not inverted/inverted
• not inverted: If the value of process variable = 1, then current is applied to TOP
• inverted: If the value of process variable = 0, then current is applied to TOP
• Wire break/short-circuit monitoring: yes/no
• Switch: High Side/Low Side
• High Side: 24 Volt are connected
• Low Side: The ground is connected
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

Analog outputs AO1 and AO2 can be configured:

• Gain (factor)
• Offset in Volt
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

The binary inputs (channel 0 to channel n) can be configured:

• Channel active: yes/no
• Input (ECU input channel)
• Active High: yes/no
• Bouncing time in seconds
• Sensor defect delay in seconds
• Use replacement value for SD: yes/no
Edit protection-/monitoring parameter

Note: Only available for ECU-7 controllers that also support this function together with DiaSys 2.40 SP1.
If the function is not supported by the controller then you get the following message:
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

The protection/monitoring parameter to be processed is selected in the “Limit” field. You can jump to the
previous/next parameter in steps using the and arrows.
The mode is selected in the “Protection-Mode” selection box in the “Protection” tab. The corresponding
protection parameters can then be set in the lower part of the window.
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

The corresponding monitoring parameters are set in the “Monitoring” tab. If there is a corresponding
limit value curve, then this can be opened directly from within this window
TIM ID: 0000022842 – 001
E531920/04E 2008-08 © MTU

3.9 Injector exchange (DiaSys 2.52 SP1 and higher)

Preconditions
• Injector(s) have been exchanged; In the following example, injector A2 was exchanged.
• Device description is open.
• Connection between DiaSys and engine governor is established.
Select function: “Extras” — “Injector functions” — “Injector exchange”
1. Selecting this function will open a window.
2. The window elements have the following meaning:

• Button “Tag all”: All buttons “A1...Axx” and B1 ... Bxx” will be enabled.
• Button “Untag all”: All buttons “A1...Axx” and B1 ... Bxx” will be disabled.
• Buttons “A1 ... Axx” and B1 ... Bxx”:
• xx for 8-cylinder engines = 4
TIM ID: 0000034308 – 001
After the activating the button, the corresponding button, the related display fields“Operating hours” and
“Virtual runtime” are set to “0”.
• Display field “Operating hours”: Operating time of the engine with the relevant injector installed.
• Display field “Virtual runtime”: Weighted runtime of the relevant injector (for internal analysis by MTU)
• Button “Save”: To save the input changes
• Button “Undo”: To undo the last saving process. However, this is only possible as long as the window
“Injector exchange” is open.
• Button “Close”: To close the "Injector exchange” window.
E531920/04E 2008-08 © MTU

Procedure
1. Exchange injector.
2. Connect DiaSys and establish connection to engine governor.
3. Select function “Extras” — “Injector functions” — “Injector exchange”.
4. Select buttons of all exchanged injectors (in the illustration, only injector 2 was exchanged).
Result: The time information shown in the display fields “Operating hours” and “Virtual runtime” of all
exchanged injectors is set to “0”.
TIM ID: 0000034308 – 001
E531920/04E 2008-08 © MTU

Saving
1. Select “Save” button.
Result: This will open a warning window.
2. Enter the serial number of the hardware key used in the entry field.
3. Select “Next” button.
Result: The entered values are saved in the engine governor. Now the engine is operated with the new values.
“Undo” function
Note: This function allows the user to undo the last saving process if the injector selection was made
incorrectly.
1. Select “Undo” button.

Result: All previous runtime values are restored and displayed in the display field “Operating hours”.
2. Resetting the operating hours for exchanged injectors can be started again.
TIM ID: 0000034308 – 001
E531920/04E 2008-08 © MTU

3.10 To menus
Depending on the hardware key, the controller and the user group selected, you can change over to the menu screen.
More functions are available in the menu screen. It is intended for the experienced user. You
can exit back out via “Extras - Task oriented operation”.
Note: A connection to the central database cannot be established in the menu screen.
TIM ID: 0000022843 – 001
E531920/04E 2008-08 © MTU

3.11 Engine history data

No. Description
1 Load profile The load profile is shown as a 3D graphic and as a 50*50 matrix in hours (or can
also be switched-over in seconds via the right mouse button).
The “Engine speed ” and “Set torque” values are used for division of the load
profile.
The load profile can be rotated along all axles using the mouse. In case of a
mouse with two buttons, keep both buttons pressed and rotate the curve by
the mouse movement. In case of a mouse with three buttons, this is done by
keeping the middle button pressed.
2 Load variation counter The load variation counter for engine, ETC 1, ETC 2, ETC 3 and ETC 4 (can
be switched-over using the right mouse button) are shown as a 3D graphic
and a 15*15 matrix.
During load variation counting, the monitored measured value (set torque or
loader speed 1 - 4) is entered in a “from-to” matrix.
3 Turbo charger switching The turbo charger switching counter is shown as a 3D graphic and a 10*10
counter matrix.
The turbo charging state is entered in a “from-to” matrix in the turbo charging
switching counter.
4 Startcounter The coolant temperature and oil temperature start counters (can be
switched-over via the right mouse button) are shown as 2D graphics and value
lists.
After each completed start, a check is made whether the measurement value is
within the temperature classes of the start counter. If yes, then the appropriate
counter is increased by one
TIM ID: 0000023436 – 001
5 Rotation counter The oil pressure rotation counter is shown as a 2D graphic and a value list.
On starting at a low oil pressure (< 1.0 bar ), the engine rotations are counted
below 300 rpm and then classified depending on the oil pressure.
Note: A context menu is called up via the right mouse button. You can print from here.
The display is also switched-over from here.
E531920/04E 2008-08 © MTU

3.12 Maintenance forecast

Note: Only available for controllers ECU-1, ECU-7 and ECS-UNI.
The following figure shows an overview of all functions related to the maintenance forecast.
Functions in MAINTENANCE E E E E E E C C R
FORECAST with Level 1B Hardware C C C C CS C D D 0
Key, depending on the controller
U U U U - U S S 8
- - - - U - / / 2
7 4 2 1 N 1 C C
I 8 R
3
Confirm scheduled maintenance — — — — X — — — —
Scheduled maintenance dates — — — — X — — — —
Shift maintenance schedule — — — — X — — — —

TIM ID: 0000022844 – 001
Load depending maintenance dates — — — — X — — — —
Confirm load depending maintenance... — — — — X — — — —
Load profile — X — X X — — — —
Endurance matrix — — — — X — — — —
E531920/04E 2008-08 © MTU

Functions in MAINTENANCE E E E E E E C C R
FORECAST with Level 1B Hardware C C C C CS C D D 0
Key, depending on the controller
U U U U - U S S 8
- - - - U - / / 2
7 4 2 1 N 1 C C
I 8 R
3
TBO Parameter — — — — X — — — —
Tolerance of maintenance dates — — — — X — — — —
Modify K factor — — — — X — — — —
New Ti matrix — — — — X — — — —
Restore... — X — X X — — — —
Save all (for restoration) — X — X X — — — —
Save data for evaluation — X — X X — — — —
Confirm scheduled maintenance

Note: Only available for ECS-Uni.
Scheduled maintenance dates are acknowledged here. The maintenance interval
and due date are shown in the window.
Mark the appropriate maintenance and click the “confirm” button.
Refer also to:
• “Scheduled maintenance dates” chapter
Scheduled maintenance dates

The log for scheduled maintenance dates is shown here.
The dates are shown in their temporal order. If execution of maintenance has been confirmed
then the date of maintenance is shown.
Refer also to:
• “Confirm scheduled maintenance” chapter
Shift maintenance schedule

The defined scheduled maintenance dates can be shifted in their entirety by a certain time period.
The dates can be shifted by 240 months max. In case of “Approaching maintenance date”, the next maintenance
date is before the shift. In case of “New date”, the new date is after the shift.
Enter the number of months by which the maintenance date is to be shifted and click the “OK” button.
TIM ID: 0000022844 – 001
Refer also to:

• “Confirm scheduled maintenance” chapter
Load depending maintenance dates

Here, the log for load-dependent maintenance is shown.
E531920/04E 2008-08 © MTU

The log includes details of how many operating hours have elapsed after a maintenance has been
acknowledged (run). The deviation from the due date is shown under “Deviation”.
Refer also to:
• “Confirm load depending maintenance” chapter
Confirm load depending maintenance

This window is used to acknowledge load-dependent maintenance. Mark the maintenance to be
confirmed and click “Confirm”. The due date of the maintenance is shown in the right column in
hours. You can also see here whether maintenance is due.
The current operating hours are shown under “Operating hours”.
Refer also to:
• “Load depending maintenance” chapter
Load profile
Displays the load profile of the connected device.
The load profile curve can be rotated around all axles using the mouse. In case of a mouse with two
buttons, keep both buttons pressed and rotate the curve by the mouse movement. In case of a mouse
with three buttons, this is done by keeping the middle button pressed.
TIM ID: 0000022844 – 001
Note: To use the data for an evaluation, they must be stored on a diskette using the “Save data for
evaluation” function as described in the “Save data for evaluation” chapter.
A context menu pops up when you press the right mouse button, in the gray area, between
the data window and the view window.
E531920/04E 2008-08 © MTU

The next and the previous levels can be displayed with the “Alt >” and “Alt <” buttons.
Endurance matrix
Shows the endurance (Ti matrix) of the engine. The expected lifetime of the engine can be viewed
here . The endurance matrix of the engine is constant and set by the MTU.
The endurance curve can be rotated around all axles using the mouse. In case of a mouse with two
buttons, keep both buttons pressed and rotate the curve by the mouse movement. In case of a mouse
with three buttons, this is done by keeping the middle button pressed.
A context menu pops up when you press the right mouse button, in the gray area, between
the data window and the view window.
TIM ID: 0000022844 – 001
TBO-Parameter
This window is used for displaying and entering the TBO parameters. The values to the left can
be edited. The values to the right are planned or current values.
If data is changed then you can accept the new data with the “Close” button or discard them with “Cancel” .
E531920/04E 2008-08 © MTU

TBO The expected lifetime of the engine
Operating hours Operating hours of the engine
Offset Time by which maintenance services have been carried out too early.
This time is subtracted from the calculated lifetime of the engine.
K-constant A constant set by the MTU
Start-TBO A constant set by the MTU
Max. TBO A constant set by the MTU
TBO Offset A constant set by the MTU
Speed (0) Idling speed of the engine
FRP (0) Fuel rack position during idling of engine

TIM ID: 0000022844 – 001
Power (0) Idling power of the engine
Speed (max.) Maximum speed of the engine
FRP (max.) Fuel rack position during full throttle of engine
Power (max.) Maximum power of the engine
E531920/04E 2008-08 © MTU

FRP factor Standardization factor
FRP offset Standardization factor offset
Refer also to:

• “K-constant” chapter
Tolerance of maintenance dates

New tolerances to confirm the load-dependent maintenance dates are set in this window.
The tolerance in which confirmation can be made can be set for each maintenance type.
The tolerances are listed as percentages of the due date.
Modify K constant
This window is used to change the K constant.
The K constant is a value set by the MTU.
Note: This function must be carried out when the engine is at standstill. The load profile must be
saved previous to this (refer to chapter “Save all for restoration”).
New Ti matrix
A new endurance matrix (TI matrix) can be read in by a data medium here.
A file selection window opens on clicking “Search” and you can now select the appropriate file. The file
must have a “mit” extension. The TI matrix is directly transmitted into the device
Note: This function must be carried out when the engine is at standstill. The load profile must be
saved previous to this (refer to chapter “Save all (for restoration)”).
Restore...
Restores a previous backup of the maintenance forecast from diskette. The diskette used for this
must have been created using the “Save all (for restoration)” function.
This is required, e.g. after replacing the hardware.
Careful: Restoration of the maintenance forecast may only be run once the engine has stopped.
Refer also to:
• “Save all (for restoration) chapter”
Save all (for restoration)

Saves the data from the maintenance forecast onto diskette to restore later (refer also to the “Restore”
chapter). You should have an empty, formatted diskette for this.
This data can not be used for an evaluation. For this, you must use the function described
in the “Save data for evaluation” chapter.
A progress bar is shown in the status line. Follow the instructions in the dialog box.
Careful: The maintenance indicator may only be stored once the engine has stopped.
TIM ID: 0000022844 – 001
Refer also to:

• “restore” chapter
Save data for evaluation

Saves the data (load profile, etc.) in Excel format for later evaluation.
E531920/04E 2008-08 © MTU

TIM ID: 0000022844 – 001
E531920/04E 2008-08 © MTU

MEM module programming 111
4 MEM module programming
4.1 Prepare for BDM programming

MEM memory modules can be programmed. To use this function, you require a backup data module
and a suitable connection cable (refer to the following figure).
1 Plug for the display 2 Blue heat-shrinkable hose
Connector assignment of the cable (MTU code number 535 530 75 34)
Connector assignment is as follows:
9 pin Sub-D FB-1 plug Potential
BDM Display
7 81 61 CAN-H
2 82 62 CAN-L
TIM ID: 0000022845 – 001
3 83 63 CAN-GND
Note:
• 60 Ω must be measured between pins 81 and 82 (bus termination resistance).
E531920/04E 2008-08 © MTU

Requirements before using

The following requirements must be fulfilled to use this function:
• The dialog PC must be equipped with a CAN board.
• A dongle (hardware key) with CAN customer support access is required.
• There must be a backup data module (BDM) with device software (GSW) from V3.02.
• Using the E2_PROGR.OUT program, check whether Option 0 (Station Type) is assigned
by PPS (refer to the following figure)
• There must be four directory levels below the base directory (this is indicated by the BDM settings).
The data must be in the fourth directory. Otherwise, the “Programming” button is not released.
The names and content of the higher levels are meaningless.
• The path for the source of the programming procedure can be selected under “MCS-5/RCS-5”, “Options”,
“BDM Settings” (e.g. CD, Diskette). The directory depth must remain as it is (refer to the above).
Attention: Except for the BDM, the DIS 10 to DIS 13 can also be used for programming the MEM-5
module via the CAN interface. For more details, refer to the DIS description.
Notes:
• Different directories are defined for the basic software and the “PU” data.
• Already programmed MEM-5 modules are overwritten without a prompt.
• To program the MEM-5 modules, the BDM and the interactive software must be set to the same baud rate.
An example of a correct setting is provided in the following example:
TIM ID: 0000022845 – 001
Note:
• If the transmission rate (Option 3 in the figure above, marked by an *) is not set to 125 kbaud then the
BDM download function (data transmission from the BDM to the plant) no longer functions.
Programming is carried out as follows:
“Product support” must be selected in the selection of the activity group (type of activity).
E531920/04E 2008-08 © MTU

Refer also to:

• “Type of activity” chapter
Device (unit) type MCS-5/RCS-5 must be selected.
TIM ID: 0000022845 – 001
E531920/04E 2008-08 © MTU

Prepare for BDM programming
Start preparation by clicking the “Prepare BDM programming” button. In the following window, you must indicate
whether the directory structure is to be created from configuration data (PU) or basic software.
TIM ID: 0000022845 – 001
E531920/04E 2008-08 © MTU

In the next step, you enter the order number and the index number for the order:
TIM ID: 0000022845 – 001
E531920/04E 2008-08 © MTU

The data available must then be selected:
TIM ID: 0000022845 – 001
E531920/04E 2008-08 © MTU

On clicking the “Select” button, a window appears in which the corresponding file can be found.
TIM ID: 0000022845 – 001
E531920/04E 2008-08 © MTU

Once all required information has been entered, preparation for BDM programming is
completed by clicking the “Execute” button.
TIM ID: 0000022845 – 001
E531920/04E 2008-08 © MTU

TIM ID: 0000022845 – 001
E531920/04E 2008-08 © MTU

4.2 Programming mode
Select programming mode by clicking on the “Programming mode...” button.
TIM ID: 0000023437 – 001
E531920/04E 2008-08 © MTU

As soon as the requirements for a safe system state are ensured (BDM is connected to the dialog PC, the
power supplies are connected and stable), then you should click the “OK” button.
In the “Type of data” panel, you should make your selection for “’PU’ data” or “Basic software”
in the windows in accordance to the two following figures.
TIM ID: 0000023437 – 001
E531920/04E 2008-08 © MTU

TIM ID: 0000023437 – 001
E531920/04E 2008-08 © MTU

The path (directory levels) must accord to the examples provided above, otherwise
the “Program” button is not released.
In the “PCMCIA-channel” panel, select the CAN interface used at the PC end.
In the “Baudrate” panel, you can also select a transmission rate of 400 kbaud. However, this presupposes
that the transmission speed in the BDM has also been set to 400 kbaud using the E2_PROGR.OUT
program. In this case, the BDM download function no longer works.
This high transmission speed is suitable for programming the MEM module.
The transmission speed must therefore always be reset to 125 kbaud after concluding the download.
After clicking the “Program” button, the programming procedure is started.
The previously described notice (according to the figure “Signalize readiness”) must again be confirmed. The
dialog system establishes an online connection to the BDM (green panel, bottom right).
Once everything has been correctly set, you can see a progress check of the programming
in accordance to the following figure.
Note:
• From the 32 blocks to be programmed, only the assigned blocks are transmitted to the BDM. In the
example provided by the following figure, these are only a total of 8 blocks.
TIM ID: 0000023437 – 001
E531920/04E 2008-08 © MTU

After completion of programming, a control screen appears logging the programming procedure.
TIM ID: 0000023437 – 001
This completes the programming procedure.

Note:
• In older versions (DiaSys, device software) irrelevant error messages are issued
when programming the ’PU’ data.
E531920/04E 2008-08 © MTU

Templates 125
5 Templates
5.1 Templates
Templates are used for storing collected selection lists within a device description in order
to run the selection faster in the future.
Storing template is - with one exception - only possible on the menu screen. You can also
access stored templates in the button screen.
Attention: Deleting a device description also deletes all templates for this device description.
Templates can be exported and imported (not for device type “MCS-5/RCS-5”), so that they
• can also be used in other device descriptions
• are not lost when deleting the device description.
Create and store templates
Templates can be created from:
• the selection of single parameters
• the selection of measuring points for data recording (also in the button screen)
• arranging the y(t) display
• measurement data lists
• bar graphics
Storage of a template is in the menu screen, each in a newly displayed menu between the
“Parameter” menu and the “Extras” menu.
Exception: The selection of measuring points for data recording is already made in the selection window
and can therefore be made both in the menu screen and the button screen.
Save: Selection of single parameters
TIM ID: 0000022848 – 001
E531920/04E 2008-08 © MTU

126 Templates
Save: Arrangement of the y(t) display
TIM ID: 0000022848 – 001
E531920/04E 2008-08 © MTU

Templates 127
Save: Measurement data list

TIM ID: 0000022848 – 001
E531920/04E 2008-08 © MTU

128 Templates
Save: Bar graphic
Export and import templates

The export or import is always made in the corresponding selection window via the “Export” or “Import” buttons.
TIM ID: 0000022848 – 001
E531920/04E 2008-08 © MTU

Templates 129
Export/Import templates: Selection of single parameters

TIM ID: 0000022848 – 001
E531920/04E 2008-08 © MTU

130 Templates
Import templates: Selection of single parameters
TIM ID: 0000022848 – 001
E531920/04E 2008-08 © MTU

Templates 131
5.2 Index
D Measurement data ..................... 47
Device description ..................... 12
O
E Overview of “Available functions” .......... 43
Engine history data . . . . . . . . . . . . . . . . . . . . . 103
Extras . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 P
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
G Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . 09
General information on the DiaSys Prepare for BDM programming . . . . . . . . . . . . 111
program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 03 Programming mode . . . . . . . . . . . . . . . . . . . . 120
I S
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Send changed data to controller ........... 62
Injector code . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Injector exchange (DiaSys 2.52 SP1 and T
higher) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
To menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
L Transmit to controller . . . . . . . . . . . . . . . . . . . 64
Logfiles .............................. 71
M
Maintenance forecast ................... 104
TIM ID: 0000022848 – 001
E531920/04E 2008-08 © MTU

Manual MTU

Uploaded by

Copyright:

Available Formats

Manual MTU

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual MTU

Uploaded by

Copyright:

Available Formats

MTU_ValueService

E531920/04E 2008-08 © MTU

E531920/04E 2008-08 © MTU

1.1 General information on the DiaSys program

Terms and definitions

ADEC Advanced Diesel Engine Controller

MDEC MTU Diesel Engine Controller

Functional software (FSW) Operating software of the controller.

CCS Compatibility Check System

E531920/04E 2008-08 © MTU

Setting the CAN hardware used

E531920/04E 2008-08 © MTU

Ctrl + P Print The active window is printed - if possible.

Explanations on Ctrl + Shift + A:

E531920/04E 2008-08 © MTU

TIM ID: 0000022787 – 001

E531920/04E 2008-08 © MTU

E531920/04E 2008-08 © MTU

TIM ID: 0000022787 – 001

E531920/04E 2008-08 © MTU

Starting the program

Select device type

E531920/04E 2008-08 © MTU

TIM ID: 0000022788 – 001

E531920/04E 2008-08 © MTU

E531920/04E 2008-08 © MTU

2.2 Device description

TIM ID: 0000022822 – 001

E531920/04E 2008-08 © MTU

Functions in DEVICE DESCRIPTION with Level E E E E E E C C R

Create device description X X X X X X X X X

Open device description X X X X X X X X X

Edit device description X X X X X X X X X

Establish connection to central database X X — X — X X — —

Transfer data using files X X — X — X X — —

Edit engine data in the local database X X — X — X — — —

Data in the local database — — — — — — X — —

Retrieve “ECU7info” from the central database X — — — — — — — —

Create new device description

E531920/04E 2008-08 © MTU

TIM ID: 0000022822 – 001

E531920/04E 2008-08 © MTU

Open device description

Edit device description

E531920/04E 2008-08 © MTU

TIM ID: 0000022822 – 001

E531920/04E 2008-08 © MTU

E531920/04E 2008-08 © MTU

Establish connection to central database

E531920/04E 2008-08 © MTU

Data record Contents of the data record

E531920/04E 2008-08 © MTU

Data record Contents of the data record

Modernized data (specified Modernized date are stored here.

E531920/04E 2008-08 © MTU

1 Central database 3 Specified data 6 For controller (Data for controller)

E531920/04E 2008-08 © MTU

Transfer parameter record to central database

• Chapter “Transfer data using files”