E531920_02E

Service Publication

DiaSys 2.xxDialog software forMTU systems

E 531 920 / 02 E

DaimlerChrysler Powersystems Off-Highway

Documentation Part 2

Printed in GermanyE 2002 Copyright MTU Friedrichshafen GmbHDiese Veröffentlichung einschließlich aller seiner Teile ist urheberrechtlich geschützt. Jede Verwertung oder Nutzung bedarf der vorherigenschriftlichen Zustimmung der MTU Friedrichshafen GmbH. Das gilt insbesondere für Vervielfältigung, Verbreitung, Bearbeitung,Übersetzung, Mikroverfilmungen und die Einspeicherung und / oder Verarbeitung in elektronischen Systemen, einschließlich Datenbankenund Online-Diensten.Das Handbuch ist zur Vermeidung von Störungen oder Schäden beim Betrieb zu beachten und daher vom Betreiber dem jeweiligenWartungs- und Bedienungspersonal zur Verfügung zu stellen.Änderungen bleiben vorbehalten.

Printed in GermanyE 2002 Copyright MTU Friedrichshafen GmbHThis Publication is protected by copyright and may not be used in any way whether in whole or in part without the prior written permission ofMTU Friedrichshafen GmbH. This restriction also applies to copyright, distribution, translation, microfilming and storage or processing onelectronic 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.

Imprimé en AllemagneE 2002 Copyright MTU Friedrichshafen GmbHTout droit réservé pour cet ouvrage dans son intégralité. Toute utilisation ou exploitation requiert au préalable l’accord écrit de MTUFriedrichshafen GmbH. Ceci s’applique notamment à la reproduction, la diffusion, la modification, la traduction, l’archivage sur microfiches,la mémorisation et / ou le traitement sur des systèmes électroniques, y compris les bases de données et les services en ligne.Le manuel devra être observé en vue d’éviter des incidents ou des endommagements pendant le service. Aussi recommandons-nous àl’exploitant de le mettre à la disposition du personnel chargé de l’entretien et de la conduite.Modifications réservées.

Impreso en AlemaniaE 2002 Copyright MTU Friedrichshafen GmbHEsta publicación se encuentra protegida, en toda su extensión, por los derechos de autor. Cualquier utilización de la misma, así como sureproducción, difusión, transformación, traducción, microfilmación, grabación y/o procesamiento en sistemas electrónicos, entre los que seincluyen bancos de datos y servicios en línea, precisa de la autorización previa de MTU Friedrichshafen GmbH.El manual debe tenerse presente para evitar fallos o daños durante el servicio, y, por dicho motivo, el usario debe ponerlo a disposición delpersonal de mantenimiento y de servicio.Nos reservamos el derecho de introducir modificaciones.

Stampato in GermaniaE 2002 Copyright MTU Friedrichshafen GmbHQuesta pubblicazione è protetta dal diritto d’autore in tutte le sue parti. Ciascun impiego od utilizzo, con particolare riguardo allariproduzione, alla diffusione, alla modifica, alla traduzione, all’archiviazione in microfilm ed alla memorizzazione od all’elaborazione insistemi elettronici, comprese banche dati e servizi on line, deve essere espressamente autorizzato per iscritto dalla MTU FriedrichshafenGmbH.II manuale va consultato per evitare anomalie o guasti durante il servizio, per cui va messo a disposizione dall’ utente al personale addettoalla manutenzione e alla condotta.Con riserva di modifiche.

¯ ISO 9001 certificationQuality assurance in design/development, production, installation and service

MTU assuring you:

¯ CE conformity-- Guideline 73/23/EEC – Low voltage guideline –

dated February 19, 1973 with amendment dated July 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 influenced if the product is installed incorrectly, an assembly or system is misusedand/or genuine MTU components are not used.

Guide Page I

E 531 920 / 02 E -- 05.2002 --

Table of contents

Table of contents I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Abbreviations IV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General information about documentation V. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 Safety requirements 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 General information about the DiaSys program 6. . . . . . . . . . . . . . . . . . . .

2.1 Use 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2 Terms and definitions 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Program info 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 New units 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 from central database 21. . . . . . . . . . . . . . . . . . . . . . . .

3.4.5 Import from disk, export to disk 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.5.1 Export data 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.5.2 Import data 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.6 Edit engine data from local database 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.7 Options 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.7.1 Select language 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4.7.2 Display logfile “Log.txt” 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GuidePage II

E 531 920 / 02 E-- 05.2002 --

Table of contents (cont.)

4 DiaSys in use with controllers 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 Show engine number 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.13 To menus 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Guide Page III

E 531 920 / 02 E -- 05.2002 --

Table of contents (cont.)

4.14 Maintenance forecast 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.14.1 Confirm scheduled 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 Confirm load 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 New Ti Matrix 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.14.12 Restore 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.14.13 Save all 83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.14.14 Save data for evaluation 83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 Programming MEM modules 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Prepare for “BDM” programming 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2 Programming mode 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GuidePage IV

E 531 920 / 02 E-- 05.2002 --

Abbreviations

Note: This list does not contain common English abbreviations.

°C Degrees Celsius

% Percent

CE Conformité Européenne, European conformity (European Union mark ofapproval)

