Цитата:
Сообщение от A.S.A.T.
Случаем пункты 21 и 22 к инжекторам никакого отношения не имеют?
|
По хакингу прошивке не похоже,ближе к MISFIRE (JTEC отслеживает изменение в угловом ускорении коленчатого вала и определяет в каком цилиндре происходит ухудшение такта рабочего хода.)
Там же добавил доки по DRBIII.
Там только это.
Freeze Frame Data #1
Stores vehicle information at the time a DTC or a 1-Trip failure was detected.
Freeze Frame Description: Freeze Frame is a snapshot of engine operating conditions at the
time a failure occurs. Freeze Frame data is stored for MIL-illuminating DTCs and 1-trip
failures. When the second consecutive occurrence of the 1-trip failure is detected, the data
stored in Freeze Frame is not overwritten; only its priority is updated. Only a fault of a
higher priority can overwrite a fault in Freeze Frame 1.
Freeze Frame Data #2
Stores vehicle information at the time a DTC or a 1-Trip failure was detected.
Freeze Frame 1 vs. Freeze Frame 2: Freeze Frame 1 always contains the DTC responsible for
the first MIL illumination, whether the MIL is currently illuminated for that particular fault
or not. The only exception is if a higher priority fault has overwritten the information in
Freeze Frame 1. Freeze Frame 1 can only be overwritten by a higher priority fault. If it is
overwritten, the DTC is NOT moved to Freeze Frame 2, but is overwritten.
Freeze Frame 2 contains any subsequent DTCs. If a new DTC occurs, it overwrites the fault
currently in Freeze Frame 2, unless the fault is a higher priority than the one in Freeze
Frame 1. In this case, the new fault overwrites the fault in Freeze Frame 1.
NOTE: Some controllers have only one frame while others can have more than two frames
of data. The intent of these additional frames of data is to store the condition of the vehicle
at the time of the DTC event. This data may be helpful in trying to duplicate the failure
conditions.
И хороший пример использования FREEZE FRAME в конце страницы .
http://mmc-autoelectric.org.ua/kody-...sfire-detected