Sie sind auf Seite 1von 104

ServicePublication

DiaSys 2.xx
Dialogsoftwarefor
MTUsystems
E 531920/ 02E
DaimlerChrysler Powersystems Off-Highway
DocumentationPart2
PrintedinGermany
E 2002Copyright MTU FriedrichshafenGmbH
Diese Verffentlichungeinschlielichaller seiner Teile ist urheberrechtlichgeschtzt. J ede Verwertungoder Nutzungbedarf der vorherigen
schriftlichenZustimmungder MTU FriedrichshafenGmbH. Das gilt insbesondere fr Vervielfltigung, Verbreitung, Bearbeitung,
bersetzung, Mikroverfilmungenunddie Einspeicherungund/ oder VerarbeitunginelektronischenSystemen, einschlielichDatenbanken
undOnline-Diensten.
Das Handbuchist zur VermeidungvonStrungenoder SchdenbeimBetriebzubeachtenunddaher vomBetreiber demjeweiligen
Wartungs- undBedienungspersonal zur Verfgungzustellen.
nderungenbleibenvorbehalten.
PrintedinGermany
E 2002Copyright MTU FriedrichshafenGmbH
This Publicationis protectedby copyright andmay not be usedinany way whether inwhole or inpart without the prior writtenpermissionof
MTU FriedrichshafenGmbH. This restrictionalso applies to copyright, distribution, translation, microfilmingandstorage or processingon
electronic systems includingdata bases andonline services.
This handbook is providedfor use by maintenance andoperatingpersonnel inorder to avoidmalfunctions or damage duringoperation.
Subject to alterations andamendments.
Imprim enAllemagne
E 2002Copyright MTU FriedrichshafenGmbH
Tout droit rserv pour cet ouvrage dans sonintgralit. Toute utilisationouexploitationrequiert aupralable laccordcrit de MTU
FriedrichshafenGmbH. Ceci sapplique notamment la reproduction, la diffusion, la modification, la traduction, larchivage sur microfiches,
la mmorisationet / oule traitement sur des systmes lectroniques, y compris les bases de donnes et les services enligne.
Le manuel devra tre observ envue dviter des incidents oudes endommagements pendant le service. Aussi recommandons-nous
lexploitant de le mettre la dispositiondupersonnel charg de lentretienet de la conduite.
Modifications rserves.
Impreso enAlemania
E 2002Copyright MTU FriedrichshafenGmbH
Esta publicacinse encuentra protegida, entoda suextensin, por los derechos de autor. Cualquier utilizacinde la misma, as como su
reproduccin, difusin, transformacin, traduccin, microfilmacin, grabaciny/o procesamiento ensistemas electrnicos, entre los que se
incluyenbancos de datos y servicios enlnea, precisa de la autorizacinprevia de MTU FriedrichshafenGmbH.
El manual debe tenerse presente para evitar fallos o daos durante el servicio, y, por dicho motivo, el usario debe ponerlo a disposicindel
personal de mantenimiento y de servicio.
Nos reservamos el derecho de introducir modificaciones.
Stampato inGermania
E 2002Copyright MTU FriedrichshafenGmbH
Questa pubblicazione protetta dal diritto dautore intutte le sue parti. Ciascunimpiego odutilizzo, conparticolare riguardo alla
riproduzione, alla diffusione, alla modifica, alla traduzione, allarchiviazione inmicrofilmedalla memorizzazione odallelaborazione in
sistemi elettronici, comprese banche dati e servizi online, deve essere espressamente autorizzato per iscritto dalla MTU Friedrichshafen
GmbH.
II manuale va consultato per evitare anomalie o guasti durante il servizio, per cui va messo a disposizione dall utente al personale addetto
alla manutenzione e alla condotta.
Conriserva di modifiche.
ISO9001certification
Quality assurance in design/development, production, installation and service
MTUassuringyou:
CE conformity
-- Guideline 73/23/EEC Lowvoltage guideline
dated February 19, 1973 with amendment dated J uly 22, 1993
(guideline 93/68/EEC)
-- Guideline 89/336/EEC Guideline on electromagnetic compatibility
dated May 3, 1989 with amendment dated April 28, 1992
(guideline 92/31/EEC)
CE conformity is influencedif the product is installedincorrectly, anassembly or systemis misused
and/or genuine MTU components are not used.
Guide Page I
E 531 920 / 02 E -- 05.2002 --
Tableof contents
Table of contents I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Abbreviations IV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General information about documentation V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Safetyrequirements 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 General informationabouttheDiaSys program 6 . . . . . . . . . . . . . . . . . . . .
2.1 Use 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Terms and definitions 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Programinfo 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Preparation 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Starting the program 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Type of activity 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Select type of unit 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Units assembly description 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 Newunits assembly description 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2 Open units assembly description 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3 Delete units assembly description 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.4 Install transmission line to central database 18 . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.4.1 Transmit parameter set to central database 20 . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.4.2 Load set of parameters fromcentral database 21 . . . . . . . . . . . . . . . . . . . . . . . .
3.4.5 Import fromdisk, export to disk 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.5.1 Export data 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.5.2 Import data 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.6 Edit engine data fromlocal database 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.7 Options 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.7.1 Select language 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.7.2 Display logfile Log.txt 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Guide Page II
E 531 920 / 02 E -- 05.2002 --
Tableof contents (cont.)
4 DiaSys inusewithcontrollers 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Establish data link to controller 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Start data recording 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Start recording of measured data without trigger 40 . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Select an active trigger 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 Properties of recording 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Stop recording 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 Evaluate recorded data 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1 Offline and online y(t) graphic 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2 Context-sensitive menus for offline and online y(t) graphic 47 . . . . . . . . . . . . .
4.5 Modify single-parameter 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6 Modify 2D-parameter 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7 Modify 3D-parameter 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.8 Injector code 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.9 Transmit modified data to controller 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.10 Transmit to controller 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.10.1 Transmit set of engine parameters 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.10.2 Delete controller and transmit anew 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.11 Logfiles 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.11.1 Error logfile 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.11.2 Modification logfile 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.11.3 Parameter modified by ... 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.11.4 Units ID 63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.12 Extras 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.12.1 Export into Excel-file 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.12.2 Import Excel-file 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.12.3 Hardware Key Info 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.12.4 Showengine number 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.13 To menus 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Guide Page III
E 531 920 / 02 E -- 05.2002 --
Tableof contents (cont.)
4.14 Maintenance forecast 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.1 Confirmscheduled maintenance 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.2 Scheduled maintenance dates 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.3 Shift maintenance schedule 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.4 Load depending maintenance dates 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.5 Confirmload depending maintenance 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.6 Load profile 75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.7 Endurance matrix 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.8 TBO-parameter 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.9 Tolerance of maintenance dates 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.10 Modify K-constant 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.11 NewTi Matrix 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.12 Restore 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.13 Save all 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14.14 Save data for evaluation 83 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 ProgrammingMEMmodules 86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Prepare for BDMprogramming 90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Programming mode 93 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Guide Page IV
E 531 920 / 02 E -- 05.2002 --
Abbreviations
Note: This list does not contain common English abbreviations.
C Degrees Celsius
% Percent
CE Conformit Europenne, European conformity (European Union mark of
approval)
DIN Deutsches Institut fr Normung, German National Standards Institute;
formerly: Deutsche Industrienorm, German Industrial Standard
ECS Engine Control System(engine management systemand controller)
EMC Electromagnetic Compatibility
EN European Norm(CEN standard)
f Frequency
g Gravity acceleration constant (9.81 m/s
2
)
Hz Hertz
IEC International Electrotechnical Commission
IP International Protection, index of protection in accordance with
DIN 40 050, part 9
kg Kilogram
m Meter
min Minute
mm Millimeter
ms Millisecond
V Volt
Guide Page V
E 531 920 / 02 E -- 05.2002 --
General informationaboutdocumentation
Documentationstructure
Documentation
Part
Title/contents Targetgroup
withthelowestlevel of qualification
1 Structure and function Operating personnel
2 Operation Operating personnel
3 Maintenance and repair
(Operating personnel)
Operating personnel charged with
maintenance
4 Maintenance and repair
(Specialist personnel)
Specialist personnel charged with
maintenance
5 Illustrated parts catalog Operating personnel charged with
maintenance
6 Plant-specific
configuration
Specialist personnel charged with
maintenance
7 Installation and
initial start-up
Start-up personnel
Note: Not all documentation parts are written for every product!
Requiredknowledge
To understand each part of the documentation, we recommend reading the preceding
parts, if applicable.
Referencenumbers andreferencelines
Details in figures are provided with reference numbers and reference lines if necessary.
If reference is made in the text to a detail provided with a reference number, the figure
number and, separated by an oblique, the reference number of the detail are written in
brackets. Example: (5/2) means fig. 5, reference number 2.
A point at the end of the reference line means that the detail is visible in the
figure.
An arrowat the end of the reference line indicates that the detail cannot be
seen in the figure.
Guide Page VI
E 531 920 / 02 E -- 05.2002 --
Symbols
The symbols used in safety notes are defined in the chapter Safety requirements.
This symbol indicates cross-references to other manuals.
This symbol indicates cross-references to other chapters (in this manual)
containing further information about the function concerned.
Safety requirements
Chapter 1
Page 1
E 531 920 / 02 E -- 05.2002 --
Chapter 1
Safetyrequirements
Chapter 1
2 Page
Safety requirements
E 531 920 / 02 E -- 05.2002 --
(This page intentionally blank)
Safety requirements
Chapter 1
Page 3
E 531 920 / 02 E -- 05.2002 --
1 Safetyrequirements
I MPORT ANT
Thesesafetyrequirements shall bereadandobservedbyall
personnel involvedinoperation, care, maintenanceor repair of the
products concerned.
Furthermore, the following shall be observed:
The safety requirements (if provided) in other relevant MTU manuals
Warning and safety notes and operating and limit values attached to the
products as required
National accident prevention and safety standards
Appropriate regulations usual in the industry
The safety notes (if provided) in the text of this manual
Conventions for safetynotes inthetext
Where necessary, this manual includes highlighted safety notes marked with a signal
word. These safety notes shall be observed to avoid injury or damage.
This type of note indicates a danger which may lead to injuryor
death.
DANGER
This type of note indicates a danger which may lead to damage
or destructionof the product described or another part of the
system.
CAUTION
Intendeduseanduser qualifications
All devices and systemcomponents may only be put to their intended use.
Operation, maintenance and repair shall only be performed by qualified and authorized
personnel.
Chapter 1
4 Page
Safety requirements
E 531 920 / 02 E -- 05.2002 --
Safetyrequirements for startingup
Before first using the electronic product, it must be installed in accordance with the in-
structions and be approved in accordance with MTU specifications.
Whenever the unit or systemis taken into operation
All maintenance and repair work must have been completed.
Any loose parts must have been removed fromrotating machine components.
Nobody is allowed within the range of moving machine components.
Immediately after taking the unit or systeminto operation, the control and display ele-
ments as well as the monitoring, signalling and alarmsystems must be suitably tested for
proper operation.
Operational safetyrequirements
The emergency procedures must be practiced on a regular basis.
The operator must be familiar with the control and display elements.
The operator must knowthe effects of any action to be performed by him.
The operator must proceed with the individual steps as specified in the documentation.
During operation, the display elements and monitoring assemblies must be supervised
with respect to current operating states, adherence to limit values as well as warnings and
alarmmessages.
If a fault is recognized or indicated by the system, the appropriate steps must be taken im-
mediately and the fault must be reported to the person in charge.
Every message must be evaluated immediately. Emergency countermeasures shall be
taken as required, e.g. emergency engine stopping.
General information DiaSys
Chapter 2
Page 5
E 531 920 / 02 E -- 05.2002 --
Chapter 2
General informationaboutthe
DiaSys program
Chapter 2
6 Page
General information DiaSys
E 531 920 / 02 E -- 05.2002 --
2 General informationabouttheDiaSys program
2.1 Use
The DiaSys programis required to communicate with various MTU controllers, RCS-5
Remote Control Systems and MCS-5 Monitoring and Control Systems.
The main features of the DiaSys programare:
Data exchange with the central database
Controller parameter setting
Data recording
Note: This manual primarily contains information pertaining to the use of the DiaSys
programin conjunction with controllers. Functions are described which require
a level 1B hardware key (service/distributor). Menu functions are not documen-
ted in this manual.
2.2 Terms anddefinitions
The following terms are used in this manual:
Term Meaning
Online mode The controller is connected to the serial interface and able
to receive commands fromDiaSys.
Offline mode The controller is not connected to the serial interface.
Previously saved data can be processed (e.g. evaluating
measured data) only.
Functional software (FSW) Controller operating software. Online connection to the con-
troller is not possible in the absence of FSW.
Engine parameter set
(MPS)
These are controller operating parameters (referenced by
the engine number in the central database).
General information DiaSys
Chapter 2
Page 7
E 531 920 / 02 E -- 05.2002 --
2.3 Programinfo
Description
This windowdisplays programinformation, version number, copyright, date and time. This
windowalways appears on starting the program.
Fig. 1 : Programinformation
A general safety warning appears after clicking the OKbutton to warn operators about
the dangers of incorrect operation and programming of the connected devices.
Fig. 2 : Safety warning
The next programwindowappears on clicking the OKbutton.
Clicking the Cancelbutton exits the program.
Chapter 2
8 Page
General information DiaSys
E 531 920 / 02 E -- 05.2002 --
(This page intentionally blank)
Preparation
Chapter 3
Page 9
E 531 920 / 02 E -- 05.2002 --
Chapter 3
Preparation
Chapter 3
10 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
3 Preparation
3.1 Startingtheprogram
The following steps are always necessary in order to start DiaSys successfully:
Programstart-up ...
Select the type of activity
Select the type of unit
Select units assembly description
To work in Online mode ...
Establish data link to controller (Connect)
To work in Offline mode ...
Establish data link to controller (Disconnect)
3.2 Typeof activity
Description
Selects the type of activity (user group). The number of users available for selection may
vary depending on the level of the active hardware key. The functions provided by the
DiaSys programdepend on the type of activity selected.
Fig. 3 : Type of activity
Preparation
Chapter 3
Page 11
E 531 920 / 02 E -- 05.2002 --
3.3 Selecttypeof unit
Description
Selects the type of unit. This windowis only active when No default type of unitis selec-
ted in the Options window.
Fig. 4 : Select type of unit
Clicking the small buttons opens a graphic representation of the device/systemcon-
cerned in order to facilitate its identification.
Fig. 5 : Graphic representation of a device showing Engine Control Unit ECU as an example
The picture disappears again when the mouse pointer is moved out of the picture or when
the ESCkey is pressed on the computer keyboard.
Chapter 3
12 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
Note: The range of functions available in DiaSys may vary depending on the type of
unit selected.
3.4 Units assemblydescription
Description
Allows creation of a newunits assembly description and opening or deleting existing ones.
Opening a units assembly description is a basic requirement for working with DiaSys.
Settings are stored in the central database for the MDEC-ECU C2 and ECU-183 control-
lers. These settings can be loaded into the local database on the computer via modemor
a link to the MTU network (LAN) and subsequently loaded into the controller. Any changes
made to parameters in the controller require the modified data set to be transmitted back
to the central database to ensure that the current status of the controller is also available
there. The Install transmission line to central databasefunction is provided to facilitate
the exchange of data.
The Optionsbutton allows the DiaSys language to be toggled between German or
English.
The Units assembly descriptionwindowmay offer a somewhat limited range of functions
depending on the controller connected.
Preparation
Chapter 3
Page 13
E 531 920 / 02 E -- 05.2002 --
Fig. 6 : Units assembly description
Function Availablefor:
Newunits assembly description All controllers
Open units assembly description All controllers
Edit units assembly description All controllers
Install transmission line to central database MDEC-ECU C1,
MDEC-ECU C2 and ECU-183
Transfer data by file MDEC-ECU C1,
MDEC-ECU C2 and ECU-183
Edit engine data in the local database MDEC-ECU C1,
MDEC-ECU C2 and ECU-183
Options All controllers
Chapter 3
14 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
3.4.1 Newunits assemblydescription
Description
Creating a newunits assembly description involves assigning one or more engine num-
bers to a specific order number. The DiaSys programautomatically creates directories in
which data are stored.
Fig. 7 : Create a newunits assembly description
The windowbelow(fig. 8) which allows an engine number to be entered appears on
clicking the Newbutton.
Fig. 8 : Enter engine number
Note: Every order number must be linked to at least one engine number.
The Available functionswindow(see chap. 4) is only accessible in this way and via the
Open units assembly descriptionfunction.
Preparation
Chapter 3
Page 15
E 531 920 / 02 E -- 05.2002 --
3.4.2 Openunits assemblydescription
Description
Opening a units assembly description involves reusing an existing units assembly descrip-
tion.
The Available functionswindow(see chap. 4) is only accessible in this way and via the
Newunits assembly descriptionfunction.
Fig. 9 : Open units assembly description
Chapter 3
16 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
3.4.3 Deleteunits assemblydescription
Description
Displays available order numbers. All data pertaining to the selected order number or
selected plant name are deleted with the Deletefunction (engine parameter sets stored
in the local database are not deleted).
Fig. 10 : Delete units assembly description
The following prompt appears on clicking the Deletebutton:
Fig. 11 : Confirming Delete units assembly description
Note: This deletes an entire order (i.e. the entire plant). Proceed as described below
in order to delete individual engine numbers.
Preparation
Chapter 3
Page 17
E 531 920 / 02 E -- 05.2002 --
The windowbelowappears on clicking the Editbutton:
Fig. 12 : Windowfor selecting an individual engine number
A newengine number can be created for an order in this windowor an individual engine
number deleted fromthe order.
The selected function is carried out on clicking the OKbutton.
Chapter 3
18 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
3.4.4 Install transmissionlineto central database
Note: Applies to MDEC-ECU C1, MDEC-ECU C2 and ECU-183 controllers only!
Description
After establishing a link to the central database (either via a modemor directly via the
MTU network (LAN)), engine data sets stored in the local database can be copied back to
the central database. It is also possible to fetch data fromthe central database. The
engine number identifies the relevant data sets unambiguously.
Note: In contrast to the LAN connection, the user must establish the link to the MTU
network via communication software when a modemis used.
Fig. 13 : Transmit parameter set to central database
A differentiation is made between two different types of data set in the local database:
Dataset Datasetcontents
For cintroller
(data for the controller)
This data stems fromthe central database and is intended for
the controller.
Current data
(data of the controller)
The current data of the controller is shown here. Any changes at
the controller are recorded. On copying a data set back to the
central database, the current datais always returned and sub-
sequently deleted in the local database.
Preparation
Chapter 3
Page 19
E 531 920 / 02 E -- 05.2002 --
Fig. 14 : Load set of parameters fromcentral database
Two data sets may be available for each engine number in the central database:
Dataset Datasetcontents
Modernized data
(desired data)
Modernization data is stored here.
Latest nominal data
(current data last
copied back)
The Latest nominal datais the data read-out of the controller.
Only corresponds to the current data set of the controller when
copied back to the central database regularly.
Chapter 3
20 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
Desired data
Current data
last copied
back
Current data
(data fromthe
controller)
Data for the
controller
MDEC-ECUC2
Engine parameter set (MPS)
+
Functional software (FSW)
Central database
Local database
Fig. 15 : Data exchange with the central database
3.4.4.1 Transmitparameter setto central database
Fig. 16 : Transmit parameter set to central database
Several engine data sets can be copied back to the central database on transmitting.
Mark the checkbox of the appropriate engine number in the Transmitfield.
Preparation
Chapter 3
Page 21
E 531 920 / 02 E -- 05.2002 --
Click the Cancelbutton to gain direct access to the Load set of parameters fromcentral
databasewindow.
Only the current data of the controller can be transmitted to the central database!
Data transfer commences on clicking the Transmitbutton.
Note: The communication software must be started beforehand and the connection
established to the provider. DiaSys is then started and data exchange started
with the Install transmission line to central databasefunction.
Refer to:
Chap. 3.4.4 Install transmission line to central database
Chap. 3.4.4.1 Load set of parameters fromcentral database
Chap. 3.4.5 Import fromdisk, export to disk
Chap. 3.4.6 Delete engine data in local database
3.4.4.2 Loadsetof parameters fromcentral database
Fig. 17 : Load set of parameters fromcentral database
The engine number must be stated to load a parameter set fromthe central database.
Also state whether modernized dataor the Latest nominal dataare to be loaded.
Access the next window(fig. 18) by clicking the Continuebutton.
Chapter 3
22 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
Fig. 18 : Parameter set info
Provides detailed information about the parameter set of the engine number entered pre-
viously.
Data is transmitted fromthe central database to the local database of the computer on
clicking the Fetch databutton.
The Fetch databutton is not enabled if the desired data set is unavailable.
Note: The FSWis also transmitted if required.
Refer to:
Chap. 3.4.4 Install transmission line to central database
Chap. 3.4.4.1 Transmit parameter set to central database
Chap. 3.4.5 Import fromdisk, export to disk
Chap. 3.4.6 Delete engine data in local database
Preparation
Chapter 3
Page 23
E 531 920 / 02 E -- 05.2002 --
3.4.5 Importfromdisk, exportto disk
Note: Applies to MDEC-ECU C1, MDEC-ECU C2 and ECU-183 controllers only!
Description
Engine data sets can be exported to disk if it is not possible to transmit data via modemor
LAN. These data sets can be imported to another PC and subsequently transferred to the
central database via LAN or modem(vice-versa also possible).
Fig. 19 : Option windowfor exporting or importing data
This windowdefines whether data is to be imported to the DiaSys programin order to
then transfer it to a controller (import) or whether data which has been read-out of a con-
troller is to be saved (exported) for purposes of archiving or analysis.
Clicking the Cancelbutton returns to the previous window.
Chapter 3
24 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
3.4.5.1 Exportdata
The windowbelowappears on clicking the Export databutton:
Fig. 20 : Information about data export
If the target directory stated in this windowis not empty, the programdeletes all files in
this directory when the Yesbutton is clicked in the windowbelow:
Fig. 21 : Warning, data deleted
Preparation
Chapter 3
Page 25
E 531 920 / 02 E -- 05.2002 --
The following windowappears after confirming export:
Fig. 22 : Transfer data by file Setup
Option Result
Export into file The name of the file (random) into which the data is
to be written is stated here. A default name is auto-
matically entered.
Direction of data transfer Determines whether data is exported for the central
database or exported for the controller.
Type of data compression Determines whether one single large file is created
for storage on a data mediumor whether the file is
to span a number of disks. Several small files which
can be copied to disk are created in this case.
Chapter 3
26 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
The windowbelowappears on clicking the Continuebutton:
Fig. 23 : Selecting data
It is nownecessary to state which data (i.e. the data of which engine number) is to be
exported. The data is marked with an xin the Exportcolumn. The selection is reversed
by clicking the appropriate box.
Once all the desired engine numbers have been selected, the transmission can be started
by clicking the Exportbutton. The windowbelowappears on (successful) completion of
the transmission:
Fig. 24 : Confirmation of successful export
Preparation
Chapter 3
Page 27
E 531 920 / 02 E -- 05.2002 --
3.4.5.2 Importdata
Pre-requisite
The file concerned must first be extracted before data can be imported. This file is self-
extracting. It must be copied into a randomdirectory on the dialog unit (e.g. C:\TEMP).
The extract programstarts automatically as soon as the file is double-clicked (e.g. in
WINDOWSt Explorer). The windowbelowthen appears:
Fig. 25 : Extract program
Clicking the Next >button starts data extraction and the data is automatically copied into
the correct directory.
Note: The partition in which the extract programruns must be smaller than 3 GB. The
extract programcan otherwise not be started.
Chapter 3
28 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
The actual import procedure can nowbe started.
The text box belowappears immediately after clicking the Import databutton (in the
DiaSys program):
Fig. 26 : Information about data import
Only ever confirmthis message with Yeswhen extraction has been carried out as des-
cribed on page 27.
Preparation
Chapter 3
Page 29
E 531 920 / 02 E -- 05.2002 --
The windowbelowthen appears:
Fig. 27 : Import of engine data set
It is nownecessary to state which data (i.e. data of which engine number) is to be impor-
ted. The data is marked by an xin the Importcolumn. Clicking the appropriate field
reverses selection.
Chapter 3
30 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
Having selected all desired engine numbers, transmission is started by clicking the
Importbutton. The windowbelowappears after (successful) completion of the transmis-
sion:
Fig. 28 : Confirmation of successful import
Preparation
Chapter 3
Page 31
E 531 920 / 02 E -- 05.2002 --
3.4.6 Editenginedatafromlocal database
Note: Applies to MDEC-ECU C1, MDEC-ECU C2 and ECU-183 controllers only!
Description
Indicates available engine numbers. Engine data sets in the local database are deleted
with the Deletefunction. The engine numbers marked in the Deletefield are deleted.
Note: Data sets are automatically deleted on transferring data via modemor LAN.
Automatic deleting does not take place on transferring via disk.
Fig. 29 : Delete engine data fromlocal database
Refer to:
Chap. 3.4.4 Install transmission line to central database
Chap. 3.4.4.1 Transmit parameter set to central database
Chap. 3.4.4.2 Load set of parameters fromcentral database
Chap. 3.4.5 Import fromdisk, export to disk
Chapter 3
32 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
The Deletebutton is enabled as soon as at least one engine number is marked with an
xin the Deletecolumn (clicking the appropriate field reverses the selection):
Fig. 30 : Deleting engine data fromthe local database
Preparation
Chapter 3
Page 33
E 531 920 / 02 E -- 05.2002 --
3.4.7 Options
Description
Options facilitate the selection of the information logging level created in the log.txtfile
during a DiaSys session. Allows the log.txtfile to be displayed and the language to be
selected (German or English). Standard values can also be re-established with Default
settings.
If a Default type of unitis listed, it becomes the default controller when the programis
started and manual controller type selection is omitted in this case.
If No default type of unitis selected, the Select type of unitwindowis not omitted.
Fig. 31 : Options
Refer to:
Chap. 3.4.7.1 Select language
Chap. 3.4.7.2 Display logfile Log.txt
Chapter 3
34 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
3.4.7.1 Selectlanguage
Description
Switches the active language in DiaSys (between German or English).
Activate the Switch programlanguage of DiaSyscheckbox with the mouse.
Fig. 32 : Switch programlanguage
Proceed as follows to change the language for DiaSys:
Click the Okbutton
Confirmthe message which appears with OK.
Fig. 33 : Select language prompt
Preparation
Chapter 3
Page 35
E 531 920 / 02 E -- 05.2002 --
Note: The windowshown belowonly appears after DiaSys has been restarted.
Select desired language:
Fig. 34 : Select language
Proceed as follows to change the language for DiaSys:
Click the Okbutton.
DiaSys then restarts with the selected language.
Chapter 3
36 Page
Preparation
E 531 920 / 02 E -- 05.2002 --
3.4.7.2 DisplaylogfileLog.txt
Description
The log.txtfile records all events in a DiaSys session stating date and time. This makes
it possible to understand sequences of events. Screen outputs are recorded in particular.
log.txtis a simple text file (ring memory design).
Fig. 35 : Example of a log.txt file
DiaSys in use with controllers
Chapter 4
Page 37
E 531 920 / 02 E -- 05.2002 --
Chapter 4
DiaSys inusewithcontrollers
Chapter 4
38 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4 DiaSys inusewithcontrollers
Descriptionof theAvailablefunctionswindow
This windowindicates the functions which are available for the unit concerned.
(The windows may vary slightly depending on the type of controller connected and the
selected type of activity).
Fig. 36 : Available functions
Refer to:
Chap. 4.2 Start data recording
Chap. 4.3 Stop recording
Chap. 4.4 Evaluate recorded data
Chap. 4.1 Establish data link to controller
Chap. 4.8 Injector code
Chap. 4.5 Modify single-parameter
Chap. 4.6 Modify 2-Dparameter
Chap. 4.7 Modify 3-Dparameter
Chap. 4.9 Transmit modified data to controller
Chap. 4.11 Logfiles
Chap. 4.12 Extras
Chap. 4.14 Maintenance forecast
Chap. 4.10 Transmit to controller
Chap. 4.13 To menus
DiaSys in use with controllers
Chapter 4
Page 39
E 531 920 / 02 E -- 05.2002 --
4.1 Establishdatalinkto controller
Description
When the controller is connected it is addressed via a serial interface (COM1, COM2 or
COM3). Interfaces which are not connected, e.g. COM3 in this case, remain empty, i.e.
they are not linked to an engine number.
The controller is connected to the serial interface on clicking the Connectbutton (switch
closes) and clicking the Okbutton. Controller data is read-in when the connection is suc-
cessfully established (Online mode).
Offline evaluation only (e.g. of recorded data) is possible if the connection remains discon-
nected or is disconnected again by clicking the Disconnectbutton (Offline mode).
Fig. 37 : Data link to unit
Data recording can be started after successfully establishing the connection!
Chapter 4
40 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.2 Startdatarecording
4.2.1 Startrecordingof measureddatawithouttrigger
Selected measured data can be read-out of the controller. It can be saved and represen-
ted graphically.
Note: The windowbelowonly appears when it is activated (as required).
Click the Nobutton in the windowbelowif no trigger has been defined or no trigger is to
be selected.
Fig. 38 : Prompt for measured data recording
This windowis used to select measured data.
Fig. 39 : Select sensors for data recording
DiaSys in use with controllers
Chapter 4
Page 41
E 531 920 / 02 E -- 05.2002 --
Designation Description
Available sensors Available sensors for the selected unit
Group of sensors A stored group can be selected here
Selected for data
recording
List of selected sensors
Select all sensors
Selects marked sensors in Available sensors. Individual sen-
sors can also be selected by double-clicking.
Drag the mouse over the desired sensors to mark several
sensors or hold down the Shift key and click several sensors.
Deselects the marked sensors in data recording. Individual
sensors can also be deselected by double-clicking.
Drag the mouse over the desired sensors to mark several
sensors or hold down the Shift key and click several sensors.
Deselects all sensors
The sampling time must be entered after selecting the sensors for representation.
After setting the sampling time, select the sensors for the sensor list and then select the
sensors for the y(t)-curve in the same way.
Recording starts on clicking the Okbutton!
Note: The Available functionsdialog box is minimized prior to graphic data repre-
sentation. To stop data recording, for example, the windowmust be reset to its
original size.
Refer to:
Chap. 4.3 Stop recording
Chap. 4.4 Evaluate recorded data
Chap. 4.2.2 Select an active trigger
Chap. 4.2.3 Properties of recording
Chap. 4.4.1 Offline and online y(t)-graphic
Chapter 4
42 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.2.2 Selectanactivetrigger
Description
Data recording started by a trigger condition is also possible. A trigger can comprise one
or more start/end condition logic operations. Data recording starts/ends when the trigger
condition has been fulfilled.
Triggers can only be defined (created) via the menu-guided user interface.
Triggers are selected in the windowbelow:
Fig. 40 : Select an active trigger
4.2.3 Properties of recording
Description
Use the property windowpage to viewand edit general information about the recording
file (label, user and note).
Fig. 41 : Properties of recording
DiaSys in use with controllers
Chapter 4
Page 43
E 531 920 / 02 E -- 05.2002 --
4.3 Stoprecording
Description
Stops the data recorder.
Click the Yesbutton to allowrecorded data to be saved under a randomfile name.
Fig. 42 : Save modifications prompt
Fig. 43 : Save as
Chapter 4
44 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.4 Evaluaterecordeddata
Description
Opens stored data for offline processing.
Fig. 44 : Open recorded data file
This dialog allows sensors to be selected.
Fig. 45 : Select sensors for y(t)-curve
DiaSys in use with controllers
Chapter 4
Page 45
E 531 920 / 02 E -- 05.2002 --
Designation Description
Available sensors Available sensors for the selected unit
Saved graphics or lists A stored group can be selected here
Selected for display List of selected sensors
Select all sensors
Selects marked sensors in Available sensors. Individual sen-
sors can also be selected by double-clicking.
Drag the mouse over the desired sensors to mark several
sensors or hold down the Shift key and click several sensors.
Deselects the marked sensors in Selected for display. Indivi-
dual sensors can also be deselected by double-clicking.
Drag the mouse over the desired sensors to mark several
sensors or hold down the Shift key and click several sensors.
Deselects all sensors
A period of time can also be defined (Period of time...button).
Data is represented graphically on clicking the Okbutton.
Refer to:
Chap. 4.2 Start data recording
Chap. 4.3 Stop recording
Chap. 4.4.1 Offline and online y(t) graphic
Chapter 4
46 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.4.1 Offlineandonliney(t) graphic
Description
This windowshows the measured values over a period of time.
Unit
Measuring
point list
Reference
to measuring
point list
Fig. 46 : Measured values over a period of time
Measuringpointlist