DIN Deutsches Institut für Normung, German National Standards Institute;formerly: Deutsche Industrienorm, German Industrial Standard

ECS Engine Control System (engine management system and controller)

EMC Electromagnetic Compatibility

EN European Norm (CEN standard)

f Frequency

g Gravity acceleration constant (9.81 m/s2)

Hz Hertz

IEC International Electrotechnical Commission

IP International Protection, index of protection in accordance withDIN 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 information about documentation

Documentation structure

DocumentationPart

Title/contents Target groupwith the lowest level of qualification

1 Structure and function Operating personnel

2 Operation Operating personnel

3 Maintenance and repair(Operating personnel)

Operating personnel charged withmaintenance

4 Maintenance and repair(Specialist personnel)

Specialist personnel charged withmaintenance

5 Illustrated parts catalog Operating personnel charged withmaintenance

6 Plant-specificconfiguration

Specialist personnel charged withmaintenance

7 Installation andinitial start-up

Start-up personnel

Note: Not all documentation parts are written for every product!

Required knowledge

To understand each part of the documentation, we recommend reading the precedingparts, if applicable.

Reference numbers and reference lines

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 figurenumber and, separated by an oblique, the reference number of the detail are written inbrackets. 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 thefigure.An arrow at the end of the reference line indicates that the detail cannot beseen in the figure.

GuidePage 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 requirementsChapter 1

Page 1

E 531 920 / 02 E -- 05.2002 --

Chapter 1

Safety requirements

Chapter 1

2PageSafety requirements

E 531 920 / 02 E-- 05.2002 --

(This page intentionally blank)

Safety requirementsChapter 1

Page 3

E 531 920 / 02 E -- 05.2002 --

1 Safety requirements

I M P O R T A N TThese safety requirements shall be read and observed by all

personnel involved in operation, care, maintenance or repair of theproducts 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 safety notes in the text

Where necessary, this manual includes highlighted safety notes marked with a signalword. These safety notes shall be observed to avoid injury or damage.

This type of note indicates a danger which may lead to injury ordeath.

DANGER

This type of note indicates a danger which may lead to damageor destruction of the product described or another part of thesystem.

CAUTION

Intended use and user qualifications

All devices and system components may only be put to their intended use.

Operation, maintenance and repair shall only be performed by qualified and authorizedpersonnel.

Chapter 1

4PageSafety requirements

E 531 920 / 02 E-- 05.2002 --

Safety requirements for starting up

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 system is taken into operation¯ All maintenance and repair work must have been completed.¯ Any loose parts must have been removed from rotating machine components.¯ Nobody is allowed within the range of moving machine components.

Immediately after taking the unit or system into operation, the control and display ele-ments as well as the monitoring, signalling and alarm systems must be suitably tested forproper operation.

Operational safety requirements

The emergency procedures must be practiced on a regular basis.

The operator must be familiar with the control and display elements.

The operator must know the 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 supervisedwith respect to current operating states, adherence to limit values as well as warnings andalarm messages.

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 betaken as required, e.g. emergency engine stopping.

General information DiaSysChapter 2

Page 5

E 531 920 / 02 E -- 05.2002 --

Chapter 2

General information about theDiaSys program

Chapter 2

6PageGeneral information DiaSys

E 531 920 / 02 E-- 05.2002 --

2 General information about the DiaSys program

2.1 Use

The DiaSys program is required to communicate with various MTU controllers, RCS-5Remote Control Systems and MCS-5 Monitoring and Control Systems.

The main features of the DiaSys program are:

¯ Data exchange with the central database

¯ Controller parameter setting

¯ Data recording

Note: This manual primarily contains information pertaining to the use of the DiaSysprogram in conjunction with controllers. Functions are described which requirea level 1B hardware key (service/distributor). Menu functions are not documen-ted in this manual.

2.2 Terms and definitions

The following terms are used in this manual:

Term Meaning

Online mode The controller is connected to the serial interface and ableto receive commands from DiaSys.

Offline mode The controller is not connected to the serial interface.Previously saved data can be processed (e.g. evaluatingmeasured 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 bythe engine number in the central database).

General information DiaSysChapter 2

Page 7

E 531 920 / 02 E -- 05.2002 --

2.3 Program info

Description

This window displays program information, version number, copyright, date and time. Thiswindow always appears on starting the program.

Fig. 1 : Program information

A general safety warning appears after clicking the “OK” button to warn operators aboutthe dangers of incorrect operation and programming of the connected devices.

Fig. 2 : Safety warning

The next program window appears on clicking the “OK” button.Clicking the “Cancel” button exits the program.

Chapter 2

8PageGeneral information DiaSys

E 531 920 / 02 E-- 05.2002 --


PreparationChapter 3

Page 9

E 531 920 / 02 E -- 05.2002 --

Chapter 3

Preparation

Chapter 3

10PagePreparation

E 531 920 / 02 E-- 05.2002 --

3 Preparation

3.1 Starting the program

The following steps are always necessary in order to start DiaSys successfully:

Program start-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 Type of activity

Description

Selects the type of activity (user group). The number of users available for selection mayvary depending on the level of the active hardware key. The functions provided by theDiaSys program depend on the type of activity selected.

Fig. 3 : Type of activity


Page 11

