Start page To favorites Print page |

### Introduction to ALADIN and vehicle diagnostics

#### In the world of vehicle diagnostics, you will face the most varied tasks every day. ALADIN therefore includes a variety of functions that are all combined in the generic term "diagnostics" and will support your work with Voith DIWA transmissions.

The term vehicle diagnostics describes the precise assignment of findings about errors in electrical and electronic components in motor vehicles. This includes a series of technical applications which are used for troubleshooting, vehicle configuration and vehicle optimization. In addition, vehicle diagnostics provide information and warnings to the driver about errors that have occurred and for initiating deactivation if safe operation cannot be assured. Vehicle diagnostics are essentially divided into three areas:

- On-Board Diagnosis
  Diagnostic components within the vehicle, also called in-vehicle diagnosis.

- Off-Board Diagnosis
  Tools that can be used to assist in error finding and subsequent repair.

- EOL Diagnosis
  End-of-line diagnosis takes place when commissioning the vehicle. For this, special operating modes are implemented in the controller.

Colloquially speaking, vehicle diagnosis refers to the communication between an external test device (diagnostic tester) and the electronic components (controllers) via a diagnostic protocol.

## On-board diagnosis

The on-board diagnosis consists essentially of the monitoring of the sensors and actuators connected to the controller, the plausibility check, the evaluation of current states and signals against target values, characteristic curves or algorithms, and the failure monitoring of cyclically-incoming information such as connected CAN systems and their data.
The controllers perform this self-monitoring during ongoing operation. If one or several error(s) are detected, the results are saved in the event memory of the controller as Diagnostic Trouble Codes (DTCs). Later, these can be read out using the diagnostic tester.
In case of safety-relevant errors, they are displayed to the driver on the dashboard.

The on-board diagnosis takes place in the controller and provides information for a diagnostic tester.
The DTCs are defined by each OEM independently. DTCs that are displayed on the dashboard can only be decoded by the respective OEM. The assignment of an OEM DTC to a Voith DTC is only possible in exceptional cases.

## Off-board diagnosis

Off-board diagnosis is free troubleshooting. After the diagnostics tester has read the data stored in the controller (including the DTCs), they are supplemented by additional information such as test instructions or wiring diagrams. With these test instructions, it should be possible to remedy all problems detected in the on-board diagnosis. Furthermore, there are errors which extend beyond the system limits of on-board diagnosis. Therefore, off-board diagnosis offers special test procedures for the analysis of sensors and actuators.
Example: A sticking solenoid valve does not cause an electrical error (since it is electrically OK) and thus cannot be detected by on-board diagnosis. The diagnostic tester therefore offers the actuator test test procedure. This enables a service technician to check the mechanically-correct functioning of the solenoid valve.

Off-board diagnosis takes place in the diagnostic tester and in the interplay between the diagnostic tester and controller, and is performed actively by the service technician.

## EOL diagnosis

EOL diagnosis is used for commissioning a vehicle. Here, the functionality of the controller is configured and calibrated.

## Diagnostic communication

The link between on-board diagnosis and off-board diagnostic tools is diagnostic communication. Using standardized hardware and software interfaces, the controllers installed in the vehicle connect to the diagnostic tester.
The diagnosis of Voith vehicle components is currently carried out under the KWP2000 (on K-Line hardware) and UDS (on CAN-BUS) protocols. Both hardware and protocol are strictly standardized, since a multitude of controllers are installed in each vehicle, which can all be addressed by an OEM diagnostic tester (e.g. MAN-Cats STARdiagnose). In addition, there are legal regulations for the diagnosis, which are derived, for example, from the emissions regulations (OBD2).
Essentially, the diagnostic communication runs as a "question/answer game". A client/server model underlies this. The controller functions as a server and the tester as client. Since all controllers and testers are connected together on one line, each device is assigned a physical address.

## ALADIN software and hardware

To use the ALADIN diagnostic software, you need a PC which meets the system specifications, a diagnostics interface (level converter) and, optionally, a vehicle-side adapter plug.

Make sure that you are always using the latest ALADIN version. Only in this way can you ensure that your diagnosis system will support all diagnostic functions. The latest ALADIN version is available for download at Voith.com.

Diagnostics interfaces are available in different versions. Please check which one meets your requirements on the Interface page.

## The ALADIN range of functions

The primary function in ALADIN is to read the event memory and its visualization in the Reporter. Reading is carried out via the Upload function. All of the controller data are read and stored in a so-called ECU file. These files are stored on the local hard disk. This makes it possible to collect vehicle data, exchange them with Voith Customer Service and to archive them. With the ALADIN Delta and Fleet reports, you are able to compare different vehicles and/or compare the same vehicle at different points in time.
Apart from evaluating events, ALADIN also provides functions that support you in the maintenance and installation of a new transmission and in troubleshooting your vehicle.

Please note that there are different authorization levels for users in ALADIN. We call these User Levels. The User Level decides which functions are available to you. All other functions are hidden so you will not see them.
We call the entry level after installation the 'Customer Level'. This help system also describes functions that are not available in the Customer Level.

Upload | The Upload reads the event memory of a transmission controller and creates an ECU file for the ALADIN ECU report. The event memory can also be cleared. |  |
Download | The Download enables the loading of HEX files (software or dataset) into a transmission controller |  |
Reporting | The Reporter visualizes all contents of the ECU file. This provides you with access to the event memory, diverse key figures and operating data or the vehicle configuration. |  |
Service | Various functions for Off-Board and EOL diagnostics | EOL Configuration Adaptation of the vehicle configuration via a set of parameters. TIM Configuration Reading and writing of the Transmission Identification Module (in short, TIM, is an electronic nameplate). Gear Shift Program Configuration Configuration of the transmission gear shift logic. The gear shifting characteristics are adapted to the needs of the topography, performance requirement and efficiency optimization. Service Data Reading and writing of service data. Service data are used to optimize services and allocate an ECU file to a service case. Reset Functions Diverse counter and settings in the controller can be reset. Actuator Test The actuator test is used for targeted troubleshooting on the solenoid valves. Relay Test The relay test is used for checking the switch-on relay in E200 controllers. Event Monitor Real-time monitor for the event memory Transmission Monitor Real-time monitor for diverse sensor signals in the transmission Oil Change Supports the transmission oil change Pushbutton selector Visual inspection of the pushbutton selector IO Test Status check of the configured inputs and outputs. Brake Switch Status check of the brake switch inputs. Load Transmitter Status check of the load transmitter inputs. |