A B C D E
Fig. 47 : Meaning of the individual items
DiaSys in use with controllers
Chapter 4
Page 47
E 531 920 / 02 E -- 05.2002 --
A All relevant functions take effect on the measuring points which are marked.
Colour coding corresponds to the curve in the diagram.
B Reference to axis
C Device number
D Measuring point number
E Measuring point designation
Note: The printing function is called up by actuating key combination Ctrl-P.
4.4.2 Context-sensitivemenus for offlineandonliney(t) graphic
Four context-sensitive menus can be opened in the fields shown below
(move the cursor to the appropriate field with the mouse and click the right mouse key to
open these popUp menus).
Y-axis
inscription
X-axis
inscription
Displayfield Measuringpoint list
Fig. 48 : PopUp menus for offline and online Y(t) graphic
Chapter 4
48 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.5 Modifysingle-parameter
Note: Not available for R082 governor!
Description
A windowappears at first allowing selection of single parameters.
Fig. 49 : Select single-parameters
The selected parameters are then displayed in a window. The properties windowis
opened by pressing key combination Ctrl+Alt+P.
Refer to:
Chap. 4.6 Modify 2D-parameter
Chap. 4.7 Modify 3D-parameter
DiaSys in use with controllers
Chapter 4
Page 49
E 531 920 / 02 E -- 05.2002 --
4.6 Modify2D-parameter
Description
A windowappears at first allowing selection of a characteristic curve (2D-parameter).
Fig. 50 : Select 2D-parameter
The selected characteristic curves are then displayed in a window.
Chapter 4
50 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.7 Modify3D-parameter
Description
A windowappears at first allowing selection of a characteristic map (3D-parameter).
Fig. 51 : Select 3D-parameter
The selected characteristic map is then displayed in a window.
DiaSys in use with controllers
Chapter 4
Page 51
E 531 920 / 02 E -- 05.2002 --
4.8 Injector code
Note: Applies to MDEC-ECU C2 controllers only!
Description
Input of injector codes.
Fig. 52 : Input of injector codes
If the injector codes have been modified and the Transmitbutton is clicked, a windowof
the following type appears:
Fig. 53 : Compare PC-parameter values and Active-parameter values
If modifications are to be made, the data can be transmitted to the controller by clicking
the Sendbutton once more.
Chapter 4
52 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.9 Transmitmodifieddatato controller
Description
The following type of windowappears when parameters have been modified:
Fig. 54 : Compare PC-parameter values and Active-parameter values
Modified data is transmitted to the controller on clicking the Sendbutton.
Return to the higher-level windowby clicking the Cancelbutton.
Designation Description
ParNr Parameter number
Parameter Parameter designation
Type Type of modified parameter (dimension, axis with index)
PC-value Newvalue to be transmitted
Active-value Old value to be overwritten
Unit Unit of measurement for the relevant parameter
DiaSys in use with controllers
Chapter 4
Page 53
E 531 920 / 02 E -- 05.2002 --
A prompt appears in the case of 2D- and 3D-parameters to make sure:
Fig. 55 : Send data prompt
Note: The following windowappears if all parameters are identical:
Please click the OKbutton.
Fig. 56 : Information Identical parameters
Chapter 4
54 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.10 Transmitto controller
Note: Applies to MDEC-ECU C1, MDEC-ECU C2 and ECU-183 controllers only!
Description
Engine data sets (functional software and engine parameter sets) can be transmitted to
the controller. They must be available in the local database. Two functions are provided:
1.
Transmit set of engine parameters
2.
Delete controller and transmit anew
(not available for the MDEC-ECU C1)
Always use the first function.
Note: Exception:
When the controller hardware has been replaced and the controller must be
completely deleted and reloaded. The second function shall only be used in this
case.
Fig. 57 : Transmit to controller
Refer to:
Chap. 4.10.1 Transmit set of engine parameters (only possible online)
Chap. 4.10.2 Delete controller and transmit anew(only possible offline)
DiaSys in use with controllers
Chapter 4
Page 55
E 531 920 / 02 E -- 05.2002 --
4.10.1 Transmitsetof engineparameters
Note: Applies to MDEC-ECU C1, MDEC-ECU C2 and ECU-183 controllers only!
Description
This is the usual method for transmitting engine parameter sets fromthe local database to
the controller.
A connection must have been established to the controller (Online mode).
Furthermore, the engine number fromthe units assembly description and controller must
also be available in the local database. The parameters in the controller are deleted and
written anew. DiaSys decides whether it is necessary to transmit newFSWto the control-
ler. On detecting an older engine parameter set in the local database than in the control-
ler, the user is explicitly requested to confirm:
Fig. 58 : Confirmation prompt
If the entries in the local database are less recent, transmission of the engine parameter
set commences immediately.
Refer to:
Chap. 4.10.2 Delete controller and transmit anew
Chapter 4
56 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.10.2 Deletecontroller andtransmitanew
Note: Applies to MDEC-ECU C2 and ECU-183 controllers only!
CAUTION
Applies to MDEC-ECUC2only:
Load profile data of the controller is deleted during this activity
and not automatically transmitted to the controller.
Only backup the maintenance indicator with the engine at a
standstill.
Description
All data in the controller is deleted. The engine parameter set and functional software are
subsequently reloaded.
The appropriate data must be available in the local database to do this. Particularly the
engine number fromthe units assembly description must be available in the local data-
base. In this case, the link to the controller must be disconnected (Offline mode) to allow
this function to be activated (see chap. 4.1). However, the connecting cable between com-
puter and controller must be connected as data is exchanged.
Fig. 59 : Transmit FSW and MPS?prompt
Click the OKbutton to transmit FSWand MPS data to the controller.
Fig. 60 : Switch off controllerinformation window
DiaSys in use with controllers
Chapter 4
Page 57
E 531 920 / 02 E -- 05.2002 --
Fig. 61 : Switch on controllerinformation window
As indicated in the windows above, the following steps must be taken in the given order:
Switch off the controller.
Confirmwith OK.
Switch the controller back on within 30 seconds.
Transmission commences when all requirements are fulfilled (indicated by the following
animated graphic):
Fig. 62 : Animated graphic Data transmission
Note: Please be patient. The length of the transmission is not known in advance and
may take up to 25 minutes.
Fig. 63 : Toggle controller off and oninformation window
Note: The controller must be subjected to a Power-On-Resetin order to complete
transfer of the freshly loaded data to the controller. The controller must be
switched off and back on again to do this. This must be confirmed by clicking
OK as shown in fig. 63.
The controller data which has just been transmitted is read-in at the end after which the
systemreturns to its normal state.
Chapter 4
58 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
1D: 3.20
Fig. 64 : Receiving data fromcontrollerinformation window
Refer to:
Chap. 4.10.1 Transmit set of engine parameters
4.11 Logfiles
Description
Provides an overviewof all available logfiles
Fig. 65 : Logfiles
DiaSys in use with controllers
Chapter 4
Page 59
E 531 920 / 02 E -- 05.2002 --
4.11.1 Error logfile
Note: Not available for ECU-2, CDS/C and R082 controllers!
Description
This opens a windowdisplaying error messages (error record). Puts the error message in
chronological order.
Fig. 66 : Error record
A popUp menu can be opened by clicking the right mouse key (click in the grey area at
the top):
Fig. 67 : Chronological orderpopUp menu
Chapter 4
60 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.11.2 Modificationlogfile
Note: This function is not available for R082 governors!
Description
Parameter modifications are automatically recorded by DiaSys. This menu option opens
the windowdisplaying parameter modifications.
Fig. 68 : Logfile of user activities
Parameter modifications carried out with the unit assembly description open are recorded.
DiaSys in use with controllers
Chapter 4
Page 61
E 531 920 / 02 E -- 05.2002 --
The following procedures are recorded:
Selection of a unit
Parameter modifications
Import
Opening of a unit assembly description
Displayed in the windoware:
Date/time
Type of activity (extended as necessary)
Description:
Type Description
Use Opened by user
Dev Device selected
Cha Parameter change
Note: This information is also deleted when the unit assembly description is deleted.
Chapter 4
62 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.11.3 Parameter modifiedby...
Note: Not available for MDEC-ECU C1, R082 and ECU-2 and ECU-183 controllers!
Description
Parameter modifications are recorded and saved in the controller. This function opens a
windowin which the logfile is displayed.
The logfile records those users who made modifications to the parameters. The modifica-
tion date is also stored.
Fig. 69 : User logfile
Note: This information is stored in the controller.
DiaSys in use with controllers
Chapter 4
Page 63
E 531 920 / 02 E -- 05.2002 --
4.11.4 Units ID
Note: Applies to all controllers with the exception of R082!
Description
This displays information about the controller, such as the number of error messages.
Structure and contents depend on the controller concerned.
Fig. 70 : IDof unit
Chapter 4
64 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.12 Extras
Description
These display information about the active hardware key and the engine number (the
extras windowvaries slightly depending on the controller).
Fig. 71 : Extras
Note: Available for the following types of controller:
Function Availablefor:
Hardware key info All controllers
Showengine number MDEC-ECU C2, ECU-183 controllers only
Export into Excel-file All controllers except R082
Import Excel-file All controllers except R082, MDEC-ECU C2
DiaSys in use with controllers
Chapter 4
Page 65
E 531 920 / 02 E -- 05.2002 --
4.12.1 Exportinto Excel-file
Note: This function is not available for R082 governors.
Description
The current
Parameter values
Error messages
Maintenance forecasts
Modification logfiles
can be exported to any desired directory.
Fig. 72 : Export to Excel
Refer to:
Chap. 4.12.2 Import Excel-file
Chapter 4
66 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.12.2 ImportExcel-file
Note: This function is not available for R082 and MDEC-ECU C2 controllers.
Description
Imports parameter values froman Excel file and subsequently transmits the data to the
controller.
Fig. 73 : Import fromExcel
Refer to:
Chap. 4.12.1 Export into Excel-file
DiaSys in use with controllers
Chapter 4
Page 67
E 531 920 / 02 E -- 05.2002 --
4.12.3 HardwareKeyInfo
Description
This windowdisplays information about the hardware key.
Fig. 74 : Hardware key info
Designation Description
Registered user Registered for
Serial number Serial number of the hardware key
Validity period Indicates howlong the hardware key is valid
Qualification level Indicates which qualification level is enabled in the hardware key
Qualified for Indicates the units for which authorization is given. The registered
user can only work with these types of unit.
Chapter 4
68 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.12.4 Showenginenumber
Note: Applies to MDEC-ECU C2 and ECU-183 controllers only!
Description
The engine number is stored internally. This number can be displayed by clicking Show
engine number.
Fig. 75 : Showengine number
4.13 To menus
Description
It is possible to change to the menu-oriented user interface depending on the hardware
key, the controller and the selected user group.
Additional functions are available in the menu-oriented user interface which is intended for
the expert user. It is possible to return via the menu
Extras -- activity-oriented operation.
Note: No connection can be established to the central database in the menu-oriented
user interface.
DiaSys in use with controllers
Chapter 4
Page 69
E 531 920 / 02 E -- 05.2002 --
4.14 Maintenanceforecast
Note: Maintenance indicator functions are only available for MDEC-ECU C1 and C2
(certain functional parts only) and ECS-Uni controllers!
Description
Displays an overviewof all functions pertaining to the maintenance indicator.
Fig. 76 : Maintenance forecast
Refer to:
Chap. 4.14.1 Confirmscheduled maintenance
Chap. 4.14.5 Confirmload depending maintenance
Chap. 4.14.2 Scheduled maintenance dates
Chap. 4.14.4 Load depending maintenance dates
Chap. 4.14.6 Load profile
Chap. 4.14.7 Endurance matrix
Chap. 4.14.14 Save data for evaluation
Chap. 4.14.13 Save all (for restoration)
Chap. 4.14.12 Restore
Chap. 4.14.8 TBO-parameter
Chap. 4.14.3 Shift maintenance schedule
Chap. 4.14.9 Tolerance of maintenance dates
Chap. 4.14.10 Modify K-constant
Chap. 4.14.11 NewTi Matrix
Chapter 4
70 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.14.1 Confirmscheduledmaintenance
Note: Available for ECS-Uni only!
Description
Scheduled maintenance work is acknowledged here. Maintenance interval and due date
are displayed in the window.
Mark the relevant maintenance interval and click Confirm.
Fig. 77 : Scheduled maintenance
Refer to:
Chap. 4.14.2 Scheduled maintenance dates
DiaSys in use with controllers
Chapter 4
Page 71
E 531 920 / 02 E -- 05.2002 --
4.14.2 Scheduledmaintenancedates
Note: Available for ECS-Uni only!
Description
The record of scheduled maintenance dates is displayed here.
The dates are shown in chronological order. The maintenance date is indicated if the
execution of maintenance work has been confirmed.
Fig. 78 : Scheduled maintenance dates
Refer to:
Chap. 4.14.1 Confirmscheduled maintenance
Chapter 4
72 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.14.3 Shiftmaintenanceschedule
Note: Available for ECS-Uni only!
Description
The defined maintenance schedule can be shifted by a certain period of time here.
The schedule can be shifted by a maximumof 240 months. The next maintenance date
before shifting is shown at Upcoming maintenance date. The newdate after shifting is
indicated at Rescheduled date.
Enter the number of months by which the maintenance schedule is to be shifted and click
the Okbutton.
Fig. 79 : Shift scheduled maintenance dates
Refer to:
Chap. 4.14.1 Confirmscheduled maintenance
DiaSys in use with controllers
Chapter 4
Page 73
E 531 920 / 02 E -- 05.2002 --
4.14.4 Loaddependingmaintenancedates
Note: Available for ECS-Uni only!
The load depending maintenance record is displayed here.
The record shows after howmany operating hours maintenance was acknowledged
(executed). Deviations fromthe due date are indicated under Deviation.
Fig. 80 : Load depending maintenance
Refer to:
Chap. 4.14.5 Confirmload depending maintenance
Chapter 4
74 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.14.5 Confirmloaddependingmaintenance
Note: Available for ECS-Uni only!
Description
This windowallows load-depending maintenance to be acknowledged. Mark the mainte-
nance work for acknowledgement and click Confirm. The right-hand column indicates
the time when maintenance is due in hours (h). It also indicates whether maintenance is
due or not. The current number of operating hours is displayed at Operating hours.
Fig. 81 : Load depending maintenance
Refer to:
Chap. 4.14.4 Load depending maintenance dates
DiaSys in use with controllers
Chapter 4
Page 75
E 531 920 / 02 E -- 05.2002 --
4.14.6 Loadprofile
Description
Indicates the load profile of the connected unit.
The load profile curve can be rotated through all axes using the mouse. On two-key mou-
ses, hold down both mouse keys and rotate the curve by moving the mouse. On three-key
mouses, this is possible by holding down the middle mouse key.
Fig. 82 : Load profile
Note: Data must be saved to disk using the Save data for evaluationfunction as
described in chapter 4.14.14 to use data for purposes of evaluation.
Chapter 4
76 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
A context-sensitive menu appears on clicking the right mouse key in the grey area
between data and display window.
Fig. 83 : Context-sensitive load profile menu
The next and previous levels can be displayed with Alt >and Alt <.
DiaSys in use with controllers
Chapter 4
Page 77
E 531 920 / 02 E -- 05.2002 --
4.14.7 Endurancematrix
Description
This displays the endurance matrix (Ti matrix) of the engine. The potential service life of
the engine can be estimated fromthis information. The endurance matrix of the engine is
constant and defined by MTU.
The endurance curve can be turned through all axes with the mouse. On two-key mouses,
hold down both mouse keys and rotate the curve by moving the mouse. On three-key
mouses, this is possible by holding down the middle mouse key.
A context-sensitive menu appears on clicking the right mouse key in the grey area
between data and display window.
Fig. 84 : Context-sensitive Ti endurance matrix menu
Chapter 4
78 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.14.8 TBO-parameter
Note: Available for ECS-Uni only!
Description
This windowallows TBO parameters to be displayed and entered. The values on the left
can be edited. The values on the right are projected/current values.
Data which has been modified can be saved by clicking the Closebutton or discarded by
clicking Cancel.
Fig. 85 : TBO-parameter
DiaSys in use with controllers
Chapter 4
Page 79
E 531 920 / 02 E -- 05.2002 --
Designation Description
TBO Expected service life of the engine
Operating hours Engine operating hours
Offset Period of time by which maintenance services W5 and W6 have been
carried out prematurely.
This period of time is subtracted fromthe calculated service life of the
engine.
K-constant Constant defined by MTU
Start-TBO Constant defined by MTU
Max. TBO Constant defined by MTU
TBO Offset Constant defined by MTU
Speed (0) Engine idling speed
FRP (0) Fuel rack position when the engine is idling
Power (0) Engine idling power
Speed (max.) Maximumengine speed
FRP (max.) Fuel rack position under full engine load conditions
Power (max.) Maximumengine power
FRP factor Scaling factor
FRP offset Scaling factor offset
Refer to:
Chap. 4.14.10 Modify K-constant
Chapter 4
80 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.14.9 Toleranceof maintenancedates
Note: Available for ECS-Uni only!
Description
This windowallows newtolerances for acknowledgement of load-depending maintenance
dates to be acknowledged.
The tolerance for each type of maintenance work for which acknowledgement is possible
can be defined.
The tolerances are stated as a percentage of the due value.
Fig. 86 : Tolerance of maintenance dates
DiaSys in use with controllers
Chapter 4
Page 81
E 531 920 / 02 E -- 05.2002 --
4.14.10 ModifyK-constant
Note: Available for ECS-Uni only!
Description
This windowallows the K-constant to be modified.
The K-constant is a value defined by MTU.
Fig. 87 : Modify K-constant
Note: Use this function with the engine at a standstill. Save the load profile before-
hand (see chap. 4.14.13 Save all).
Chapter 4
82 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
4.14.11 NewTi Matrix
Note: Available for ECS-Uni only!
Description
A newendurance matrix (TI-matrix) can be read in froma data carrier.
Click Browse...to open a windowallowing selection of an appropriate file. The file must
have the extension mit. The TI-matrix is transmitted directly to the unit.
Fig. 88 : Replace TI-matrix
Note: Use this function with the engine at a standstill. Save the load profile before-
hand (see chap. 4.14.13 Save all).
4.14.12 Restore
Description
Restores an earlier backup of the maintenance indicator fromdisk. The disk used for this
must have been created using the Save all (for restoration)function as described in
chapter 4.14.13.
This is necessary e.g. after replacing hardware.
CAUTION
The maintenance indicator shall only be restored with the engine
at a standstill.
Refer to:
Chap. 4.14.13 Save all
DiaSys in use with controllers
Chapter 4
Page 83
E 531 920 / 02 E -- 05.2002 --
4.14.13 Saveall
Description
This menu option backs the maintenance indicator up to disk (see chap. 4.14.12). Have
an empty, formatted disk ready in this case.
This datacannot beusedfor evaluation. The function described in chap. 4.14.14 is
necessary to do this.
A progress bar is displayed in the status line. Followthe instructions on the screen.
CAUTION
The maintenance indicator shall only be saved with the engine at
a standstill.
Refer to:
Chap. 4.14.12 Restore
4.14.14 Savedatafor evaluation
Description
Saves the data (load profile, etc.) in Excel format for evaluation at a later date.
Chapter 4
84 Page
DiaSys in use with controllers
E 531 920 / 02 E -- 05.2002 --
(This page intentionally blank)
Programming MEM modules
Chapter 5
Page 85
E 531 920 / 02 E -- 05.2002 --
Chapter 5
ProgrammingMEMmodules
Chapter 5
86 Page
Programming MEM modules
E 531 920 / 02 E -- 05.2002 --
5 ProgrammingMEMmodules
Description
MEM memory modules can be programmed. This feature requires a Backup Data Module
and a suitable connecting cable (see fig. 89).
Display connector
Blue shrink-fit hose
Fig. 89 : Backup Data Module BDM with connecting cable for dialog PC
Connector pinassignmentof thecable(MTUitemno. 5355307534)
The connector pin assignment of the cable is as follows:
9polesub D
FB-1connector
Potential 9-polesub-D
BDM Display
Potential
7 81 61 CAN-H
2 82 62 CAN-L
3 83 63 CAN-GND
Note: 60 must be measured between pins 81 and 82 (bus terminator).
Programming MEM modules
Chapter 5
Page 87
E 531 920 / 02 E -- 05.2002 --
Pre-requisites for use
The following pre-requisites must be fulfilled to use this feature:
The dialog PC must be equipped with a CAN board.
A dongle (hardware key) allowing CAN customer service access is necessary.
A Backup Data Module BDM with device software (GSW) version V3.02 or
higher must be available.
Check that option 0 (station type) is assigned to PPS using the
E2_PROGR.OUT program(see also fig. 90).
Four directory levels must be available belowthe initial path (this is stated in
the BDM settings). Data must be in the fourth directory.
The Programmingbutton is otherwise not enabled.
Designation and contents in the higher levels are irrelevant.
The path for the programming source (e.g. CD, disk) can be selected with the
MCS-5/RCS-5, options, BDM settings buttons. Directory nesting depth must,
however, remain unchanged (see above).
Notes:
Different directories are defined for the basic software and the PUdata.
MEM-5 modules which have already been programmed are written over without
warning.
BDM and dialog software must be set to the same baud rate to programthe
MEM-5 modules.
Chapter 5
88 Page
Programming MEM modules
E 531 920 / 02 E -- 05.2002 --
Fig. 90 shows an example with correct settings:
*
Fig. 90 : Example showing correct settings
Note: The BDM download function (data transmission fromBDM to plant) is no longer
guaranteed if the transmission rate (option 3 in fig. 90, marked with a *) is not
set to 125 kBaud.
Programming MEM modules
Chapter 5
Page 89
E 531 920 / 02 E -- 05.2002 --
Proceedas follows for programming:
Select Product supportin the Type of activity (users) box.
Fig. 91 : Type of activity
See also:
Chap. 3.2 Type of activity
Select type of unit MCS-5/RCS-5.
Fig. 92 : Select type of unit
Chapter 5
90 Page
Programming MEM modules
E 531 920 / 02 E -- 05.2002 --
5.1 Preparefor BDMprogramming
Fig. 93 : Prepare for BDMprogramming
Start preparation by clicking the Prepare for BDMprogramming...button. The window
which then opens requires confirmation of whether the directory structure is to be created
for project configuration data (PU) or basic software.
Fig. 94 : Option windowfor directory structure
Programming MEM modules
Chapter 5
Page 91
E 531 920 / 02 E -- 05.2002 --
The next step is to enter the order number and index number of the order:
Fig. 95 : Entering the order
Then select the available data:
Fig. 96 : Selecting data
Chapter 5
92 Page
Programming MEM modules
E 531 920 / 02 E -- 05.2002 --
Clicking the Selectbutton opens a windowin which the appropriate file can be chosen.
Fig. 97 : Search and select file
Once all the necessary information has been entered, preparation for BDM programming
is completed by clicking the Executebutton.
Fig. 98 : Completing preparation for BDM programming
Programming MEM modules
Chapter 5
Page 93
E 531 920 / 02 E -- 05.2002 --
5.2 Programmingmode
Fig. 99 : Programming mode
Select programming mode by clicking the Programming mode...button.
Fig. 100 : Indicating readiness for operation
Click the OKbutton as soon as the pre-requisites for a safe systemstate have been ful-
filled (BDM is connected to the dialog PC, power supplies are connected and stable).
Chapter 5
94 Page
Programming MEM modules
E 531 920 / 02 E -- 05.2002 --
Choose PUData or Basic software in the Type of datafield as shown in figs. 101 and
102.
Fig. 101 : PUData option
Fig. 102 : Basic software option
The path (directory levels) must match the examples shown above, the Programbutton
is otherwise not enabled.
Select the CAN interface used by the PC in the PCMCIA channelfield.
Programming MEM modules
Chapter 5
Page 95
E 531 920 / 02 E -- 05.2002 --
A transmission rate of 400 kBaud can also be selected in the Baudratefield. However,
this means that the transmission rate in the BDM must also be set to 400 kBaud using the
E2_PROGR.OUT program. The BDM download feature is no longer available in this case.
This high transmission rate is only suitable for programming MEM modules.
Always set the transmission rate back to 125 kBaud after completing downloading
for this reason.
Clicking the Programbutton starts the programming sequence.
The warning described earlier (see fig. 100) must be re-confirmed. The dialog system
establishes an online link to the BDM (green field, bottomright).
A programming progress bar as shown in fig. 103 appears when everything is correctly
set up.
Note: Of the max. 32 blocks to be programmed, only the assigned blocks are trans-
mitted to the BDM. Only a total of 8 blocks are shown in the example in fig. 103,
Fig. 103 : Programming sequence
Chapter 5
96 Page
Programming MEM modules
E 531 920 / 02 E -- 05.2002 --
A monitoring windowappears on completion of programming which shows a record of the
programming sequence.
Fig. 104 : On completion of programming (example shows incorrect programming!)
The programming sequence is thus terminated.
Note: Some irrelevant fault messages are received on programming PUdata on
older versions (DiaSys, device software).