E 531 920 / 02 E -- 05.2002 --

3.3 Select type of unit

Description

Selects the type of unit. This window is only active when “No default type of unit” is selec-ted in the Options window.

Fig. 4 : Select type of unit

Clicking the small buttons opens a graphic representation of the device/system con-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 whenthe “ESC” key is pressed on the computer keyboard.

Chapter 3

12PagePreparation

E 531 920 / 02 E-- 05.2002 --

Note: The range of functions available in DiaSys may vary depending on the type ofunit selected.

3.4 Units assembly description

Description

Allows creation of a new units 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 modem ora link to the MTU network (LAN) and subsequently loaded into the controller. Any changesmade to parameters in the controller require the modified data set to be transmitted backto the central database to ensure that the current status of the controller is also availablethere. The “Install transmission line to central database” function is provided to facilitatethe exchange of data.

The “Options” button allows the DiaSys language to be toggled between German orEnglish.

The “Units assembly description” window may offer a somewhat limited range of functionsdepending on the controller connected.


Page 13

E 531 920 / 02 E -- 05.2002 --

Fig. 6 : Units assembly description

Function Available for:

New units assembly description All controllers

Open units assembly description All controllers

Edit unit’s 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

14PagePreparation

E 531 920 / 02 E-- 05.2002 --

3.4.1 New units assembly description

Description

Creating a new units assembly description involves assigning one or more engine num-bers to a specific order number. The DiaSys program automatically creates directories inwhich data are stored.

Fig. 7 : Create a new units assembly description

The window below (fig. 8) which allows an engine number to be entered appears onclicking the “New” button.

Fig. 8 : Enter engine number

Note: Every order number must be linked to at least one engine number.

The “Available functions” window (see chap. 4) is only accessible in this way and via the“Open units assembly description” function.


Page 15

E 531 920 / 02 E -- 05.2002 --

3.4.2 Open units assembly description

Description

Opening a units assembly description involves reusing an existing units assembly descrip-tion.

The “Available functions” window (see chap. 4) is only accessible in this way and via the“New units assembly description” function.

Fig. 9 : Open units assembly description

Chapter 3

16PagePreparation

E 531 920 / 02 E-- 05.2002 --

3.4.3 Delete units assembly description

Description

Displays available order numbers. All data pertaining to the selected order number orselected plant name are deleted with the “Delete” function (engine parameter sets storedin the local database are not deleted).

Fig. 10 : Delete unit’s assembly description

The following prompt appears on clicking the “Delete” button:

Fig. 11 : Confirming “Delete unit’s assembly description”

Note: This deletes an entire order (i.e. the entire plant). Proceed as described belowin order to delete individual engine numbers.


Page 17

E 531 920 / 02 E -- 05.2002 --

The window below appears on clicking the “Edit” button:

Fig. 12 : Window for selecting an individual engine number

A new engine number can be created for an order in this window or an individual enginenumber deleted from the order.

The selected function is carried out on clicking the “OK” button.

Chapter 3

18PagePreparation

E 531 920 / 02 E-- 05.2002 --

3.4.4 Install transmission line to 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 modem or directly via theMTU network (LAN)), engine data sets stored in the local database can be copied back tothe central database. It is also possible to fetch data from the central database. Theengine number identifies the relevant data sets unambiguously.

Note: In contrast to the LAN connection, the user must establish the link to the MTUnetwork via communication software when a modem is used.

Fig. 13 : Transmit parameter set to central database

A differentiation is made between two different types of data set in the local database:

Data set Data set contents

For cintroller(data for the controller)

This data stems from the central database and is intended forthe controller.

Current data(data of the controller)

The current data of the controller is shown here. Any changes atthe controller are recorded. On copying a data set back to thecentral database, the “current data” is always returned and sub-sequently deleted in the local database.


Page 19

E 531 920 / 02 E -- 05.2002 --

Fig. 14 : Load set of parameters from central database

Two data sets may be available for each engine number in the central database:

Data set Data set contents

Modernized data(desired data)

Modernization data is stored here.

Latest nominal data(current data last

copied back)

The “Latest nominal data” is the data read-out of the controller.Only corresponds to the current data set of the controller whencopied back to the central database regularly.

Chapter 3

20PagePreparation

E 531 920 / 02 E-- 05.2002 --

Desired dataCurrent datalast copied

back

Current data(data from the

controller)

Data for thecontroller

MDEC-ECU C2

Engine parameter set (MPS)+

Functional software (FSW)

Central database

Local database

Fig. 15 : Data exchange with the central database

3.4.4.1 Transmit parameter set to 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 “Transmit” field.


Page 21

E 531 920 / 02 E -- 05.2002 --

Click the “Cancel” button to gain direct access to the “Load set of parameters from centraldatabase” window.

Only the current data of the controller can be transmitted to the central database!Data transfer commences on clicking the “Transmit” button.

Note: The communication software must be started beforehand and the connectionestablished to the provider. DiaSys is then started and data exchange startedwith the “Install transmission line to central database” function.

Refer to:Chap. 3.4.4 Install transmission line to central databaseChap. 3.4.4.1 Load set of parameters from central databaseChap. 3.4.5 Import from disk, export to diskChap. 3.4.6 Delete engine data in local database

