Document No.: E4.08.09 E4.08.09 : AE_xx_000
Revision: 13 9 : 00
Page: 52 of 89
Copyright © 2019, Austro Engine GmbH
Dept.: Electric/Electronic
8.2.8.1 The Event Recorder Window
The previous steps will cause the AE300-Wizard to read in and interpret the selected event
recorder hex dump file and to open a new window displaying the result (combining data
from both ECUs):
- Per default the events are sorted by their timestamp (the left most column)
- The data displayed can be sorted in ascending or descending order by clicking on the
columns headers (e.g. clicking on the DTC header will sort all events by their DTCs)
- A red background marks the “beginning” of an event (i.e. “Rail pressure below normal
range”)
- A green background marks the “end” of event (i.e. the event “Rail pressure below nor-
mal range” has ended and the rail pressure is back to normal now)
Example:
Interpretation:
- April 15
th
, 2009 at 8:37:39 (DTC=1E34, event status=00000001, event count=122h)
- DTC 1E34 is a “rail pressure operating range” event of the type MIN. The code is auto-
matically translated into the textual description “Rail pressure below normal range”
- The event status (see layout in appendix “12.3.1 Event Status”) is automatically trans-
lated into “beginning of an event” (i.e. the rail pressure fell below a predefined limit)
and it was recorded at ECU-B which was also the active ECU at that time
- This was event queue entry 290 decimal (122 hex)
- April 15
th
, 2009 at 8:37:39 (DTC=1E34, event status=00000000, event count=123)
- Active ECU B recorded (as entry number 291dec/123hex) the end of the event “rail
pressure below normal range” (rail pressure increased again above a predefined limit)
- The timestamp resolution is 1 second, so this was a very short pressure fluctuation
- The two lines above show, that the passive ECU A detected and recorded the same rail
pressure fluctuation about 1 to 2 seconds later.
To Next Page
Loading...
Need help?
General