ECU data / ECU files - Control unit file
| Every control unit in the vehicle is referred to as an ECU (Electronic Control Unit). When using ALADIN, an ECU file (electronic control unit file) is created automatically with every
upload. This file contains all the relevant diagnostic data and is stored on the local hard disk of your PC.
The name of an ECU file is composed of the serial number of the transmission control unit, the current date and the extension .ecu. For example, if a diagnostic session is performed at the transmission control unit with the serial number 4711 on May 20, 2007, a control unit file with the file name "4711-2007-05-20.ecu" will be created. This file is always stored in the folder "C:\Documents and Settings\YourUserName\My documents". You can change this setting under
ALADIN Setup Folders.
 |
|
 |
|
 |
Service data |
Service data contains information on the vehicle, engine, transmission, customer and service. For further information, please see: Service data. |
 |
Identification data |
Identification data describes the elements that the DIWA.5 transmission system is composed of. This includes the transmission, the control unit (hardware), the software etc. This allows for selecting the appropriate components in the event of changes (e.g., a new dataset for new vehicle requirements) or service work. For further information, please see: Identification data in the report. |
 |
Operating data |
Operating data is used to reduce operation expenses, increase availability, optimize the drive line configuration, etc. For further information, please see: Operating data in the report. |
 |
Event memory |
The event memory stores faults that have occurred, messages of the early-warning system and general information. For further information, please see:
Event memory in the report. |
 |
Adaptation data |
Adaptation data are correction values for the control pressure profile calculated by the transmission control unit that optimize the transmission automatically to minimum wear and highest shifting quality. For further information, please see: Adaptation. |
 |
Dataset |
The purpose of the dataset is configuring the functions of the transmission software. The dataset is used, for example, to configure shift programs, define calculation values, determine flexible inputs / outputs or define CAN receive messages. For further information, please see: Dataset in the report. |
 |
History storage |
Certain events such as performing a transmission oil change, configuring the shift programs with an external diagnostic tester or reprogramming actions are stored in a time context in the history storage of the transmission control unit. For further information, please see:
History storage. |
 |
Scourcer |
"Scourcer" is an artificial word that stands for scan source addresses. The function of the Scourcer is to compare the CAN settings for the SAE-J1939 (vehicle standard) receive messages defined in the dataset to the actually existing source addresses in the vehicle. For further information, please see:
Scourcer in the report. |
 |
LID |
LIDs / DIDs are measured values that have been recorded during the upload. This includes the current shift program configuration and the oil level trend memory. For further information, please see: LID |
 |
EOL |
The vehicle-specific variables are set at the end of the line during production using EOL parameters and the corresponding diagnostic services. At present, approx. 200 parameters are vehicle-specific in DIWA.5. This is why they are potentially required for a complete EOL configuration. For further information, please see: EOL |
For the Report, ALADIN also uses this ECU data to calculate the:
 |
Indices |
Indices contain compressed quantitative information on the vehicle and/or transmission application. The indices are calculated from the operating data that has been recorded and cumulated during transmission operation. For further information, please see:
Indices in the report. |
 |
Configuration |
The I/O configuration provides information on the vehicle's CAN configuration, shift program configuration and the configuration of the flexible inputs/outputs at the transmission control unit and the gear range selector. For further information, please see: Configuration in the report. |
 |
Dwell time analysis |
The dwell time analysis provides information on how long and in which operating condition the vehicle has been standing so far during its operating time. For further information, please see:
Dwell time analysis in the report. |
 |
Downloads |
The Downloads area indicates what downloads have been made in a vehicle. For further information, please see: Downloads in the
report. |
 |
SORT data |
SORT is a project between bus carriers and manufacturers for developing standardized fuel consumption tests for buses. For further information, please see: SORT in the report. |
|
 |
|
Carry out an upload. To do so, click
Upload. This will automatically read the complete ECU data from a connected transmission control unit, create the ECU file on your local hard disk and open an ALADIN report. The complete contents of the ECU file are displayed in the report.
When using the Clear Fault Memory function, only the ECU data of the event memory is read from a connected transmission control unit. If you have already made an upload, the file that exists on your hard disk will be updated. If you have not performed an upload yet, a new ECU file will be created. However, this file contains
only the entries of the event memory.
There are two methods of reading an ECU file.
- By double-clicking an ECU file, the Voith Reporter is started automatically and creates a report that displays the complete contents of the ECU file.
- If you have already started ALADIN, click Report in the main window. The dialog box "Select ECU File" appears.
More information on:
Report
More information on:
ECU file formats
More information on:
Setup
More information on: Upload
More information on:
Clear fault memory
More information on: FAQ
Up
> Higher-level section
© by Voith Turbo GmbH & Co. KG
send remarks to joachim.ehleiter@voith.com (electronic department)
or r.theilacker@voith.com (electronic department) |