3.4.4.2 Load set of parameters from central database

Fig. 17 : Load set of parameters from central database

The engine number must be stated to load a parameter set from the central database.Also state whether “modernized data” or the “Latest nominal data” are to be loaded.

Access the next window (fig. 18) by clicking the “Continue” button.

Chapter 3

22PagePreparation

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 from the central database to the local database of the computer onclicking the “Fetch data” button.

The “Fetch data” button is not enabled if the desired data set is unavailable.

Note: The FSW is also transmitted if required.

Refer to:Chap. 3.4.4 Install transmission line to central databaseChap. 3.4.4.1 Transmit parameter set to central databaseChap. 3.4.5 Import from disk, export to diskChap. 3.4.6 Delete engine data in local database


Page 23

E 531 920 / 02 E -- 05.2002 --

3.4.5 Import from disk, export to disk


Description

Engine data sets can be exported to disk if it is not possible to transmit data via modem orLAN. These data sets can be imported to another PC and subsequently transferred to thecentral database via LAN or modem (vice-versa also possible).

Fig. 19 : Option window for exporting or importing data

This window defines whether data is to be imported to the DiaSys program in order tothen 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 “Cancel” button returns to the previous window.

Chapter 3

24PagePreparation

E 531 920 / 02 E-- 05.2002 --

3.4.5.1 Export data

The window below appears on clicking the “Export data” button:

Fig. 20 : Information about data export

If the target directory stated in this window is not empty, the program deletes all files inthis directory when the “Yes” button is clicked in the window below:

Fig. 21 : Warning, data deleted


Page 25

E 531 920 / 02 E -- 05.2002 --

The following window appears 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 isto be written is stated here. A default name is auto-matically entered.

Direction of data transfer Determines whether data is exported for the centraldatabase or exported for the controller.

Type of data compression Determines whether one single large file is createdfor storage on a data medium or whether the file isto span a number of disks. Several small files whichcan be copied to disk are created in this case.

Chapter 3

26PagePreparation

E 531 920 / 02 E-- 05.2002 --

The window below appears on clicking the “Continue” button:

Fig. 23 : Selecting data

It is now necessary to state which data (i.e. the data of which engine number) is to beexported. The data is marked with an “x” in the “Export” column. The selection is reversedby clicking the appropriate box.

Once all the desired engine numbers have been selected, the transmission can be startedby clicking the “Export” button. The window below appears on (successful) completion ofthe transmission:

Fig. 24 : Confirmation of successful export


Page 27

E 531 920 / 02 E -- 05.2002 --

3.4.5.2 Import data

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 random directory on the dialog unit (e.g. C:\TEMP).

The extract program starts automatically as soon as the file is double-clicked (e.g. inWINDOWSt Explorer). The window below then appears:

Fig. 25 : Extract program

Clicking the “Next >” button starts data extraction and the data is automatically copied intothe correct directory.

Note: The partition in which the extract program runs must be smaller than 3 GB. Theextract program can otherwise not be started.

Chapter 3

28PagePreparation

E 531 920 / 02 E-- 05.2002 --

The actual import procedure can now be started.

The text box below appears immediately after clicking the “Import data” button (in theDiaSys program):

Fig. 26 : Information about data import

Only ever confirm this message with “Yes” when extraction has been carried out as des-cribed on page 27.


Page 29

E 531 920 / 02 E -- 05.2002 --

The window below then appears:

Fig. 27 : Import of engine data set

It is now necessary to state which data (i.e. data of which engine number) is to be impor-ted. The data is marked by an “x” in the “Import” column. Clicking the appropriate fieldreverses selection.

Chapter 3

30PagePreparation

E 531 920 / 02 E-- 05.2002 --

Having selected all desired engine numbers, transmission is started by clicking the“Import” button. The window below appears after (successful) completion of the transmis-sion:

Fig. 28 : Confirmation of successful import


Page 31

E 531 920 / 02 E -- 05.2002 --

3.4.6 Edit engine data from local database


Description

Indicates available engine numbers. Engine data sets in the local database are deletedwith the “Delete” function. The engine numbers marked in the “Delete” field are deleted.

Note: Data sets are automatically deleted on transferring data via modem or LAN.Automatic deleting does not take place on transferring via disk.

Fig. 29 : Delete engine data from local database

Refer to:Chap. 3.4.4 Install transmission line to central databaseChap. 3.4.4.1 Transmit parameter set to central databaseChap. 3.4.4.2 Load set of parameters from central databaseChap. 3.4.5 Import from disk, export to disk

Chapter 3

32PagePreparation

E 531 920 / 02 E-- 05.2002 --

The “Delete” button is enabled as soon as at least one engine number is marked with an“x” in the “Delete” column (clicking the appropriate field reverses the selection):

Fig. 30 : Deleting engine data from the local database


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.txt” fileduring a DiaSys session. Allows the “log.txt” file to be displayed and the language to beselected (German or English). Standard values can also be re-established with “Defaultsettings”.

If a “Default type of unit” is listed, it becomes the default controller when the program isstarted and manual controller type selection is omitted in this case.

If “No default type of unit” is selected, the “Select type of unit” window is not omitted.

Fig. 31 : Options

