# Using the Online Monitor / Event Memory window In the Online Monitor window, the status of the event memory and a connected transmission control unit is read and displayed at intervals. For monitoring specific events you can either delete individual entries from the event memory or delete the complete event memory. In addition, an ALADIN report on the current state of the event memory can be created at any time. You can also reset the transmission control unit.
| How to open the Online Monitor
Click the Service and then the Clear Fault Memory button in the main window. The Online Monitor window appears, where communication with a connected transmission control unit is established automatically and the event memory is read in at intervals.
| How to stop communication with the transmission control unit:
> | Click the symbol to stop communication with the transmission control unit. This function is required for debugging tasks only.
| How to start communication with the transmission control unit:
> | Click the symbol to start reading the event memory at intervals.
| How to clear the complete event memory:
> | Click the symbol to delete the complete event memory.
| How to delete individual events from the event memory:
> | Click the event that is displayed. A safety query appears prompting you whether you want to delete the event.
| How to create an ALADIN report:
> | Click the symbol to create an ALADIN report on the current state of the event memory. This report includes only the currently registered events. For further information, please see: ALADIN report.
| How to reset the transmission control unit:
> | Click the symbol to perform a reset (warm start) of a connected transmission control unit.
| The display in the Online Monitor:
> > The following information is displayed for each event that has been recorded: FMI Failure Mode Identifier The FMI describes the basic event type. The transmission control unit differentiates between 16 different FMIs:
> > FMI | Symptom | Description |
> > 0 | no fault symptom available | No specific event type can be assigned. |
> > 1 | above maximum threshold | A value lies above the maximum threshold. |
> > 2 | below minimum threshold | A value lies below the minimum threshold. |
> > 3 | not plausible | A value is not plausible. |
> > 4 | no signal | No signal is provided. |
> > 5 | short to ground | Short-circuit to ground. |
> > 6 | short to highsource | Short-circuit to supply voltage. |
> > 7 | general short | General short-circuit. |
> > 8 | invalid signal | The signal is invalid. |
> > 9 | device error | General device error. |
> > 10 | disconnection | General line interruption. |
> > 11 | hardware suspect | The hardware is suspect. |
> > 12 | software suspect | The software is suspect. |
> > 13 | signal suspect | A signal is suspect. |
> > 14 | data suspect | Data is suspect. |
> > 15 | special error condition | A special error condition is provided. |
active Indicates whether an event is currently active or passive. For further information, please see: The principle of active and passive events. Event location Indicates the event location / fault location. For further information, please see: Fault locations, fault types, previous fault types and action locations. Details A description of the event is given here. 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)