Refer to:Chap. 3.4.7.1 Select languageChap. 3.4.7.2 Display logfile “Log.txt”

Chapter 3

34PagePreparation

E 531 920 / 02 E-- 05.2002 --

3.4.7.1 Select language

Description

Switches the active language in DiaSys (between German or English).

Activate the “Switch program language of DiaSys” checkbox with the mouse.

Fig. 32 : Switch program language

Proceed as follows to change the language for DiaSys:

¯ Click the “Ok” button

¯ Confirm the message which appears with “OK”.

Fig. 33 : Select language prompt


Page 35

E 531 920 / 02 E -- 05.2002 --

Note: The window shown below only appears after DiaSys has been restarted.

Select desired language:

Fig. 34 : Select language

Proceed as follows to change the language for DiaSys:

¯ Click the “Ok” button.

¯ DiaSys then restarts with the selected language.

Chapter 3

36PagePreparation

E 531 920 / 02 E-- 05.2002 --

3.4.7.2 Display logfile “Log.txt”

Description

The “log.txt” file records all events in a DiaSys session stating date and time. This makesit possible to understand sequences of events. Screen outputs are recorded in particular.“log.txt” is a simple text file (ring memory design).

Fig. 35 : Example of a log.txt file

DiaSys in use with controllersChapter 4

Page 37

E 531 920 / 02 E -- 05.2002 --

Chapter 4

DiaSys in use with controllers

Chapter 4

38PageDiaSys in use with controllers

E 531 920 / 02 E-- 05.2002 --

4 DiaSys in use with controllers

Description of the “Available functions” window

This window indicates the functions which are available for the unit concerned.(The windows may vary slightly depending on the type of controller connected and theselected type of activity).

Fig. 36 : Available functions

Refer to:Chap. 4.2 Start data recordingChap. 4.3 Stop recordingChap. 4.4 Evaluate recorded dataChap. 4.1 Establish data link to controllerChap. 4.8 Injector codeChap. 4.5 Modify single-parameterChap. 4.6 Modify 2-D parameterChap. 4.7 Modify 3-D parameterChap. 4.9 Transmit modified data to controllerChap. 4.11 LogfilesChap. 4.12 ExtrasChap. 4.14 Maintenance forecastChap. 4.10 Transmit to controllerChap. 4.13 To menus


Page 39

E 531 920 / 02 E -- 05.2002 --

4.1 Establish data link to controller

Description

When the controller is connected it is addressed via a serial interface (COM1, COM2 orCOM3). 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 “Connect” button (switchcloses) and clicking the “Ok” button. 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 “Disconnect” button (Offline mode).

Fig. 37 : Data link to unit

Data recording can be started after successfully establishing the connection!

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.2 Start data recording

4.2.1 Start recording of measured data without trigger

Selected measured data can be read-out of the controller. It can be saved and represen-ted graphically.

Note: The window below only appears when it is activated (as required).

Click the “No” button in the window below if no trigger has been defined or no trigger is tobe selected.

Fig. 38 : Prompt for measured data recording

This window is used to select measured data.

Fig. 39 : Select sensors for data recording


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 datarecording

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 severalsensors or hold down the Shift key and click several sensors.

Deselects the marked sensors in “data recording”. Individualsensors can also be deselected by double-clicking.Drag the mouse over the desired sensors to mark severalsensors 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 thesensors for the y(t)-curve in the same way.

Recording starts on clicking the “Ok” button!

Note: The “Available functions” dialog box is minimized prior to graphic data repre-sentation. To stop data recording, for example, the window must be reset to itsoriginal size.

Refer to:Chap. 4.3 Stop recordingChap. 4.4 Evaluate recorded dataChap. 4.2.2 Select an active triggerChap. 4.2.3 Properties of recordingChap. 4.4.1 Offline and online y(t)-graphic

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.2.2 Select an active trigger

Description

Data recording started by a trigger condition is also possible. A trigger can comprise oneor more start/end condition logic operations. Data recording starts/ends when the triggercondition has been fulfilled.

Triggers can only be defined (created) via the menu-guided user interface.

Triggers are selected in the window below:

Fig. 40 : Select an active trigger

4.2.3 Properties of recording

Description

Use the property window page to view and edit general information about the recordingfile (label, user and note).

Fig. 41 : Properties of recording


Page 43

E 531 920 / 02 E -- 05.2002 --

4.3 Stop recording

Description

Stops the data recorder.Click the “Yes” button to allow recorded data to be saved under a random file name.

Fig. 42 : Save modifications prompt

Fig. 43 : Save as

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.4 Evaluate recorded data

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


Page 45

E 531 920 / 02 E -- 05.2002 --


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 severalsensors 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 severalsensors 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 “Ok” button.

Refer to:Chap. 4.2 Start data recordingChap. 4.3 Stop recordingChap. 4.4.1 Offline and online y(t) graphic

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.4.1 Offline and online y(t) graphic

Description

This window shows the measured values over a period of time.

Unit

Measuringpoint list

Referenceto measuringpoint list

Fig. 46 : Measured values over a period of time

Measuring point list

A B C D E

Fig. 47 : Meaning of the individual items


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-sensitive menus for offline and online y(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 toopen these popUp menus).

Y-axisinscription

X-axisinscription

Display field Measuring point list

Fig. 48 : PopUp menus for offline and online Y(t) graphic

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.5 Modify single-parameter

Note: Not available for R082 governor!

Description

A window appears at first allowing selection of single parameters.

Fig. 49 : Select single-parameters

The selected parameters are then displayed in a window. The properties window isopened by pressing key combination Ctrl+Alt+P.

Refer to:Chap. 4.6 Modify 2D-parameterChap. 4.7 Modify 3D-parameter


Page 49

E 531 920 / 02 E -- 05.2002 --

4.6 Modify 2D-parameter

Description

A window appears 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


E 531 920 / 02 E-- 05.2002 --

4.7 Modify 3D-parameter

Description

A window appears 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.


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 “Transmit” button is clicked, a window ofthe 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 clickingthe “Send” button once more.

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.9 Transmit modified data to controller

Description

The following type of window appears 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 “Send” button.

Return to the higher-level window by clicking the “Cancel” button.


ParNr Parameter number

Parameter Parameter designation

Type Type of modified parameter (dimension, axis with index)

PC-value New value to be transmitted

Active-value Old value to be overwritten

Unit Unit of measurement for the relevant parameter


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 window appears if all parameters are identical:Please click the “OK” button.

Fig. 56 : Information “Identical parameters”

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.10 Transmit to controller


Description

Engine data sets (functional software and engine parameter sets) can be transmitted tothe 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 becompletely deleted and reloaded. The second function shall only be used in thiscase.

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)


Page 55

E 531 920 / 02 E -- 05.2002 --

4.10.1 Transmit set of engine parameters


Description

This is the usual method for transmitting engine parameter sets from the local database tothe controller.

A connection must have been established to the controller (Online mode).Furthermore, the engine number from the units assembly description and controller mustalso be available in the local database. The parameters in the controller are deleted andwritten anew. DiaSys decides whether it is necessary to transmit new FSW to 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 parameterset commences immediately.

Refer to:Chap. 4.10.2 Delete controller and transmit anew

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.10.2 Delete controller and transmit anew

Note: Applies to MDEC-ECU C2 and ECU-183 controllers only!

CAUTION

Applies to MDEC-ECU C2 only:Load profile data of the controller is deleted during this activityand not automatically transmitted to the controller.

Only backup the maintenance indicator with the engine at astandstill.

Description

All data in the controller is deleted. The engine parameter set and functional software aresubsequently reloaded.

The appropriate data must be available in the local database to do this. Particularly theengine number from the 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 allowthis 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 “OK” button to transmit FSW and MPS data to the controller.

Fig. 60 : “Switch off controller” information window


Page 57

E 531 920 / 02 E -- 05.2002 --

Fig. 61 : “Switch on controller” information window

As indicated in the windows above, the following steps must be taken in the given order:

¯ Switch off the controller.

¯ Confirm with OK.

¯ Switch the controller back on within 30 seconds.

Transmission commences when all requirements are fulfilled (indicated by the followinganimated graphic):

Fig. 62 : Animated graphic “Data transmission”

Note: Please be patient. The length of the transmission is not known in advance andmay take up to 25 minutes.

Fig. 63 : “Toggle controller off and on” information window

Note: The controller must be subjected to a “Power-On-Reset” in order to completetransfer of the freshly loaded data to the controller. The controller must beswitched off and back on again to do this. This must be confirmed by clickingOK as shown in fig. 63.

The controller data which has just been transmitted is read-in at the end after which thesystem returns to its normal state.

Chapter 4


E 531 920 / 02 E-- 05.2002 --

1D: 3.20

Fig. 64 : “Receiving data from controller” information window

Refer to:Chap. 4.10.1 Transmit set of engine parameters

4.11 Logfiles

Description

Provides an overview of all available logfiles

Fig. 65 : Logfiles


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 window displaying error messages (error record). Puts the error message inchronological order.

Fig. 66 : Error record

A popUp menu can be opened by clicking the right mouse key (click in the grey area atthe top):

Fig. 67 : “Chronological order” popUp menu

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.11.2 Modification logfile

Note: This function is not available for R082 governors!

Description

Parameter modifications are automatically recorded by DiaSys. This menu option opensthe window displaying parameter modifications.

Fig. 68 : Logfile of user activities

Parameter modifications carried out with the unit assembly description open are recorded.


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 window are:

¯ Date/time

¯ Type of activity (extended as necessary)

¯ Description:Type DescriptionUse Opened by userDev Device selectedCha Parameter change

Note: This information is also deleted when the unit assembly description is deleted.

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.11.3 Parameter modified by ...

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 awindow in 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.


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 : ID of unit

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.12 Extras

Description

These display information about the active hardware key and the engine number (theextras window varies slightly depending on the controller).

Fig. 71 : Extras

Note: Available for the following types of controller:

Function Available for:

Hardware key info All controllers

Show engine 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


Page 65

E 531 920 / 02 E -- 05.2002 --

4.12.1 Export into 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


E 531 920 / 02 E-- 05.2002 --

4.12.2 Import Excel-file

Note: This function is not available for R082 and MDEC-ECU C2 controllers.

Description

Imports parameter values from an Excel file and subsequently transmits the data to thecontroller.

Fig. 73 : Import from Excel

Refer to:Chap. 4.12.1 Export into Excel-file


Page 67

E 531 920 / 02 E -- 05.2002 --

4.12.3 Hardware Key Info

Description

This window displays information about the hardware key.

Fig. 74 : Hardware key info


Registered user Registered for

Serial number Serial number of the hardware key

Validity period Indicates how long 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 registereduser can only work with these types of unit.

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.12.4 Show engine number

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 “Showengine number”.

Fig. 75 : Show engine number

4.13 To menus

Description

It is possible to change to the menu-oriented user interface depending on the hardwarekey, the controller and the selected user group.

Additional functions are available in the menu-oriented user interface which is intended forthe 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-orienteduser interface.


Page 69

E 531 920 / 02 E -- 05.2002 --

4.14 Maintenance forecast

Note: Maintenance indicator functions are only available for MDEC-ECU C1 and C2(certain functional parts only) and ECS-Uni controllers!

Description

Displays an overview of all functions pertaining to the maintenance indicator.

Fig. 76 : Maintenance forecast

Refer to:Chap. 4.14.1 Confirm scheduled maintenanceChap. 4.14.5 Confirm load depending maintenanceChap. 4.14.2 Scheduled maintenance datesChap. 4.14.4 Load depending maintenance datesChap. 4.14.6 Load profileChap. 4.14.7 Endurance matrixChap. 4.14.14 Save data for evaluationChap. 4.14.13 Save all (for restoration)Chap. 4.14.12 RestoreChap. 4.14.8 TBO-parameterChap. 4.14.3 Shift maintenance scheduleChap. 4.14.9 Tolerance of maintenance datesChap. 4.14.10 Modify K-constantChap. 4.14.11 New Ti Matrix

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.14.1 Confirm scheduled maintenance

Note: Available for ECS-Uni only!

Description

Scheduled maintenance work is acknowledged here. Maintenance interval and due dateare 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


Page 71

E 531 920 / 02 E -- 05.2002 --

4.14.2 Scheduled maintenance dates


Description

The record of scheduled maintenance dates is displayed here.

The dates are shown in chronological order. The maintenance date is indicated if theexecution of maintenance work has been confirmed.

Fig. 78 : Scheduled maintenance dates

Refer to:Chap. 4.14.1 Confirm scheduled maintenance

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.14.3 Shift maintenance schedule


Description

The defined maintenance schedule can be shifted by a certain period of time here.

The schedule can be shifted by a maximum of 240 months. The next maintenance datebefore shifting is shown at “Upcoming maintenance date”. The new date after shifting isindicated at “Rescheduled date”.

Enter the number of months by which the maintenance schedule is to be shifted and clickthe “Ok” button.

Fig. 79 : Shift scheduled maintenance dates

Refer to:Chap. 4.14.1 Confirm scheduled maintenance


Page 73

E 531 920 / 02 E -- 05.2002 --

4.14.4 Load depending maintenance dates


The load depending maintenance record is displayed here.

The record shows after how many operating hours maintenance was acknowledged(executed). Deviations from the due date are indicated under “Deviation”.

Fig. 80 : Load depending maintenance

Refer to:Chap. 4.14.5 Confirm load depending maintenance

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.14.5 Confirm load depending maintenance


Description

This window allows load-depending maintenance to be acknowledged. Mark the mainte-nance work for acknowledgement and click “Confirm”. The right-hand column indicatesthe time when maintenance is due in hours (h). It also indicates whether maintenance isdue 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


Page 75

E 531 920 / 02 E -- 05.2002 --

4.14.6 Load profile

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-keymouses, 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 evaluation” function asdescribed in chapter 4.14.14 to use data for purposes of evaluation.

Chapter 4


E 531 920 / 02 E-- 05.2002 --

A context-sensitive menu appears on clicking the right mouse key in the grey areabetween data and display window.

Fig. 83 : Context-sensitive load profile menu

The next and previous levels can be displayed with “Alt >” and “Alt <”.


Page 77

E 531 920 / 02 E -- 05.2002 --

4.14.7 Endurance matrix

Description

This displays the endurance matrix (Ti matrix) of the engine. The potential service life ofthe engine can be estimated from this information. The endurance matrix of the engine isconstant 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-keymouses, this is possible by holding down the middle mouse key.

A context-sensitive menu appears on clicking the right mouse key in the grey areabetween data and display window.

Fig. 84 : Context-sensitive Ti endurance matrix menu

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.14.8 TBO-parameter


Description

This window allows TBO parameters to be displayed and entered. The values on the leftcan be edited. The values on the right are projected/current values.

Data which has been modified can be saved by clicking the “Close” button or discarded byclicking “Cancel”.

Fig. 85 : TBO-parameter


Page 79

E 531 920 / 02 E -- 05.2002 --


TBO Expected service life of the engine

Operating hours Engine operating hours

Offset Period of time by which maintenance services W5 and W6 have beencarried out prematurely.This period of time is subtracted from the calculated service life of theengine.

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.) Maximum engine speed

FRP (max.) Fuel rack position under full engine load conditions

Power (max.) Maximum engine power

FRP factor Scaling factor

FRP offset Scaling factor offset

Refer to:Chap. 4.14.10 Modify K-constant

Chapter 4


E 531 920 / 02 E-- 05.2002 --

4.14.9 Tolerance of maintenance dates


Description

This window allows new tolerances for acknowledgement of load-depending maintenancedates to be acknowledged.

The tolerance for each type of maintenance work for which acknowledgement is possiblecan be defined.

The tolerances are stated as a percentage of the due value.

Fig. 86 : Tolerance of maintenance dates


Page 81

E 531 920 / 02 E -- 05.2002 --

4.14.10 Modify K-constant


Description

This window allows 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


E 531 920 / 02 E-- 05.2002 --

4.14.11 New Ti Matrix


Description

A new endurance matrix (TI-matrix) can be read in from a data carrier.

Click “Browse...” to open a window allowing selection of an appropriate file. The file musthave 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 from disk. The disk used for thismust have been created using the “Save all (for restoration)” function as described inchapter 4.14.13.

This is necessary e.g. after replacing hardware.

CAUTION

The maintenance indicator shall only be restored with the engineat a standstill.

Refer to:Chap. 4.14.13 Save all


Page 83

E 531 920 / 02 E -- 05.2002 --

4.14.13 Save all

Description

This menu option backs the maintenance indicator up to disk (see chap. 4.14.12). Havean empty, formatted disk ready in this case.

This data cannot be used for evaluation. The function described in chap. 4.14.14 isnecessary to do this.

A progress bar is displayed in the status line. Follow the instructions on the screen.

CAUTION

The maintenance indicator shall only be saved with the engine ata standstill.

Refer to:Chap. 4.14.12 Restore

4.14.14 Save data for evaluation

Description

Saves the data (load profile, etc.) in Excel format for evaluation at a later date.

Chapter 4


E 531 920 / 02 E-- 05.2002 --


Programming MEM modulesChapter 5

Page 85

E 531 920 / 02 E -- 05.2002 --

Chapter 5

Programming MEM modules

Chapter 5

86PageProgramming MEM modules

E 531 920 / 02 E-- 05.2002 --

5 Programming MEM modules

Description

MEM memory modules can be programmed. This feature requires a Backup Data Moduleand 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 pin assignment of the cable (MTU item no. 535 530 75 34)

The connector pin assignment of the cable is as follows:

9 pole sub DFB-1 connector

Potential9-pole sub-DBDM 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).


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 orhigher must be available.

¯ Check that option 0 (station type) is assigned to PPS using theE2_PROGR.OUT program (see also fig. 90).

¯ Four directory levels must be available below the initial path (this is stated inthe BDM settings). Data must be in the fourth directory.The “Programming” button 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 theMCS-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 “PU” data.

¯ MEM-5 modules which have already been programmed are written over withoutwarning.

¯ BDM and dialog software must be set to the same baud rate to program theMEM-5 modules.

Chapter 5


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 from BDM to plant) is no longerguaranteed if the transmission rate (option 3 in fig. 90, marked with a *) is notset to 125 kBaud.


Page 89

E 531 920 / 02 E -- 05.2002 --

Proceed as follows for programming:

Select “Product support” in 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


E 531 920 / 02 E-- 05.2002 --

5.1 Prepare for “BDM” programming

Fig. 93 : Prepare for “BDM” programming

Start preparation by clicking the “Prepare for “BDM” programming...” button. The windowwhich then opens requires confirmation of whether the directory structure is to be createdfor project configuration data (PU) or basic software.

Fig. 94 : Option window for directory structure


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


E 531 920 / 02 E-- 05.2002 --

Clicking the “Select” button opens a window in which the appropriate file can be chosen.

Fig. 97 : Search and select file

Once all the necessary information has been entered, preparation for BDM programmingis completed by clicking the “Execute” button.

Fig. 98 : Completing preparation for BDM programming


Page 93

E 531 920 / 02 E -- 05.2002 --

5.2 Programming mode

Fig. 99 : Programming mode

Select programming mode by clicking the “Programming mode...” button.

Fig. 100 : Indicating readiness for operation

Click the “OK” button as soon as the pre-requisites for a safe system state have been ful-filled (BDM is connected to the dialog PC, power supplies are connected and stable).

Chapter 5


E 531 920 / 02 E-- 05.2002 --

Choose “PU” Data or Basic software in the “Type of data” field as shown in figs. 101 and102.

Fig. 101 : “PU” Data option

Fig. 102 : Basic software option

The path (directory levels) must match the examples shown above, the “Program” buttonis otherwise not enabled.

Select the CAN interface used by the PC in the “PCMCIA channel” field.


Page 95

E 531 920 / 02 E -- 05.2002 --

A transmission rate of 400 kBaud can also be selected in the “Baudrate” field. However,this means that the transmission rate in the BDM must also be set to 400 kBaud using theE2_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 downloadingfor this reason.

Clicking the Program button starts the programming sequence.

The warning described earlier (see fig. 100) must be re-confirmed. The dialog systemestablishes an online link to the BDM (green field, bottom right).

A programming progress bar as shown in fig. 103 appears when everything is correctlyset 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


E 531 920 / 02 E-- 05.2002 --

A monitoring window appears on completion of programming which shows a record of theprogramming 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 “PU” data onolder versions (DiaSys, device software).

Documents

E531920_02E