Diagnostic Document for V42 ECU 2A Software

DED_V42_2A_X79-X90-X35_K7M-K4M-F4R(4.0).
doc
______________ Begin of DED_1.0.0.0.0.0.0_000_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.5).doc ______________
DIAGNOSTIC USER DOSSIER

X90 D4D760 K7M714 K4M694 K4M695 VDIAG $06
X79 F4R400 F4R402 F4R403 K4M606 VDIAG $04
X79 F4R404 F4R405 K4M694 VDIAG $06
X35 K4M674 VDIAG $06
H79 K4M696 VDIAG $05
X65 D4D752 VDIAG $06
V42 ECU / 2A Software
Written by: Reviewed by: Approved by:

Name: C.Abraham
Department: Assystem
Position:
Telephone: +33(0)1.768.71062
Date: 13/12/2009
Signature:
1 / 120
DED_V42_2A_X79-X90-X35_K7M-K4M-F4R(4.0).doc
SPECIFICATION SHEET
AUTHOR(S) NUMBER OF PAGES TYPE OF DOCUMENT

C.Abraham (ASSYSTEM) 120 Report
DOCUMENT TITLE
DED_V42_enveloppe V03
.doc
AUTHOR SUMMARY
KEYWORDS INPUT MODE

Word 2002
REVISION CONTROL
NO. DATE PAGES REVISED REASON(S) FOR REVISION

rev. [AUTHOR(S)]
1.0 13/12/2009 all Initial revision [C.Abraham ASSYSTEM]
2 / 120
CONTENTS
1 Glossary 6
2 Control Unit Identification 9
3 Wiring diagram 10
3.1 Pin-out 10
3.1.1 Connector A 10
3.1.2 Connector B 11
3.1.3 Connector C 12
3.2 Short-Circuit 13
3.2.1 Connector A 13
3.2.2 Connector B 14
3.2.3 Connector C 15
4 Diagnostic resources 17
4.1 Generic services 17
4.1.1 Service StartDiagnosticSession (10h): 17
4.1.2 Service SecurityAccess (27h): 19
4.1.3 Service TesterPresent (3Eh): 20
4.1.4 Service ReadDataByLocalIdentifier (21h) : 20
4.1.5 Service DynamicallyDefineLocalIdentifier (2Ch): 21
4.1.6 Service ReadMemoryByAddress (23h): 22
4.1.7 Service ReadDTCInformation (19h): 23
4.1.8 Service ReadDataByIdentifier (22h): 23
4.1.9 Service InputOutputControlByLocalIdentifier (30h): 24
4.1.10 Service StartRoutineByLocalIdentifier (31h): 24
4.1.11 Service StopRoutineByLocalIdentifier (32h): 24
4.1.12 Service WriteDataByIdentifier (2Eh): 24
4.1.13 Service WriteDataByLocalIdentifier (3Bh): 25
4.1.14 Service ClearDiagnosticInformation(14h): Valeurs initialisées 26
4.2 System conditions restricting the execution of a service 27
4.2.1 Service StartDiagnosticSession (10h): 27
4.2.2 Service SecurityAccess (27h): 27
4.2.3 Service TesterPresent (3Eh): 27
4.2.4 Service ReadDataByLocalIdentifier (21h): 27
4.2.5 Service DynamicallyDefineLocalIdentifier (2Ch): 27
4.2.6 Service ReadMemoryByAddress (23h): 27
4.2.7 Service ReadDTCInformation (19h): 27
4.2.8 Service ReadDataByIdentifier (22h): 27
4.2.9 Service InputOutputControlByLocalIdentifier (30h): 28
4.2.10 Service StartRoutineByLocalIdentifier ( 31h): 28
4.2.11 Service StopRoutineByLocalIdentifier ( 32h): 28
4.2.12 Service WriteDataByIdentifier (2Eh): 28
4.2.13 Service WriteDataByLocalIdentifier (3Bh): 28
4.2.14 Service ClearDiagnosticInformation(14h): 29
4.3 Reference to the DDT database 30
5 FAULT MANAGER 31
5.1 Confirmation and storage 31
5.2 Diagnostic completion status 31
5.3 Disappearance 31
5.4 Context 32
5.4.1 Manufacturer Freeze Frames 32
5.4.2 Last occurrence mileage $80 32
5.4.3 Occurrence counter $84 32
5.4.4 Last disappeared mileage $85 33
5.4.5 Distance travelled failure present $86 33
5.4.6 First occurrence mileage $87 33
3 / 120
5.5 EOBD fault management 33

5.5.1 EOBD pending failure: temporary fault 33
5.5.2 EOBD confirmed failure 33
5.5.3 EOBD freeze frame: context frame 34
5.5.4 Distance covered since the last Clear Diagnostic Information 34
5.5.5 Distance covered with the MIL lit 34
5.6 Warning indicator lighting management 34
5.6.1 Severity warning light 1&2 (WAL 1&2) 34
5.6.2 MIL warning light 35
5.7 DTC & Status 35
5.8 Clear diagnostic information: deleting faults 35
5.9 Graphs 37
6 Using diagnostic resources 40
6.1 Diagnostic trouble codes 40
6.1.1 P0010 – Intake Camshaft Position Solenoid Valve and/or Actuator 40
6.1.2 P0011 – Camshaft Position Solenoid Valve and/or Actuator Control Function 41
6.1.3 P0016 – Crankshaft Position – Intake Camshaft Position Correlation 42
6.1.4 P0095 – Intake Air Temperature Downstream Turbocharger/Supercharger Sensor 43
6.1.5 P0106 – Manifold Absolute Pressure Function 44
6.1.6 P0115 – Engine Coolant Temperature Sensor 45
6.1.7 P0120 – Intake Throttle Position Sensor 46
6.1.8 P0130 – O2 Sensor - Upstream 47
6.1.9 P0135 – O2 Sensor Heater - Upstream 48
6.1.10 P0136 – O2 Sensor - Downstream 49
6.1.11 P0141 – O2 Sensor Heater - Downstream 50
6.1.12 P0170 – Fuel Trim 51
6.1.13 P0201 – Injector Circuit – Cylinder 1 52
6.1.17 P0217 – Engine Coolant Temperature 56
6.1.18 P0220 – Intake Throttle Position Sensor - Track 2 57
6.1.19 P0225 – Accelerator Pedal Position Sensor - Track 1 58
6.1.20 P0226 – Accelerator Pedal Position Sensor 59
6.1.21 P0300 – Random/Multiple Cylinder Misfire Detected 60
6.1.22 P0301 – Cylinder 1 Misfire Detected 61
6.1.26 P0313 – Misfire Detected with Low Fuel 65
6.1.27 P0314 – Single Cylinder Misfire (Cylinder not Specified) 66
6.1.28 P0315 – Crankshaft Position System Variation Not Learned 66
6.1.29 P0325 – Knock Sensor 66
6.1.30 P0335 – Crankshaft Position Sensor 66
6.1.31 P0340 – Intake Camshaft Position Sensor 66
6.1.32 P0420 – Catalyst System 66
6.1.33 P0443 – Canister Purge Valve 66
6.1.34 P0461 – Fuel Level Sensor 66
6.1.35 P0480 – Fan 1 Control Relay 66
6.1.36 P0500 – Vehicle Speed Sensor 66
6.1.37 P0504 – Brake Pedal 66
6.1.38 P0530 – A/C Refrigerant Pressure Sensor 66
6.1.39 P0560 – Battery Voltage 66
6.1.40 P0571 – Closed Brake Sensor 66
6.1.41 P0606 – Engine Control Module - Processor 66
6.1.42 P060A – Engine Control Module - Reset 66
6.1.43 P061A – Engine Control Module - Torque Control Function 66
6.1.44 P0627 – Fuel Pump Control 66
6.1.45 P0638 – Intake Throttle Actuator Control Function 66
6.1.46 P0641 – Power Supply 1 66
4 / 120
6.1.47 P0650 – Malfunction Indicator Lamp (MIL) Control Circuit 66

6.1.48 P0651 – Power Supply 2 66
6.1.49 P0657 – Actuators Power Relay 66
6.1.50 P0703 – Open Brake Pedal Switch 66
6.1.51 P0833 – Begining of Clutch Pedal Move Switch 66
6.1.52 P1351 – Ignition Coil - Cylinder 1 and 4 66
6.1.53 P1352 – Ignition Coil - Cylinder 2 and 3 66
6.1.54 P1633 – Additional Fuel Tank Solenoid Control 66
6.1.55 P1644 – Relay of Air Heater Passenger Compartment 1 66
6.1.58 P1656 – Electromagnetic Torque Control 66
6.1.59 P2100 – Intake Throttle Actuator Control - H Bridge 66
6.1.60 P2119 – Intake Throttle Actuator Offset Learning 66
6.1.61 P2120 – Accelerator Pedal Position Sensor - Track 2 66
6.1.62 P2135 – Throttle Correlation Between The Two Sensors 66
6.1.63 P2502 – Charging System Voltage Circuit 66
6.1.64 P2503 – Charging System Voltage Low Voltage 66
6.1.65 P2632 – Second fuel Pump Control for additional fuel tank 66
6.1.66 PC101 – Lost Communication with Transmission Control Module 66
6.1.67 PC121 – Lost Communication With Anti-Lock Brake System (ABS) Control Module 66
6.1.68 PC402 – Invalid Data Received From Transmission Control Module 66
6.1.69 PC415 – Invalid Data Received From Anti-Lock Brake System Control Module 66
6.2 Status and parameters 66
6.3 Configuration operation(s) 66
6.3.1 Configuration by calibration / reprogramming 66
6.3.2 Configuration by automatic detection 66
6.4 Programming operation(s) 66
6.5 Actuators command (30h) 66
6.6 Routines execution 66
6.6.1 Static test (31 07 00 h) 66
6.6.2 MONITOOL (31 21h) 66
6.6.2.1 Protocol of communication: 66
6.6.2.1.1 General plan: 66
6.6.2.1.2 Activation request: 66
6.6.2.1.3 Stop request: 66
6.6.2.1.4 Reading of supported identifiers: 66
6.6.2.2 Values calculation to send on CAN by identifier: 66
6.6.2.3 Activation conditions and MONITOOL deactivation: 66
6.6.2.3.1 Embarked vehicle watching: 66
6.6.2.3.2 Embarked engine watching: 66
6.6.2.3.3 Bypass watching: 66
6.6.2.3.4 ECM / Tool communication watching: 66
6.6.3 Lbup routine (31 0A 00 h) 66
6.6.4 Catalyst routine (31 08 00 h) 66
6.6.5 Fuel Feed inhibition routine (31 04 00 h) 66
5 / 120
1 Glossary
OTHER
!
2IC : factory correction of the SIEMENS injectors
A
ABS : anti lock brake system
AC : air conditionning
AFS : after sales
AGB : automatic gear box
AS : air system
ASR : anti ski (or skating) regulation
AT : after treatement
AYC : anti yaw control
B
BCM : body control module
C
C2i : factory correction of the DELPHI injectors
C3i : factory correction of the DELPHI injectors
CAN : control area network
CB : combustion
CC : cruise control
CCSL : cruise control / speed limiter
CL : coolant and lubrification
CLIP : RENAULT after sales tool
CO2 : chimical symbol for carbone dioxide
CPS : engine system manager
CRC : checking redundancy code
CSF : combustion soot filter
D
DC : driving cycle
DDT : RENAULT developpement diagnostic tool
DED : diagnostic user dossier
deg C : celsius degrees
DID : data identifier
DIV : vehicle engineering departement
DOC : Diesel oxidation catalyst
DTC : data trouble code
E
ECM : engine control module
ECU : electronical control unit
EEPROM : electrical erazable programmable read only memory
EGR : exhaust gaz recirculation
EOBD : european on board diagnostic
ESP : electronic stability program
ETC : electronic throttle component
EV : electrovalve
6 / 120
F
FM : fault manager
FTDIV : vehicle engineering departement functions
H
H2O : chimical symbol for water
HC : chimical symbol for unburned fuel
HP : high pressure
I
IMV : inlet metering valve (=VCV)
IT : inlet/intake throttle
L
Local ID : local identifier
LSB : last significant bit
M
MAF : mass air flow
MAP : manifold air pressure
MAX : maximum
MCD : Common Diagnostic Data Library
MIL : EOBD malfunction indicator lamp
MIN : minimum
MSB : most significant bit
MSR : deceleration sleep control (Motor Shleppmoment Regelung)
N
NOK : not OK
NOx : chimical symbol for azote oxyde
NRC : non rewritable code
NVMY : non volatile memory
O
O2 : chimical symbol for oxygen
OBD : on board diagnostic
OC : open circuit
OWE : oil wear estimation
P
P4C : name of DELPHI software for CAN M3 architecture
PC : powertrain coordination
PCM : power control module
PTC : habitacle air heater
PWM : pulse width mode
7 / 120
R
RAM : random acces memory
RD9 : name of SIEMENS gasoline software for CAN M3 architecture
ROM : read only memory
RPM : rotation per minute
RR : idle speed regulation
RS1 : name of BOSCH software for CAN M3 architecture
RSA : RENAULT (« société anonyme »)
S
SC : short circuit
SCB : short circuit to battery
SCG : short circuit to ground
SCW : short circuit to power supply
SL : speed limiter
SM : speed managment
T
TDC : top dead center
TEFI : exhaust fuel injection line cutting valve routine
THP : thermoplunger
TQ : torque
U
USM : underhood switches module
V
V.I.N : vehicle identifier number
VCV : volume control valve
Vdiag : diagnostic version number for RENAULT after sales tool
Verlog : immobilizer
VF : vehicle functions
VIN : vehicle identifier number
VVT : variable valve timing
VVTC : variable valve timming continuous
W
WAL : warning alert lamp
Y ________________ End of DED_1.0.0.0.0.0.0_000_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.5).doc ______________
8 / 120
______________ Begin of DED_2.0.0.0.0.0.0_000_3XXXX0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.0).doc ______________
2 Control Unit Identification

This DED can be used for V42 ECU with 2A software.
The corresponding identification we can see on 2180 request is the following:
00 2A xx xx xx xx
________________ End of DED_2.0.0.0.0.0.0_000_3XXXX0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.0).doc ______________
9 / 120
______________ Begin of DED_3.0.0.0.0.0.0_000_3KXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(3.0).doc ______________
3 Wiring diagram
3.1 Pin-out
3.1.1 Connector A
ECU PIN DESCRIPTION

A.A1
A.A2 On/Off cruise control
A.A3 CAN L1(vehicle)
A.A4 CAN H1 (vehicle)
A.B1 Fan 1 relay command
A.B2 TDC engine signal
A.B3 Heat fan in
A.B4 Diagnosis K link
A.C1 Fan 2 relay command
A.C2
A.C3 On/Off speed limiter
A.C4 Clutch signal
A.D1 Voltage battery after key : VBK
A.D2 Cruise control signal + (steering wheel)
A.D3 Cruise control signal ground (steering wheel)
A.D4 Fuel Pump Drive Output
A.E1 CAN L3 (private engine)
A.E2 CAN H3 (private engine)
A.E3 Close brake on signal
A.E4 Open brake on signal
A.F1
A.F2 Pedal potentiometer 1 supply
A.F3 Pedal potentiometer signal 2
A.F4 Pedal potentiometer ground 2
A.G1
A.G2 Pedal potentiometer 2 supply
A.G3 Power ground 4
A.G4 Power ground 1
A.H1 Power ground 2
A.H2 Pedal potentiometer signal 1
A.H3 Pedal potentiometer ground 1
A.H4 Power ground 3
10 / 120
3.1.2 Connector B
ECU PIN DESCRIPTION

B.A1 Injector 1 Output
B.B1 Alliance Tooth Signal Ground
B.B2 Knock control shielding
B.B3 Knock control Input
B.B4 Knock control ground
B.C1 Alliance Tooth Signal Input
B.C2 On AC Input
B.C3 PMH (GPL) Output
B.C4 Steering Pressure Input
B.D1 Alliance Tooth Signal Supply
B.D2 Verlog 2
B.D3 Throttle Potentiometer 2 Input
B.D4 Power Latch Relay Output
B.E1 Turbocharged pressure ground
B.E2 Air temperature signal
B.E3 Air temperature ground
B.E4 Engine Speed Input (-)
B.F1 Turbocharged pressure signal
B.F2 Water temperature signal
B.F3 Engine Speed Input (+)
B.F4 Water temperature ground
B.G1 Turbocharged pressure supply
B.G2 Throttle Potentiometer supply
B.G3 Throttle Potentiometer 1 Input
B.G4 Throttle Potentiometer Ground
B.H1 Gasoline Temperature Input
B.H2 Intake Manifold Power Supply
B.H3 Intake Manifold Input
B.H4 Intake Manifold Ground
B.J1 Gasoline Temperature Ground / Freon
B.J2 Freon Pressure Power Supply
B.J3 Freon Pressure Input
B.J4 Freon Temperature Input
B.K1 Vehicle Speed Input
B.K2 Freon Pressure Ground
B.K3 CAN L2
B.K4 CAN H2
B.L1 Evap Valve / FlexFuel Output / CTP fan relay
Oil Steam PTC Output / Water temperature management / Disconnectable
B.L2
engine water pump
B.L3 Intake VVT Output
B.L4 Water Pump Output
B.M1
B.M2 VBR Power Supply
B.M3 Throttle actuator Output 1 (+)
B.M4 Throttle actuator Output 2 (-)
11 / 120
3.1.3 Connector C
ECU PIN DESCRIPTION

C.A1 Mechanical Ground
C.A2 Oxygen sensor down input
C.A3 ECU Identification
C.A4
C.B1 Oxygen sensor up input
C.B2 Oxygen sensor down ground
C.B3 Output consumption (ADAC)
C.B4
C.C1 Oxygen sensor up ground
C.C2 Analog Power Supply spare 1
C.C3 Analog Input spare 1
C.C4 FlexFuel GEN 21 Input / Airbag_Spd_Hgh
C.D1 Fuel Pump Relay Output
C.D2 FlexFuel Relay Output / CTP_2_relay
C.D3 Analog Input Ground spare 1
C.D4 FlexFuel GEN 22 input / Fuel_tank_gauge_pwm_info or eth_rate_sign
C.E1 Canister Cleaning Output
C.E2 Crank Shaft Sensor Ground
C.E3 Steering Pressure Switch Supply
C.E4 FlexFuel GEN 21 Output / water temperature lamp
C.F1 Cranck Shaft sensor Input
C.F2 Alliance Crank Shaft Power Supply
C.F3 Steering Pressure Switch Ground
C.F4 FlexFuel GEN 22 Output / Engine control lamp
C.G1 Terminal DF Input
C.G2 CTP_1_relay / Relay flex fuel
C.G3 Analog Steering Pressure Input
C.G4 WasteGate Output
C.H1 Default 2 Light Indicator
C.H2 Freeshift lamp up
C.H3 Freeshift lamp down
C.H4 Dual mode Solenoid Valve Output / Disconnect Water & Oil Pump Relay
C.J1
C.J2 MIL Light Indicator
C.J3 Gasoline Evap Pressure Power Supply
C.J4 Gasoline Evap Pressure Power Input
C.K1 Air Conditionning Relay Output
C.K2
C.K3 Default 1 Light Indicator
C.K4 Gasoline Evap Pressure Ground
C.L1 Output 2 Spare / pump w Free Wheel Diode
C.L2 Oxygen sensor up Heater Output
C.L3 Oxygen sensor down Heater Output
C.L4 Ignition Coil 4 Output
C.M1
C.M2 Ignition Coil 3 Output
C.M3 Ignition Coil 2 & 3 Output
C.M4 Ignition Coil 1 & 4 Output
12 / 120
3.2 Short-Circuit
3.2.1 Connector A
additionnal
PROTECTIONS DETECTION DTC
information
OPEN-CIRCUIT
COHERENCE
SC GROUND
SC GROUND
OC <> SCG
OC <> SCV
THERMAL
CURRENT
SC VBAT
SC VBAT
Vmax
Vmin
n° pin Signal Name Signal Type
A.A1 Not used
A.A2 On/Off cruise control Input 0V/Vbat 0V Vbat H H N N N N N N No DTC

Loss of
A.A3 CAN L1(vehicle) Network 0V Vbat H H H No DTC
communication
Loss of
A.A4 CAN H1 (vehicle) Network 0V Vbat H H H No DTC
communication
A.B1 Fan 1 relay command Low Side 0V Vbat H H H H DTC $0480
A.B2 TDC engine signal Low Side PWM H H H H No DTC
A.B3 Heat Fan in Input 0V / Vbat 0V Vbat No DTC
A.B4 Diagnosis K link Network H H H H No DTC
A.C1 Fan 2 relay command Low Side 0V Vbat H H H H DTC $0481
A.C2 Not used
A.C3 On/Off speed limiter Input 0V/Vbat 0V Vbat H H N N N N N N No DTC
A.C4 Clutch signal Input 0V/Vbat 0V Vbat H H N N N N N N No DTC

Voltage battery after key :
A.D1 Input 0/Vbat 0V Vbat H H No DTC
VBK
Cruise control signal +
A.D2 Input 0V/5V 0V Vbat H H N N N N N N No DTC
(steering wheel)
Cruise control signal
A.D3 Ground 0V 0V N N N N N N No DTC
ground (steering wheel)
A.D4 Fuel Pump Drive Output Low Side 0V Vbat H H H H Y Y Y Not used
A.E1 CAN L3 (private engine) Network H H H No DTC
A.E2 CAN H3 (private engine) Network H H H No DTC
A.E3 Close brake on signal Input 0V/Vbat 0V Vbat H H No DTC
A.E4 Open brake on signal Input 0V/Vbat 0V Vbat H H N N N N N N No DTC
A.F1 Not used

Pedal potentiometer 2 Output 5V
A.F2 5V 5V H H H H SW SW DTC $2120
supply supply
Pedal potentiometer signal
A.F3 Input 5V/0V 0V Vbat H H SW SW DTC $2120
2
Pedal potentiometer
A.F4 Ground 0V 0V N N N N N N DTC $2120
ground 2
A.G1 Not used
Pedal potentiometer 1 Output 5V
A.G2 5V 5V H H H H SW SW DTC $0225
supply supply
A.G3 Power ground 4 Ground 0V 0V N N N N N N No DTC
A.G4 Power ground 1 Ground 0V 0V N N N N N N No DTC
A.H1 Power ground 2 Ground 0V 0V N N N N N N No DTC

Pedal potentiometer signal
A.H2 Input 5V/0V 0V Vbat H H SW SW DTC $0225
1
Pedal potentiometer
A.H3 Ground 0V 0V N N N N N N DTC $0225
ground 1
A.H4 Power ground 3 Ground 0V 0V N N N N N N No DTC
D = Destruction
H = Hardware Protection
N = no hardware diagnosis
SW = software detection (Plausibility)
Y = yes / hardware diagnosis
13 / 120
T = threshold diagnosis
3.2.2 Connector B
additionnal
information
OPEN-CIRCUIT
COHERENCE
SC GROUND
SC GROUND
OC <> SCG
OC <> SCV
THERMAL
CURRENT
SC VBAT
SC VBAT
Vmax
Vmin
n° pin Signal Name Signal Type
B.A1 Injector 1 Output Low Side 0V Vbat H H H H Y Y Y DTC $0201

Alliance Tooth Signal No DTC
B.B1 Ground 0V 0V N N N N N N
Ground
B.B2 Knock control shielding Ground 0V 0V N N N N N N No DTC
B.B3 Knock control Input Input 0V H H SW No DTC
B.B4 Knock control ground Ground 0V 0V N N N N N N No DTC

Alliance Tooth Signal
B.C1 Input 0V H H SW No DTC
Input
Loss of
B.C2 On AC Input Input 0V H H N N N N N N
communication
B.C3 PMH (GPL) Output PWM 0V H H H H No DTC
B.C4 Steering Pressure Input Input 0V H H No DTC

Alliance Tooth Signal
B.D1 Analog 5V 5V H H H H SW SW No DTC
Supply
B.D2 Verlog 2
Throttle Potentiometer 2
B.D3 Input 0V H H SW N N N N SW DTC $0220
Input
Loss of
B.D4 Power Latch Relay Output Low Side 0V Vbat H H H H SW SW
communication
Turbocharged pressure
B.E1 Ground 0V 0V N N N N N N Not used
ground
B.E2 Air temperature signal 0V H H SW SW DTC $0095
B.E3 Air temperature ground Ground 0V 0V N N N N N N DTC $0095
B.E4 Engine Speed Input (-) Input 0V H H SW SW No DTC

B.F1 Input 0V H H SW SW Not used
signal
B.F2 Water temperature signal Input 0V H H SW SW DTC $0115
B.F3 Engine Speed Input (+) Input 0V H H SW SW No DTC
B.F4 Water temperature ground Ground 0V 0V N N N N N N DTC $0115

B.G1 Analog 5V 5V H H H H SW SW Not used
supply
Throttle Potentiometer DTC $0220
B.G2 Analog 5V 5V H H H H SW SW
supply DTC $0120
Throttle Potentiometer 1
B.G3 Analog 0V H H SW N N N SW DTC $0120
Input
Throttle Potentiometer DTC $0220
B.G4 Ground 0V 0V N N N N N N
Ground DTC $0120
Gasoline Temperature
B.H1 Analog 0V H H No DTC
Input
Intake Manifold Power
B.H2 Analog 5V 5V H H H H SW SW No DTC
Supply
B.H3 Intake Manifold Input Analog 0V H H SW SW DTC $0106
B.H4 Intake Manifold Ground Ground 0V 0V N N N N N N No DTC
Gasoline Temperature
B.J1 Ground 0V 0V N N N N N N No DTC
Ground / Freon
Freon Pressure Power
B.J2 Analog 5V 5V H H H H SW SW No DTC
Supply
B.J3 Freon Pressure Input Analog 0V H H SW SW DTC $0530
B.J4 Freon Temperature Input Analog 0V H H No DTC
B.K1 Vehicle Speed Input PWM 0V H H No DTC
B.K2 Freon Pressure Ground Ground 0V 0V N N N N N N DTC $0530
14 / 120
B.K3 CAN L2 Network H H H DTC $0530
B.K4 CAN H2 Network H H H No DTC

Evap Valve / FlexFuel
B.L1 Low Side 0V Vbat H H H H DTC $1633
Output
B.L2 Oil Steam PTC Output Low Side 0V Vbat H H H H SW SW No DTC
B.L3 Intake VVT Output Low Side 0V Vbat H H H H Y Y Y Not used
B.L4 Water Pump Output Low Side 0V Vbat H H H H SW SW Not used
B.M1 Not used
B.M2 VBR Power Supply Input 0V Vbat H H H H SW No DTC

Throttle actuator Output 1
B.M3 Différential H H H H SW SW DTC $0638
(+)
Throttle actuator Output 2
B.M4 Différential H H H H SW SW DTC $0638
(-)
D = Destruction
3.2.3 Connector C
additionnal
information
OPEN-CIRCUIT
COHERENCE
SC GROUND
SC GROUND
OC <> SCG
OC <> SCV
THERMAL
CURRENT
SC VBAT
SC VBAT
Vmax
Vmin
N° pin Signal Name Signal Type
C.A1 Mechanical Ground Ground 0V 0V N N N N N N No DTC

Oxygen sensor down
C.A2 0V 18V H H SW SW SW No DTC
input
C.A3 ECU Identification 0V N N N N N N No DTC
C.A4 Not used
C.B1 Oxygen sensor up input 0V H H SW SW SW No DTC

Oxygen sensor down
C.B2 Ground 0V 0V N N N N N N No DTC
ground
C.B3 Not used
C.B4 Not used
C.C1 Oxygen sensor up ground Ground 0V 0V N N N N N N No DTC

Analog Power Supply
C.C2 Analog 5V 5V H H H H No DTC
spare 1
C.C3 Analog Input spare 1 0V 0V H H No DTC
C.C4 FlexFuel GEN 21 Input 0V Vbat H H No DTC
C.D1 Fuel Pump Relay Output Low Side 0V Vbat H H Y Y Y DTC $0627
C.D2 FlexFuel Relay Output Low Side 0V Vbat H H H H DTC $2632

Analog Input Ground
C.D3 Analog 0V 0V N N N N N N No DTC
spare 1
C.D4 FlexFuel GEN 22 input 0V H H No DTC
C.E1 Canister Cleaning Output Low Side 0V Vbat H H H H Y Y Y DTC $0443

Crank Shaft Sensor
C.E2 Ground 0V 0V N N N N N N No DTC
Ground
Steering Pressure Switch
C.E3 5V 5V H H H H No DTC
Supply
C.E4 FlexFuel GEN 21 Output Low Side 0V Vbat No DTC
C.F1 Cranck Shaft sensor Input 0V H H No DTC
C.F2 Alliance Crank Shaft Analog 5V 5V H H H H No DTC
15 / 120
Power Supply
Steering Pressure Switch

C.F3 Ground 0V 0V N N N N N N No DTC
Ground
C.F4 FlexFuel GEN 22 Output Low Side 0V Vbat Not used
C.G1 Terminal DF Input 0V Vbat H H No DTC

Air Pump Relay Output /
C.G2 Low Side 0V Vbat H H H H SW - - SW - No DTC
Relay flex fuel
Analog Steering Pressure
C.G3 0V Vbat H H No DTC
Input
C.G4 WasteGate Output Low Side 0V Vbat H H H H SW SW Not used
C.H1 Default 2 Light Indicator Low Side 0V Vbat SW - - SW - No DTC
C.H2 Freeshift lamp up Not used
C.H3 Freeshift lamp down Not used

Dualmode Solenoid Valve
C.H4 Low Side 0V Vbat H H H H SW - - SW - No DTC
Output
C.J1 Not used
C.J2 MIL Light Indicator Low Side SW - - SW - No DTC

Gasoline Evap Pressure
C.J3 5V 5V H H H H No DTC
Power Supply
C.J4 0V Vbat H H No DTC
Power Input
Air Conditionning Relay
C.K1 Low Side 0V Vbat H H H H DTC $0645
Output
C.K2 0V Vbat Not used
C.K3 Default 1 Light Indicator Low Side 0V Vbat SW - - SW - No DTC

C.K4 0V 0V N N N N N N No DTC
Ground
C.L1 Output 2 Spare Low Side 0V 0V H H H H No DTC
Oxygen sensor up Heater Y/

C.L2 Low Side 0V Vbat H H Y Y DTC $0135
Output SW
Oxygen sensor down Y/
C.L3 Low Side 0V Vbat H H Y Y DTC $0141
Heater Output SW
C.L4 Ignition Coil 4 Output Low Side 0V Vbat SW SW SW SW SW No DTC
C.M1 Not used
C.M2 Ignition Coil 3 Output Low Side 0V Vbat SW SW SW SW SW No DTC

Ignition Coil 2 & 3
C.M3 Low Side 0V Vbat SW SW SW SW SW No DTC
Output
Ignition Coil 1 & 4
C.M4 Low Side 0V Vbat SW SW SW SW SW No DTC
Output
D = Destruction
________________ End of DED_3.0.0.0.0.0.0_000_3KXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(3.0).doc ______________
16 / 120
4 Diagnostic resources
This chapter describes all the diagnostic services availables for aftersales purpose.
4.1 Generic services

Diagnostic Session
Diagnostic Service Name SID $81 $C0 $85
StartDiagnosticSession 10h x x x
SecurityAccess 27h x
TesterPresent 3Eh x x x
ReadDataByLocalIdentifier 21h x x x
DynamicallyDefineLocalIdentifier 2Ch x x
ReadMemoryByAddress 23h x
ReadDTCInformation 19h x x
ReadDataByIdentifier 22h x x x
InputOutputControlByLocalIdentifier 30h x
StartRoutineByLocalIdentifier 31h x x
StopRoutineByLocalIdentifier 32h x
WriteDataByIdentifier 2Eh x
WriteDataByLocalIdentifier 3Bh x
ClearDiagnosticInformation 14h x x
4.1.1 Service StartDiagnosticSession (10h):
The StartDiagnosticSession service is used to enable different diagnostic sessions in the ECU(s). A diagnostic
session enables a specific set of diagnostic services and/or functionality in the ECU(s).
Request message definition

A_Data Parameter Name Cvt Hex Value Mnem
byte
#1 StartDiagnosticSession Request Service Id M $10 SDS
#2 diagnosticSessionType M $00-$FF DIAGMODE
Positive response message definition

byte
#1 StartDiagnosticSession Response Service Id M $50 SDSPR
#2 diagnosticSessionType M $00-$FF DIAGMODE
Diagnostic sessions are the following:
17 / 120
$81 Default Session

$85 Programming Session
$C0 Assembly Line Testing & After Sales Session
4.1.2 Service SecurityAccess (27h):
The purpose of this service is to provide a mean to access data and/or diagnostic services, which have restricted
access for security, emissions, or safety reasons. Diagnostic services for downloading/uploading routines or data
into an ECU and reading specific memory locations from an ECU are situations where security access may be
required. Improper routines or data downloaded into an ECU could potentially damage the electronics or other
vehicle components or risk the vehicle’s compliance to emission, safety, or security standards. The security
concept uses a seed and key relationship.
A typical example of the use of this service is as follows:
- tool requests the “Seed”
- ECU sends the “Seed”
- tool sends the “Key” (appropriate for the Seed received)
- ECU responds that the “Key” was valid and that it will unlock itself
Request message definition - parameter = requestSeed

byte
#1 SecurityAccess Request Service Id M $27 SA
#2 securityAccessType = requestSeed M $01, $03, $05, LEV_
$07-$FD SAT_RSD
securityAccessDataRecord[] = [ SECACCDR_
#3 parameter#1 U $00-$FF PARA1
: : : : :
#n parameter#m ] U $00-$FF PARAm
Request message definition - parameter = sendKey

byte
#1 SecurityAcces Request Service Id M $27 SA
#2 securityAccessType = sendKey M $02, $04, LEV_
$06, SAT_SK
$08-$FE
securityKey[ ] = [ SECKEY_
#3 key#1 (high byte) M $00-$FF KEY1HB
: : : : :
#n key#m (low byte) ] U $00-$FF KEYmLB
18 / 120

byte
#1 SecurityAccess Response Service Id M $67 SAPR
#2 securityAccessType M $00-$FF SAT_
securitySeed[ ] = [ SECSEED_
#3 seed#1 (high byte) C $00-$FF SEED1HB
: : : : :
#n seed#m (low byte) ] C $00-$FF SEEDmLB
C: The presence of this parameter depends on the securityAccessType parameter. It is mandatory to be present if
the securityAccessType parameter indicates that the tool wants to retrieve the seed from the ECU.
Response message data parameter definition

Definition
securityAccessType
This parameter is an echo of the sub-function parameter from the request message.
securitySeed (high and low bytes)
The seed parameter is a data value sent by the ECU and is used by the tool when calculating the key needed
to access security. The securitySeed data bytes are only present in the response message if the request
message was sent with the securityAccessType parameter set to a value which requests the seed of the ECU.
4.1.3 Service TesterPresent (3Eh):
This service is used to indicate to an ECU that a tool is still connected to the vehicle and that certain diagnostic
services (Timed services) and/or communication that have been previously activated are to remain active.
This service is used to keep the ECU in a diagnostic session other than the defaultSession. This is done by
transmitting the TesterPresent request message in case of the absence of other diagnostic services to prevent the
ECU from automatically returning to the defaultSession.

byte
#1 TesterPresent Request Service Id M $3E TP
#2 responseRequired M $01 RSPREQ

byte
#1 TesterPresent Response Service Id M $7E TPPR
4.1.4 Service ReadDataByLocalIdentifier (21h) :
Description OF Defined Reading Frames:
Identification frame 80h
V.I.N. 81h
19 / 120
MUX network frame 82h
Traceability frame 84h
Reprogramming data F0h - FFh
ReadDataByLocalIdentifier request message

A_Data Byte Parameter Name Hex Value Mnem
#1 ReadDataByLocalIdentifier Request Service Id $21 RDBLID
#2 Record Local Identifier $xx RLOCID

Byte
#1 ReadDataByLocalIdentifier Response Service Id M $61 RDBLIDPR
#2 Record Local Identifier M $xx RLOCID
#3 to n Record Value M $xx .. $xx RECVAL
4.1.5 Service DynamicallyDefineLocalIdentifier (2Ch):
The DynamicallyDefineDataIdentifier service allows the tool to dynamically define in an ECU a data identifier
that can be read via the ReadDataByLocalIdentifier service at a later time.
The intention of this service is to provide the tool with the ability to group one or more data elements into a data
superset that can be requested via the ReadDataByLocalIdentifier / ReadDataByIdentifier /
ReadMemoryByAddress services. The data elements to be grouped together can either be referenced by:
- A source data identifier(LocalID/Identifier), a position and size or,
- A memory address and a memory length.
This service allows greater flexibility in handling data needs of the diagnostic application that extend beyond the
information that can be read via statically defined data identifiers, and can also be used to reduce bandwidth
utilization by avoiding overhead penalty associated with frequent request/response transactions.
IMPORTANT: Defined data Identifier shall be reset via session change / power down.
definitionMode = defineByLocalIdentifier mixed with defineByIdentifier

A_Data Byte Parameter Name Cvt Hex Value Mnem
#1 DynamicallyDefineLocalIdentifier Request Service Id M $2C DLIDDY
#2 DynamicallyDefinedLocalIdentifier M $E0-$EF DDLOCID
#3 definitionMode=[defineByLocalIdentifier]#1 M $01 DEFMODE
#4 PositionInDynamicallyDefinedLocalIdentifier#1 M $xx PIDYDLID
#5 LocalIdentifierDataLength #1 M $xx LIDDL
#6 RecordLocalIdentifier#1 M $xx RLOCID
#7 PositionInRecordLocalIdentifier#1 M $xx PIRLOCID
#8 definitionMode=[defineByLocalIdentifier]#2 C $01 DEFMODE
#9 PositionInDynamicallyDefinedLocalIdentifier#2 C $xx PIDYDLID
#10 LocalIdentifierDataLength #2 C $xx LIDDL
#11 RecordLocalIdentifier#2 C $xx RLOCID
20 / 120
#12 PositionInRecordLocalIdentifier#2 C $xx PIRLOCID

: : : :
#n-5 definitionMode=[defineByIdentifier]#m C $02 DEFMODE
#n-4 PositionInDynamicallyDefinedLocalIdentifier#m C $xx PIDYDLID
#n-3 IdentifierDataLength #m C $xx CIDDL
#n-2 RecordIdentifier#m (Highest Byte) C $xx RCID
#n-1 RecordIdentifier#m (Lowest Byte) C $xx
#n PositionInRecordIdentifier#m C $xx PIRCID
- the parameter positionInDynamicallyDefinedLocalIdentifier shall specify the position in the record

referenced by the parameter dynamicallyDefinedLocalIdentifier.
- the parameter LocalIdentifierDataLength shall specify the number of data bytes referenced by the parameter
recordLocalIdentifier;
- the parameter positionInRecordLocal/Identifier shall specify the starting position in the record stored in the
ECU’s memory.
The request may consist of multiple definitions.
definitionMode=defineByMemoryAddress
#3 definitionMode=[defineByMemoryAddress]#1 M $03 DEFMODE
#4 PositionInDynamicallyDefinedLocalIdentifier#1 M $xx PIDYDLID
#5 MemoryAddressDataLength #1 M $xx MEMADDL
#6 MemoryAddress#1 (Highest Byte) M $xx MEMAHH
#7 MemoryAddress#1 (HL byte) M $xx MEMAHL
#8 MemoryAddress#1 (LH byte) M $xx MEMALH
#9 MemoryAddress#1 (Lowest Byte) M $xx MEMALL
#10 definitionMode=[defineByMemoryAddress]#2 C $03 DEFMODE
#11 PositionInDynamicallyDefinedLocalIdentifier#2 C $xx PIDYDLID
#12 MemoryAddressDataLength #2 C $xx MEMADDL
#13 MemoryAddress#2 (Highest Byte) C $xx MEMAHH
#14 MemoryAddress#2 (HL byte) C $xx MEMAHL
#15 MemoryAddress#2 (LH byte) C $xx MEMALH
#16 MemoryAddress#2 (Lowest Byte) C $xx MEMALL
: : : : :
#n-6 definitionMode=[defineByMemoryAddress]#m C $03 DEFMODE
#n-5 PositionInDynamicallyDefinedLocalIdentifier#m C $xx PIDYDLID
#n-4 MemoryAddressDataLength #m C $xx MEMADDL
#n-3 MemoryAddress#m (Highest Byte) C $xx MEMAHH
#n-2 MemoryAddress#m (HL Byte) C $xx MEMAHL
#n-1 MemoryAddress#m (LH Byte) C $xx MEMALH
21 / 120
#n MemoryAddress#m (Lowest Byte) C $xx MEMALL
- the parameter positionInDynamicallyDefinedLocalIdentifier shall specify the position in the record

referenced by the parameter dynamicallyDefinedLocalIdentifier.
- the parameter MemoryAddressDataLength shall specify the number of data bytes starting at the specified
memoryAddress in the ECU’s memory.
The request may consist of multiple definitions.
DefinitionMode = ClearDynamicallyDefinedLocaldentifier
#3 definitionMode=[ClearDynamicallyDefinedIdentifier] M $04 DEFMODE

definitionMode parameter definition
#1 DynamicallyDefineLocalIdentifier Response Service Id M $6C DLIDDYPR
4.1.6 Service ReadMemoryByAddress (23h):
The ReadMemoryByAddress service allows the tool to request memory data from the ECU via provided starting
address and size of memory to be read.
The ReadMemoryByAddress request message is used to request memory data from the ECU identified by the
parameter memoryAddress and memorySize.
The number of bytes used for the memoryAddress is 4 (DCM 3.4 = 3) and for memorySize is 2.
In case of overlapping memory areas it is possible to use the MA_B1 memoryAddress MSB as a
memoryIdentifier. (e.g. use of internal and external flash memory, EEPROM,…).
This service is highly recommended during development phase to access dynamic data for debugging purposes.
It may also be used for rescue mode along with SecurityAccess service.

#1 ReadMemoryByAddress Request Service Id M $23 RMBA
memoryAddress[ ] = [ MA_
#2 byte#1 (MSB) M $00-$FF B1
: : : : :
#5 byte#4 ] M $00-$FF B4
memorySize[ ] = [ MS_
#6 byte#1 (MSB) M $00-$FF B1
#7 byte#2 ] M $00-$FF B2
22 / 120

#1 ReadMemoryByAddress Response Service Id M $63 RMBAPR
dataRecord[ ] = [ DREC_
#2 data#1 M $00-$FF DATA_1
: : : : :
#n data#m ] U $00-$FF DATA_m
4.1.7 Service ReadDTCInformation (19h):
Described in chapter 5
4.1.8 Service ReadDataByIdentifier (22h):
via 22h service, the ECU gives a package of data associated to an identification number (DID). Some datas are
specific to each supplier injection system; these datas are defined in the commun diagnostic messaging base.
Description OF Defined Reading Datas:
RSA DID 0000h - FCFFh
Supplier DID FD00h - FFFFh

#1 ReadDataByIdentifier Request Service Id M $22 RDBI
dataIdentifier[] #1 = [ DID_
#2 byte#1 (MSB) M $00-$FF B1
#3 byte#2 ] M $00-$FF B2
: : : : :
dataIdentifier[] #m = [ DID_
#n-1 byte#1 (MSB) U $00-$FF B1
#n byte#2 ] U $00-$FF B2
23 / 120

#1 ReadDataByIdentifier Response Service Id M $62 RDBIPR
dataIdentifier[] #1 = [ DID_
#2 byte#1 (MSB) M $00-$FF B1
#3 byte#2 ] M $00-$FF B2
dataRecord[] #1 = [ DREC_
: : : : :
#(k-1)+4 data#k ] U $00-$FF DATA_m
: : : : :
dataIdentifier[] #m = [ DID_
#n-(o-1)-2 byte#1 (MSB) U $00-$FF B1
#n-(o-1)-1 byte#2 ] U $00-$FF B2
dataRecord[] #m = [ DREC_
#n-(o-1) data#1 U $00-$FF DATA_1
: : : : :
#n data#o ] U $00-$FF DATA_k
4.1.9 Service InputOutputControlByLocalIdentifier (30h):
4.1.10 Service StartRoutineByLocalIdentifier (31h):
4.1.11 Service StopRoutineByLocalIdentifier (32h):
4.1.12 Service WriteDataByIdentifier (2Eh):
The service WriteDataByIdentifier permits users to write a data in the non volatil memory of the ECU.
The data is identified by its identifier (DID). The ECU authorizes or not the writing depending of some
authorization conditions (engine speed, engine state, vehicle speed, data writeable or not, …).
Description OF Defined Writing Datas:
RSA DID 0000h - FCFFh
Supplier DID FD00h - FFFFh
24 / 120

#1 WriteDataByIdentifier Request Service Id M $2E WDBI
dataIdentifier[] = [ DID_
#2 byte#1 (MSB) M $00-$FF B1
#3 byte#2 ] M $00-$FF B2
dataRecord[] = [ DREC_
: : : : :
#m+3 data#m ] U $00-$FF DATA_m

#1 WriteDataByIdentifier Response Service Id M $6E WDBIPR
dataIdentifier[] = [ DID_
#2 byte#1 (MSB) M $00-$FF B1
#3 byte#2 ] M $00-$FF B2
4.1.13 Service WriteDataByLocalIdentifier (3Bh):
This service is used to :

- Write on ECU memory the data relevant to Engineering, After-Sales, Plant Process (example: date) or
Quality Department (or other).
- select a law, a calibration, a threshold, a coefficient or a vehicle assembly line configuration.
- correct certain parameters (example: injection idle rate setting) within the limits fully controlled by the ECU.
It might be necessary to take certain precautions regarding vehicle production and last After-Sales operation
dates (e.g. prohibit the writing of the plant vehicle production date in the After-Sales network). It is the
responsibility of the function manager to specify this to the ECU supplier.
Depending on the Local ID, data may be written either on volatile memory or on non-volatile memory. The
choice will be done regarding diagnostic communication performance.
This service shall not be used to reset the memory including the stored fault codes.
Description OF Defined Writing Datas:
V.I.N. 81h

A_Data byte Parameter name Cvt Hex Value Mnem.
#1 WriteDataByLocalIdentifier request Service Id M $3B WDBLID
#2 RecordLocalIdentifier M $xx RECLID
#3 to n RecordValue = values to be written : To be defined by U $xx RECVAL
the function manager
25 / 120
A_Data byte Parameter Name Cvt Hex Mnem

Value
#1 WriteDataByLocalIdentifier Response Service Id M $7B WDBLIDPR
#2 RecordLocalIdentifier M $xx RECLID
4.1.14 Service ClearDiagnosticInformation(14h): Valeurs initialisées
Requête 14FFFFFFh – All failures group

Description OF Clear All Failures Group:
ClearDiagnosticInformation FFFFFFh

Value
#1 ClearDiagnosticInformation Request Service Id M $14 CDTCI
groupOfDTC[] = [ GODTC_
#2 groupOfDTCHighByte M $00-$FF HB
#3 groupOfDTCMiddleByte M $00-$FF MB
#4 groupOfDTCLowByte ] M $00-$FF LB

Value
#1 ClearDiagnosticInformation Response Service Id M $54 CDTCIPR
All defaults and associated snapshots are erased by this request.
26 / 120
4.2 System conditions restricting the execution of a service
4.2.1 Service StartDiagnosticSession (10h):
There is no ECU or Engine current operating condition that do not allow the execution of the request.
4.2.2 Service SecurityAccess (27h):
This request can be executed only when the following conditions are all filled:
• the ECU must be in locked state
• the criteria for the request SecurityAccess must be met
4.2.3 Service TesterPresent (3Eh):
4.2.4 Service ReadDataByLocalIdentifier (21h):
• Antitheft not active
• Not in power-latch phase (key ON)
• Engine stopped or running
4.2.5 Service DynamicallyDefineLocalIdentifier (2Ch):
This request can be executed only when the following condition is filled:
4.2.6 Service ReadMemoryByAddress (23h):
4.2.7 Service ReadDTCInformation (19h):
4.2.8 Service ReadDataByIdentifier (22h):
27 / 120

• Engine stopped or running
• Requested DID supported by the ECU
• Only one DID in a frame
4.2.9 Service InputOutputControlByLocalIdentifier (30h):
• Not in power-latch phase (key ON) (for output not controllables in the power-latch Phase)
• Engine stopped (vehicle speed = 0 Km/h)
4.2.10 Service StartRoutineByLocalIdentifier ( 31h):
Conditions depends on the routine used: please see chapter 6
4.2.11 Service StopRoutineByLocalIdentifier ( 32h):
4.2.12 Service WriteDataByIdentifier (2Eh):
• Engine stopped
• Requested DID supported by the ECU
• Only one DID in a frame
4.2.13 Service WriteDataByLocalIdentifier (3Bh):

• Engine stopped
• No Non-volatile Memory Failure
• VIN is virgin (for LID $3B81)
28 / 120
4.2.14 Service ClearDiagnosticInformation(14h):
This request can be executed only when the following conditions are all filled :
• Not in power-latch phase (+key ON)
• Engine stopped
________________ End of DED_4.0.0.0.0.0.0_000_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.1).doc ______________
29 / 120
______________ Begin of DED_4.3.0.0.0.0.0_000_3XXXX0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.0).doc ______________
4.3 Reference to the DDT database

Please use the DDT database corresponding to V42 ECU with 2A software.
________________ End of DED_4.3.0.0.0.0.0_000_3XXXX0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.0).doc ______________
30 / 120
______________ Begin of DED_5.0.0.0.0.0.0_000_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX2XXXXXXX(1.1).doc ______________
5 FAULT MANAGER
Diagnoses are designed to detect any fault of a component or a system which affect its functionality. There are
two diagnostic types in the engine control unit:
- electrical diagnoses of the different sensors and actuators (continuity) ;
- functional diagnoses of vehicle functions (CC/SL...) and systems (catalyst, secondary air, misfire...).
Each diagnosis consists in one or several tests. After its realization it calls the Failure Manager (FM) with the
following information:
- its identifier (Nxx_ind)
- elementary decision (detected failure Vbx_df)
- increment value (Cxx_dfinc)
- decrement value (Cxx_dfdec)
The FM filters these elementary results and produces several types of confirmed failures states for limp home
and control strategies, and also after-sale using.
5.1 Confirmation and storage

Each diagnosis has its own confirmation counter (Vxx_dfctr) which is respectively incremented (by Cxx_dfinc)
or decremented (by Cxx_dfdec) if the FM is called with an elementary decision bad (Vbx_df=true) or good
(Vbx_df=false).
A failure is confirmed as present if its confirmation counter reaches its maximum value FFFF. At that time all
the confirmed states are set to 1 and the failure is memorized:
- confirmed (Vbx_cf)
- confirmed saved at the key transition (Sbx_cf, bit0 of DTCStatus)
- confirmed hold until the power latched (Vbx_clf, bit1 of DTCStatus NonOBD relevant)
- memorized (Sbx_mf, bit5 of DTCStatus)
At the end of the cycle and after the power latched, the memorized and the saved confirmed flags (Sbx_mf,
Sbx_cf) are stored into non volatile memory.
5.2 Diagnostic completion status
The FM produces for each diagnosis two flags that indicate its completion:
- complete this monitoring cycle (Vbx_rdn, bit6 of DTCStatus)
- complete since last clear (Sbx_rdn, bit4 of DTCStatus)
At each FM call with the same elementary decision (no edge) a specific counter is incremented by Cxx_dfinc.
The previous flags are set to 0 when the counter reaches its maximum value FFFF. If there is an edge between
two elementary decisions (Vbx_df), the counter is reset to Cxx_dfinc.
At the end of the cycle and after the power latched, the complete since last clear flag is stored into non volatile
memory.
The initial value of the flags is 1.
5.3 Disappearance
Some failures are not definitive and can disappear. The failures are confirmed absent (ie the confirmed states
Vbx_cf & Sbx_cf are set to 0 - bit0 of DTCStatus) if the 2 following conditions are met:
- confirmation counter reaches the value 0
31 / 120
- readiness flag (Vbx_rdn, bit6 of DTCStatus) indicates that the diagnosis is complete
5.4 Context
The FM stores several context data for a defined number (Cxx_dyn_thd+1) of memorized failures. If this
dynamical memory pool of failure is full, occurrences of new failures make rearrangement with the following
priority rules (from highest to lowest):
- failure provokes MIL illumination
- EOBD failure
- failure provokes WAL 2 illumination
- failure provokes WAL 1 illumination
- other failure
When there are several candidates to be overwritten, the FM chooses the first which have disappeared if it exists
otherwise the oldest one which has appeared.
5.4.1 Manufacturer Freeze Frames

At the confirmation of a failure (Sbx_cf 0→1, bit0 of DTCStatus) the FM stores a set of context data. 5 are
common to all failures:
- engine coolant temperature
- engine speed
- vehicle speed
- estimated effective engine torque
- battery voltage
5 other spaces are available to store specific context data which are interesting to link to the failure for repair.
The choice of the data are realized by the calibration Ctx_ffm_did_’device’ (shared by device) which contains the
data identifiers (DID) of the Common Diagnostic Data Library.
There are 3 sets of context data (accessible by service $19-04 of ISO 14229):
- first occurrence ($01)
- minimum values ($02)
- maximum values ($03)
At the first occurrence the current value of data are stored in the three sets. Then at each reoccurrence (Sbx_cf
0→1, bit0 of DTCStatus), the minimum and maximum values are refreshed in associated sets of data.
The three sets of context data are stored in non volatile memory at the end of the cycle and after the power
latched.
For diagnoses which need more context data for discrimination or re-activating of failures, another snapshot can
be saved at the confirmation of failure (managing with the same priority rules). If it is used by a DTC it is
accessible by service $19-04 os ISO 14229 with the SnapshotRecordNumber $04.
5.4.2 Last occurrence mileage $80
The FM stores (in non volatile memory at the end of the cycle and after the power latched) the total distance
travelled by the vehicle at the each occurrence of a failure (Sbx_cf 0→1, bit0 of DTCStatus).
The data is accessible by service $19-06: DataRecordNumber=$80.
Initial value: 0.
5.4.3 Occurrence counter $84
32 / 120
The number of failure occurrences, Sbx_cf 0→1 (bit0 of DTCStatus) edge, is stored in non volatile memory at
the end of the cycle and after the power latched.
Initial value: 0.
5.4.4 Last disappeared mileage $85
travelled by the vehicle at each disappearance of a failure (Sbx_cf 1→0, bit0 of DTCStatus).
The data is reinitialized at each occurrence (Sbx_cf 0→1, bit0 of DTCStatus) and is accessible by service $19-06:
DataRecordNumber=$85.
Initial value: 16777215.
5.4.5 Distance travelled failure present $86
The FM calculates and stores (in non volatile memory at the end of the cycle and after the power latched) the
distance travelled by the vehicle during the presence of a failure (during Sbx_cf=1, bit0 of DTCStatus) throw all
occurrences.
Initial value: 0.
5.4.6 First occurrence mileage $87
travelled by the vehicle at the first occurrence of a failure (Sbx_mf 0→1, bit5 of DTCStatus).
Initial value: 0.
5.5 EOBD fault management
Furthermore the general management, the EOBD failures (emission relative diagnoses and their surveillance)
have a specific management defined by regulations. As the context data, these information are stored and
managed for defined number of memorized failures (Cxx_dyn_thd+1) with the same priority rules.
A driving cycle begins with the autonomous state reaching by the engine and finishes with the end of the power
latched or with a key on event (engine stopped).
A warm up cycle is detected if the engine coolant temperature is above Cxx_wup_thd_tco (generally 70°C) and
has risen by at least Cxx_wup_dif_thd_tco (generally 22°C) from engine starting one.
5.5.1 EOBD pending failure: temporary fault
If a failure is confirmed and if the engine is in autonomous state (driving cycle), a pending flag (Stx_pfo) is
stored and hold until the system finishes a full driving cycle with the failure no longer present (Sbx_cf=0).
The data is reported to the Scantool via service $07 of ISO 15031-5.
5.5.2 EOBD confirmed failure
If a pending failure occurs during a defined number (per failure) of consecutive driving cycles
(Cxx_obd_dc_’device’_’faulttype’, generally 3 DC), a confirmed flag (Stx_mfo) is stored and hold until the
system realises a defined number (Cxx_obd_wup_thd, common to all failures, minimum 40) of consecutives
warm up cycles with the default no longer present and the MIL extinguished.
33 / 120
The data is reported to the Scantool via service $03 of ISO 15031-5.
5.5.3 EOBD freeze frame: context frame
As the manufacturer freeze frame, a set of context data is stored at the first occurrence of an EOBD failure
(Sbx_cf 0→1, bit0 of DTCStatus). But a simple set is reported to the Scantool for one EOBD failure with the
following priority rules (from highest to lowest):
- oldest misfire confirmed failure
- oldest EOBD MIL illuminating confirmed failure
- oldest EOBD confirmed failure
- oldest pending failure
The EOBD freeze frame contains the following data:
- for spark ignition engine:
- load value
- coolant temperature
- engine speed
- vehicle speed
- intake manifold absolute pressure
- fuel system status
- short term fuel trim
- long term fuel trim
- distance travelled since last clear
- for compression ignition engine:
- load value
- coolant temperature
- engine speed
- vehicle speed
- intake manifold absolute pressure
- air flow rate from mass air flow sensor
- fuel rail pressure
- intake air temperature
- distance travelled since last clear
5.5.4 Distance covered since the last Clear Diagnostic Information
The distance travelled by the vehicle since the last clear request is computed by the FM and is reported to the
Scantool via service $01 of ISO 15031-5.
5.5.5 Distance covered with the MIL lit
The distance travelled by the vehicle with the MIL illuminated is computed by the FM and is reported to the
Scantool via service $01 of ISO 15031-5.
5.6 Warning indicator lighting management

5.6.1 Severity warning light 1&2 (WAL 1&2)
The warning lamps are illuminated with the same behaviour as the save confirmed status (Sbx_cf, bit0 of
DTCStatus) of associated failures:
34 / 120
- Sbx_cf=ON → illuminated
- Sbx_cf=OFF → extinguished
5.6.2 MIL warning light
The MIL blinks when destructive catalyst misfire is detected in order to prevent the user that he has to slow
down as soon as possible:
- destructive catalyst misfire failure is detected : MIL is blinking
- no destructive catalyst misfire failure detected : MIL is not blinking
For all the failures which request a fixed illumination of the MIL, the behaviour is:
- illumination of the MIL on associated EOBD confirmed failure rising
- extinction after un common defined number of driving cycle (Cxx_obd_dc_off, minimum 3) with the
failure no longer present
5.7 DTC & Status
Each failure is identified by a unique 3 bytes Diagnostic Trouble Code (ISO 15031-6). The engine control unit is
compliant with ISO 14229 protocol of communication. The $19 service can report the DTC, their status and their
context data for after-sale needs.
On the other hand, the DTC reported to the Scantool is coded on 2 bytes.
DTC High Byte DTC Middle Byte DTC Low Byte

$1 $2 $3 $4 $0 $0
0 0 0 1 0 0 1 0 0 0 1 1 0 1 0 0 0 1 0 1 0 1 1 0
P 1 2 3 4 5 6
Cxx_dtc_hmb_xxx Cxx_dtc_lb_xxx
Device Fault type
Example of 3-bytes Diagnostic Trouble Code structure

Bit EOBD instance No EOBD instance
0 TestFailed – Sbx_cf
1 TestFailedThisDrivingCycle TestFailedThisMonitoringCycle – Vbx_clf
2 PendingDTC – Stx_pfo 0
3 ConfirmedDTC – Stx_mfo ContextDataAvailable
4 TestNotCompletedSinceLastlear – Sbx_rdn
5 TestFailedSinceLastClear – Sbx_mf
6 TestNotCompletedThisMonitoringCycle – Vbx_rdn
7 LampIlluminationRequest (MIL/WAL1/WAL2)
RSA DTC generic status byte implementation
5.8 Clear diagnostic information: deleting faults
35 / 120
This request is effective engine off only and key on. Consequences on the previous described data:
- All confirmed/memorized states and confirmation counters of all failures are set to 0: Vbx_cf, Sbx_cf,
Vbx_clf, Sbx_mf, Vxx_dfctr.
- All context data, EOBD states/freeze frames of dynamic memory pool are set to 0 except Last
Disappeared Mileage which are set to maximum value (FFFF).
- All completion statuses are set to ON (not completed).
Lamp illumination requests are set to 0 (no request).
In consequence all DTCStatuses are set to $50 (not tested).
36 / 120
5.9 Graphs
DTCStatus & Counters
NOBD/WAL2 failure
ON
Key OFF
ON
Engine State OFF

true
Vbx df false
max
Vxx dfctr min

true
Vbx cf false
true
← → Increment filter
← → Decrement filter ← → Readiness filter

bit 0Sbx cf false
true
bit 1Vbx clf false
Cxx obd dc of f
Cxx obd dc
Stx obd clfctr

true
bit 2 false
true
bit 3 false
max
↑ Edge filter
Vxx rdn min
true
bit 4Sbx rdn false

true
bit 5Sbx mf false

true
bit 6Vbx rdn false

true
WAL 2 WAL 2 WAL 2

← → ← → ← →
bit 7Lamp false
Time
37 / 120
DTCStatus & Counters

OBD/WAL1 failure
ON
Key OFF
ON
Engine State OFF

true
Vbx df false
max
Vxx dfctr min

true
Vbx cf false
true
← → Increment filter
← → Decrement filter ← → Readiness filter

bit 0Sbx cf false
true
bit 1Vtx fail dc false
Cxx obd dc of f
Cxx obd dc
Stx obd clfctr

true
bit 2Stx pfo false

true
n WUP detected →
bit 3Stx mfo false
max
↑ Edge filter
Vxx rdn min
true
bit 4Sbx rdn false

true
bit 5Sbx mf false

true
bit 6Vbx rdn false

true
WAL 1 WAL 1 WAL 1 + MIL MIL WAL 1

← → ← →← →← → ← →
false
Time
38 / 120
Manufacturer Freeze Frames & ExtendedData

OBD/WAL1 failure
bit 0Sbx cf
150
Tco
FF$01Tco
Coolant temperature (°C)
FF$02Tco Min
100 FF$03Tco Max
50
0
0 20 40 60 80 100 120 140 160
15
Vb
FF$01Vb
FF$02Vb Min
Battery voltage (V)
10 FF$03Vb Max
0
0 20 40 60 80 100 120 140 160
bit 2Stx pfo
bit 3Stx mfo
bit 7Lamp
$84Occ ctr
200 Distance
$80Km Fail
$85Km Pass
150
Distance (km)
$86Dist Fail
100
50
0
0 20 40 60 80 100 120 140 160
Time
________________ End of DED_5.0.0.0.0.0.0_000_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX2XXXXXXX(1.1).doc ______________
______________ Begin of DED_6.0.0.0.0.0.0_000_3K401030100011000012000000000000000002001020000000(2.0).doc ______________
39 / 120
6 Using diagnostic resources
6.1 Diagnostic trouble codes

______________ Begin of FID_Enveloppe_2A44_v03.xls__0010h__.doc ______________
6.1.1 P0010 – Intake Camshaft Position Solenoid Valve and/or Actuator
DTC 0010h
Intake Camshaft Position Solenoid Valve and/or Actuator
Fault
Description ABC Type
Type
13h Circuit Open
11h Circuit Short to Ground
12h Circuit Short to Battery
Detection Conditions for Bit 4 (readiness)
13h [At key-on OR when VVTC command is ON] AND 6 V < battery voltage
Detection Conditions for Bit 0 (test failed) Detection timing Resorption Timing
13h Hardware detection of VVT command Short Circuit to Ground 1000 ms 100 ms
11h Hardware detection of VVT command Short Circuit to Ground 1000 ms 2000 ms
12h Hardware detection of VVT command Short Circuit to Battery - ms - ms
Specific Snapshot
$2007 - Oil temperature - engine
$2010 - Engine status
$2031 - Intake camshaft phaser position
$2033 - Intake camshaft phaser PWM command
$2030 - Intake camshaft phaser position setpoint
________________ End of FID_Enveloppe_2A44_v03.xls__0010h__.doc ______________
40 / 120
6.1.2 P0011 – Camshaft Position Solenoid Valve and/or Actuator Control

Function
DTC 0011h
Camshaft Position Solenoid Valve and/or Actuator Control Function
Fault
Type
78h Incorrectly Adjusted or Aligned Component Detected
77h Unable to Move the Component to the Commanded Position
92h Component Performance Outside its Expected Range
78h learning of the camshaft wheel enabled
77h Engine speed > 2400 rpm AND battery voltage > 11 V AND oil temp > 30 °C AND no DTC present linked to VVTC actuator
92h Engine speed > 2400 rpm AND battery voltage > 11 V AND oil temp > 30 °C AND no DTC present linked to VVTC actuator
78h Abnormal angular position of an active edge of the camshaft wheel - ms - ms
[VVTC regulation error over max threshold OR abnormal saturation of
77h - ms - ms
VVTC actuator command] near low trust position
[VVTC regulation error over max threshold OR abnormal saturation of
92h 1500 ms 4500 ms
VVTC actuator command] NOT near low trust position
Specific Snapshot
$2007 - Oil temperature - engine
$2033 - Intake camshaft phaser PWM command
$2030 - Intake camshaft phaser position setpoint
41 / 120
6.1.3 P0016 – Crankshaft Position – Intake Camshaft Position Correlation
DTC 0016h
Crankshaft Position – Intake Camshaft Position Correlation
Fault
Type
62h Two (or More) Input Parameters compared for Plausibility
62h Engine running AND no DTC present linked to camshaft and crankshaft sensors
Camshaft reference position is outside of the designed range (relative to the
62h < 1s ms < 1s ms
engine position from crankshaft)
Specific Snapshot
$240B - Intake manifold pressure
$2162 - Counter of loose of crankshaft synchronization
$2014 - Camshaft/crankshaft synchronization state
$2016 - Crankshaft synchronization state
42 / 120
6.1.4 P0095 – Intake Air Temperature Downstream

Turbocharger/Supercharger Sensor
DTC 0095h
Intake Air Temperature Downstream Turbocharger/Supercharger Sensor
Fault
Type
17h Voltage Above a Specified Range
16h Voltage Below a Specified Range
17h Always
16h Always
17h Air temperature sensor voltage above maximum threshold 1000 ms 2000 ms
16h Air temperature sensor voltage below minimum threshold 1000 ms 2000 ms
Specific Snapshot
$FD83 - Intake manifold temperature sensor voltage
$243F - Intake manifold temperature
$2401 - Boost pressure
$2422 - Amount of air pumped into cylinder
-
43 / 120
6.1.5 P0106 – Manifold Absolute Pressure Function
DTC 0106h
Manifold Absolute Pressure Function
Fault
Type
64h Plausibility Failure
1Ch Voltage Outside the Expected Range
Engine speed > 608 rpm AND DTC 0641h, 060Ah, 061Ah, 0560h, 0606h, 2100h, 0638h NOT present AND (DTC 0106h
64h
present OR DTC 095h, 0115h, 0651h, 0443h NOT present)
Stopped engine: DTC 0651h not present Running engine: Engine speed > 608 rpm AND DTC 0641h, 060Ah, 061Ah, 0560h,
1Ch
0606h, 2100h, 0638h not present
64h Abnormal manifold pressure value (compared to modelized value). 400 ms 2550 ms
Stopped engine: Manifold pressure NOT between 200 hPa & 20000 hPa
Running engine : (Manifold pressure < 1030 hPa AND Inlet throttle relative
1Ch 500 ms 1000 ms
position > 0 % Vsens) OR (Manifold pressure > Cxx_sens_map_run_h_thd
AND Inlet throttle relative position < 10 % Vsens)
Specific Snapshot
$FD81 - Intake manifold pressure sensor voltage
$24D7 - Manifold pressure value from model
44 / 120
6.1.6 P0115 – Engine Coolant Temperature Sensor
DTC 0115h
Engine Coolant Temperature Sensor
Fault
Type
2Fh Signal momentarily Implausible or Discontinuous
17h Always
16h Always
2Fh No DTC present linked to coolant temperature sensor
17h Coolant temperature sensor voltage signal above maximum threshold 1000 ms 4000 ms
16h Coolant temperature sensor voltage signal below minimun threshold 1000 ms 4000 ms
2Fh Abnormal coolant temperature gradient 8000 ms 80000 ms
Specific Snapshot
$FD8B - Engine coolant temperature sensor voltage
$2C04 - Current gear engaged
$204A - Motor-fans requests
45 / 120
6.1.7 P0120 – Intake Throttle Position Sensor
DTC 0120h
Intake Throttle Position Sensor
Fault
Type
29h Signal Not Plausible
29h DTC 0641h not present
29h Unplausible IT sensor 1 position 190 ms 4680 ms
Specific Snapshot
$2415 - Throttle valve position - track 1
$2021 - Sensors supply voltage 1
-
-
46 / 120
6.1.8 P0130 – O2 Sensor - Upstream
DTC 0130h
O2 Sensor - Upstream
Fault
Type
13h Circuit Open
09h No Component Specific SubType
Engine autonomous AND Upstream lambda sensor is hot AND Upstream lambda sensor output voltage between 275 mV &
13h
445 mV
11h Injection activated AND no DTC present linked to boost pressure, ambient pressure, coolant temperature or air temperature
12h [Engine running AND DTC 0135h not present AND time after start > 3min] during 0 s
Coolant temp > 75 °C AND engine running time > 820 s AND 1900 rpm < engine speed < 4000 rpm AND no variation of
09h
engine speed AND no DTC present
13h Activation conditions true during 0 s 5000 ms 20 ms
11h Upstream lambda sensor output voltage < 20 mV 10000 ms 20 ms
12h Upstream lambda sensor output voltage > 1395 mV 10 ms 20 ms ms
09h Abnormal duration of min period duration of lambda sensor 20000 ms 20000 ms
Specific Snapshot
$2449 - Catalyst exhaust gas upstream oxygen sensor voltage
$244B - Catalyst exhaust gas upstream oxygen resistance heater PWM command
47 / 120
6.1.9 P0135 – O2 Sensor Heater - Upstream
DTC 0135h
O2 Sensor Heater - Upstream
Fault
Type
13h Circuit Open
13h APC AND Component not activated since 1,3ms
12h APC AND Component activated
13h Hardware detection of open circuit 2000 ms 4000 ms
11h Hardware detection of short circuit to battery 2000 ms 4000 ms
12h Hardware detection 2000 ms 4000 ms
Specific Snapshot
$244B - Catalyst exhaust gas upstream oxygen resistance heater PWM command
$24C4 - Time expected to switch on the heating of the upstream sensor
$284E - Richness regulation status
48 / 120
6.1.10 P0136 – O2 Sensor - Downstream
DTC 0136h
O2 Sensor - Downstream
Fault
Type
13h Circuit Open
Richness double loop activated AND no DTC present linked to boost pressure, ambient pressure, coolant temperature or air
11h
temperature
[Downstream sensor heating activated almost one time during the current driving cycle (engine running time > 5min at idle
12h
speed) AND engine autonomous AND DTC 0141h not present] during 5 s
[Downstream sensor heating activated almost one time during the current driving cycle (engine running time > 5min at idle
13h
speed) AND engine autonomous AND DTC 0141h not present] during 5 s
11h Rear Oxygen Sensor signal < 20 mV 30000 ms 20 ms
12h Rear Oxygen Sensor signal > 1395 mV 10 ms 20 ms
13h Lambda sensor signal > 275 mV after more than 10s of injection cut-off 1000 ms 10 ms
Specific Snapshot
$244A - Catalyst exhaust gas downstream oxygen sensor voltage
$244C - Catalyst exhaust gas downstream oxygen resistance heater PWM command
-
49 / 120
6.1.11 P0141 – O2 Sensor Heater - Downstream
DTC 0141h
O2 Sensor Heater - Downstream
Fault
Type
13h Circuit Open
12h APC AND Component activated since 80ms
Specific Snapshot
$244C - Catalyst exhaust gas downstream oxygen resistance heater PWM command
$244A - Catalyst exhaust gas downstream oxygen sensor voltage
$2506 - Progress in the heater strategy
$284E - Richness regulation status
50 / 120
6.1.12 P0170 – Fuel Trim
DTC 0170h
Fuel Trim
Fault
Type
09h 950 rpm < Engine speed < 6000 rpm AND engine running for more than 0 s AND no DTC present
09h Mean richness deviation exceeding threshold 10 ms ms 10 ms ms
Specific Snapshot
$2873 - Corrected average ALFACL for memorized fuel system diagnostic
$2850 - Richness regulation correction
$2874 - Misfire counter
-
-
51 / 120
6.1.13 P0201 – Injector Circuit – Cylinder 1
DTC 0201h
Injector Circuit – Cylinder 1
Fault
Type
13h Circuit Open
13h Engine running and Component not activated since 1,3ms
12h Engine running and Component activated since 80ms
11h Hardware detection of short circuit to ground 1000 ms 2000 ms
Specific Snapshot
$2851 - Richness adaptation factor
$2852 - Richness adaptation offset
-
-
-
52 / 120
DTC 0202h
Fault
Type
13h Circuit Open
Specific Snapshot
-
-
-
53 / 120
DTC 0203h
Fault
Type
13h Circuit Open
Specific Snapshot
-
-
-
54 / 120
DTC 0204h
Fault
Type
13h Circuit Open
Specific Snapshot
-
-
-
55 / 120
6.1.17 P0217 – Engine Coolant Temperature
DTC 0217h
Engine Coolant Temperature
Fault
Type
98h Temperature too High
98h Always
98h Coolant temperature > 118°C 1000 ms 1000 ms
Specific Snapshot
$2C04 - Current gear engaged
-
-
56 / 120
6.1.18 P0220 – Intake Throttle Position Sensor - Track 2
DTC 0220h
Intake Throttle Position Sensor - Track 2
Fault
Type
29h Unplausible IT sensor 2 position 190 ms 4680 ms
Specific Snapshot
-
-
57 / 120
6.1.19 P0225 – Accelerator Pedal Position Sensor - Track 1
DTC 0225h
Accelerator Pedal Position Sensor - Track 1
Fault
Type
accelerator pedal sensor 1 output voltage > 0,9648093842 Uref ratio AND
17h 250 ms 1000 ms
DTC 2120h not present
accelerator pedal sensor 1 output voltage < 0,07331378299 Uref ratio AND
16h 250 ms 1000 ms
Specific Snapshot
$200C - Accelerator pedal voltage - track 2
$200B - Accelerator pedal voltage - track 1
-
58 / 120
6.1.20 P0226 – Accelerator Pedal Position Sensor
DTC 0226h
Accelerator Pedal Position Sensor
Fault
Type
F3h Multiple Failure
F1h Safety Case 1
F2h Safety Case 2
[No accelerator pedal track 1 or 2 signal detected failure (high or low) AND no failure on acc. pedal track 1 or 2 power supply]
64h
OR DTC 0226h present
F3h Always
- accelerator pedal variation < 0,3000977517 Uref ratio/s - accel pedal position > 0,2003910068 Uref ratio - vehicle speed > 0
km/h - no accelerator pedal detected failure, - no AYC, ASR or MSR current request if configuration bit is not set, - accelerator
F1h
pedal sensor information not invalid. - n > 608 rpm. - no braking setpoint from Adaptive Cruise Control system (only for
applications with ACC) if configuration bit is not set.
F2h DTC 0226h status F1h present
64h Ratio between accelerator pedal track 1 & 2 position < [6%..8%] Uref ratio 400 ms 1600 ms
Accelerator pedal track 1 & 2 signal detected failure (high or low) OR
F3h (failure on one Acc. pedal track signal AND failure on the other acc. pedal 250 ms 10000 ms
track power supply)
F1h No pedal position variation 1200 ms 20 ms
F2h No pedal variation 30000 ms ms
Specific Snapshot
$2036 - Counter of inconsistencies between accelerator pedal and brake
59 / 120
6.1.21 P0300 – Random/Multiple Cylinder Misfire Detected
DTC 0300h
Random/Multiple Cylinder Misfire Detected
Fault
Type
F8h Catalyst Destructive
66h More Transitions than a Specified Number
F8h 550 rpm < engine speed < 4500 rpm AND coolant temperature > -10 ºC AND no DTC present linked to injection system
66h 550 rpm < engine speed < 4500 rpm AND coolant temperature > -10 ºC AND no DTC present linked to injection system
F8h Abnormal number of torque diminutions BUT no cylinder identified 20s ms 20s ms
66h Abnormal torque diminution BUT no cylinder identified 10 min ms 10 min ms
Specific Snapshot
$2841 - Misfire counter - cylinder 1
$281B - Fuel low level
60 / 120
6.1.22 P0301 – Cylinder 1 Misfire Detected
DTC 0301h
Cylinder 1 Misfire Detected
Fault
Type
F8h Abnormal number of torque diminutions on cylinder 1 20s ms 20s ms
66h Abnormal torque diminution on cylinder 1 10 min ms 10 min ms
Specific Snapshot
61 / 120
DTC 0302h
Fault
Type
Specific Snapshot
62 / 120
DTC 0303h
Fault
Type
Specific Snapshot
63 / 120
DTC 0304h
Fault
Type
Specific Snapshot
64 / 120
6.1.26 P0313 – Misfire Detected with Low Fuel
DTC 0313h
Misfire Detected with Low Fuel
Fault
Type
Abnormal number of torque diminutions on one ore more cylinders with low
F8h 20s ms 20s ms
fuel level in tank
Abnormal torque diminution on one or more cylinders with low fuel level in
66h 10 min ms 10 min ms
tank
Specific Snapshot
65 / 120
6.1.27 P0314 – Single Cylinder Misfire (Cylinder not Specified)
DTC 0314h
Single Cylinder Misfire (Cylinder not Specified)
Fault
Type
Abnormal number of torque diminutions during 400 TDC on one or more
F8h 20000 ms 20000 ms
cylinders
66h Abnormal torque diminution on one or more cylinders 10 min ms 10 min ms
Specific Snapshot
66 / 120
6.1.28 P0315 – Crankshaft Position System Variation Not Learned
DTC 0315h
Crankshaft Position System Variation Not Learned
Fault
Type
09h After injection cut-off between 3000 Rpm & 3500 Rpm, during 100 TDC (for crankshaft position system variation learning)
09h Abnormal value for crankshaft target variation learning 100 TDC ms 100 TDC ms
Specific Snapshot
$2156 - TLZ - Last achieved adaptive value
$215D - TLZ - TLZ adaptive correction
-
-
-
67 / 120
6.1.29 P0325 – Knock Sensor
DTC 0325h
Knock Sensor
Fault
Type
1Ch Voltage Outside the Expected Range
1Ch Engine running and Coolant temperature > 70 °C and engine speed > 8000 RPM
1Ch Abnormal Knock sensor signal (too low) 2621,4 ms 2621,4 ms
Specific Snapshot
$284D - Mean knock noise
$2847 - Knock counter detection - cylinder 1
$284A - Knock counter detection - cylinder 4
68 / 120
6.1.30 P0335 – Crankshaft Position Sensor
DTC 0335h
Crankshaft Position Sensor
Fault
Type
62h Two (or More) Input Parameters compared for Plausibility
31h Signal Not Detected
25h Improper Signal Shape (plot of Amplitude with Respect to Time)
62h Engine speed > Threshold AND no DTC present linked to camshaft and crankshaft sensors
31h Engine running AND no DTC present crankshaft sensors
25h Engine running
At next driving cycle
64h Reference gap not detected at correct position +/- 2 teeth < 1s ms
ms
62h Abnormal number of teeth per crankshaft revolution < 1s ms
ms
31h Crankshaft sensor signal is missing < 1s ms
ms
25h No camshaft signal although engine is running 5 récurrences ms 30 récurrences ms
Specific Snapshot
$2161 - Crankshaft signal
69 / 120
6.1.31 P0340 – Intake Camshaft Position Sensor
DTC 0340h
Intake Camshaft Position Sensor
Fault
Type
31h Signal Not Detected
64h Unexpected camshaft pulse < 1s ms < 1s ms
31h Camshaft signal not detected engine rotations ms engine rotations ms
Specific Snapshot
70 / 120
6.1.32 P0420 – Catalyst System
DTC 0420h
Catalyst System
Fault
Type
1900 rpm < Engine speed < 4000 rpm AND 25 kg/h< Mass air flow < 130 kg/h AND average mass air flow variation < 20 kg/h
09h AND coolant temp > 75 °C AND Gear ratio >= 4 wu AND time after engine start > 980 s AND DTC 0443h, 0335h, 1351h,
1352h, 0201h, 0202h, 0203h, 0204h, 0130h, 0135h ,0136h, 0095h, 0115h, 0170h, 030xh not present
Difference between raw and filtered lambda sensor signals anormaly high
09h 25000 ms 25000 ms
when submitted to richness pulses
Specific Snapshot
$2873 - Corrected average ALFACL for memorized fuel system diagnostic
-
-
-
71 / 120
6.1.33 P0443 – Canister Purge Valve
DTC 0443h
Canister Purge Valve
Fault
Type
13h Circuit Open
13h APC & component activated since 1,3ms
11h APC & component activated since 1,3ms
12h APC & component not activated since 0,80µs
13h Hardware detection of Open Circuit 2000 ms 4000 ms
11h Hardware detection of Short Circuit to Ground 2000 ms 4000 ms
12h Hardware detection of Short Circuit to Battery 650 ms 650 ms
Specific Snapshot
$2822 - Canister drain valve command
-
-
-
-
72 / 120
6.1.34 P0461 – Fuel Level Sensor
DTC 0461h
Fuel Level Sensor
Fault
Type
If ignition key is on or has been switched off since a period less than the calibration 11 s with the condtion that Counter of valid
17h
frame >= 4 -
If ignition key is on or has been switched off since a period less than the calibration 11 s with the condtion that: Counter of
16h
valid frame > 4 -
17h High period signal of fuel tank gauge > 900 ms 14000 ms 28000 ms
16h High period signal of fuel tank gauge < 100 ms 6000 ms 12000 ms
Specific Snapshot
$287F - Memorized variable of the fuel level
-
-
-
73 / 120
6.1.35 P0480 – Fan 1 Control Relay
DTC 0480h
Fan 1 Control Relay
Fault
Type
13h Circuit Open
13h +APC and fan not activated
11h '+APC and fan not activated
12h +APC and fan activated
13h Hardware detection of open circuit or short circuit to battery 1000 ms 2000 ms
11h Hardware detection of open circuit or short circuit to ground 1000 ms 2000 ms
Specific Snapshot
-
-
-
74 / 120
6.1.36 P0500 – Vehicle Speed Sensor
DTC 0500h
Vehicle Speed Sensor
Fault
Type
3Ah Too Many Pulses Measured
39h Too Few Pulses Measured
3Ah DTC 0500h not present
DTC 0500h not present AND engine speed > 1100 rpm AND engine torque > 54 N.m AND clutch pedal not pressed AND
39h
brake pedal not pressed
3Ah Raw value of vehicle speed > 215 km/h 400 ms 20 ms
39h Raw vehicle speed value < 3 km/h 41000 ms 187200 ms
Specific Snapshot
$2C03 - Targetted gear engaged
$2025 - Brake pedal - close active switch state
$2026 - Brake pedal - open active switch state
$206D - Configuration - Clutch pedal - minimum travel switch
-
75 / 120
6.1.37 P0504 – Brake Pedal
DTC 0504h
Brake Pedal
Fault
Type
91h Component Parameter Outside its Expected Range
64h DTC 0571h & 0703h not present
91h DTC 0571h not present and DTC 0703h
64h Brake pedal pressed & vehicle speed > 20 km/h during 30 s 100 ms 100 ms
If coherency seen
Braking is seen by close active brake switch but not by the open one during between the 2
91h 100 ms
more than 2,6 s contactors during
braking phase ms
Specific Snapshot
$200F - Brake pedal - switches consolidation state
$206A - Brake pedal - duration of the close active switch blocked
$206B - Brake pedal - duration of the open active switch blocked
-
-
76 / 120
6.1.38 P0530 – A/C Refrigerant Pressure Sensor
DTC 0530h
A/C Refrigerant Pressure Sensor
Fault
Type
17h
16h
17h ms ms
16h ms ms
Specific Snapshot
-
-
-
-
-
77 / 120
6.1.39 P0560 – Battery Voltage
DTC 0560h
Battery Voltage
Fault
Type
17h +APC AND Engine not in driven state AND engine speed < 16383,75 rpm
16h +APC AND Engine not in driven state AND engine speed >= 0 rpm
17h Battery voltage > 16 V 2500 ms 100 ms
16h Battery voltage < 9 V 10000 ms 100 ms
Specific Snapshot
$2057 - Alternator power
$2099 - Alternator load
$FD4D - Context No Safety data memorised.
$FD42 - Context No Safety data memorised.
78 / 120
6.1.40 P0571 – Closed Brake Sensor
DTC 0571h
Closed Brake Sensor
Fault
Type
29h Engine running and DTC 0571 not present
10 transitions ON <->
Close brake switch seen ON during 14400 s OR Close brake switch seen
29h 1000 ms OFF of close brake
OFF during 36000 s
switch ms
Specific Snapshot
79 / 120
6.1.41 P0606 – Engine Control Module - Processor
DTC 0606h
Engine Control Module - Processor
Fault
Type
04h No System Internal Specific SubType
04h Always
04h Hardware detection of Main CPU internal error. 200 ms ms 200 ms ms
Specific Snapshot
$FD43 - Context Safety data memorised with reset 1/2.
$FD4E - Context Safety data memorised with reset 2/2.
______________ Begin of FID_Enveloppe_2A44_v03.xls__060Ah__.doc ______________
80 / 120
6.1.42 P060A – Engine Control Module - Reset
DTC 060Ah
Engine Control Module - Reset
Fault
Type
F1h Safety Case 1
F2h Safety Case 2
F1h Always
F2h Always
F1h Hardware detection 40 ms 40 ms
F2h Hardware detection 40 ms 40 ms
Specific Snapshot
________________ End of FID_Enveloppe_2A44_v03.xls__060Ah__.doc ______________
______________ Begin of FID_Enveloppe_2A44_v03.xls__061Ah__.doc ______________
81 / 120
6.1.43 P061A – Engine Control Module - Torque Control Function
DTC 061Ah
Engine Control Module - Torque Control Function
Fault
Type
61h Algorithm Based Calculation Failure
F9h Limp Home
64h - Engine speed > 1504 rpm - Coolant temperature > 70 °C - 1 reset already requested by safety strategy - within 10s after reset
61h - Engine speed > 1504 rpm - Coolant temperature > 70 °C
F9h
Final indicated torque set point without anti-jerck correction - Final indicated
64h torque set point for safety < 40 Nm Estimated indicated torque from 40 ms
ms
manifold air pressure - Final indicated torque set point for safety < 50Nm
Final indicated torque set point without anti-jerck correction - Final indicated
61h torque set point for safety < 40 Nm Estimated indicated torque from 240 ms
ms
manifold air pressure - Final indicated torque set point for safety < 50Nm
F9h Manifold pressure value > table hPa + 200 hPa 240 ms ms
ms
Specific Snapshot
$2418 - Throttle valve position sensor voltage - track 1
-
________________ End of FID_Enveloppe_2A44_v03.xls__061Ah__.doc ______________
82 / 120
6.1.44 P0627 – Fuel Pump Control
DTC 0627h
Fuel Pump Control
Fault
Type
13h Circuit Open
13h +APC AND pump not activated
11h +APC AND pump not activated
12h +APC AND Pump Activated
13h Hardware detection of Open Circuit 1000 ms 2000 ms
11h Hardware detection of Short Circuit to Ground 1000 ms 2000 ms
12h Hardware detection of Short Circuit to Battery 1000 ms 2000 ms
Specific Snapshot
$281C - Gas pump command state
$2861 - Gas pump priming state
$2862 - Gas pump priming done
-
-
83 / 120
6.1.45 P0638 – Intake Throttle Actuator Control Function
DTC 0638h
Intake Throttle Actuator Control Function
Fault
Type
77h Unable to Move the Component to the Commanded Position
78h Incorrectly Adjusted or Aligned Component Detected
77h Inlet throttle regulation activated AND no DTC present linked to Inlet Throttle
78h Always
IT command NOT between -6000 mV & 6000 mV AND |IT setpoint - IT At next driving cycle
77h Immediately ms
position| > 8 % Vsens AND IT position regulation error sign doesn't change ms
78h Counter of detection failure is superior at 4 wu 2 ms 2 ms
Specific Snapshot
$2414 - Throttle valve position setpoint
$24C9 - Limp home position of the inlet throttle
-
84 / 120
6.1.46 P0641 – Power Supply 1
DTC 0641h
Power Supply 1
Fault
Type
17h Always
16h Always
17h Power supply 1 voltage is above maximum threshold 250 ms 2500 ms
16h Power supply 1 voltage is below minimum threshold 250 ms 2500 ms
Specific Snapshot
-
85 / 120
6.1.47 P0650 – Malfunction Indicator Lamp (MIL) Control Circuit
DTC 0650h
Malfunction Indicator Lamp (MIL) Control Circuit
Fault
Type
16h APC and 7,002 V < Battery Voltage < 17,958 V
17h APC and 7,002 V < Battery Voltage < 17,958 V
17h Hardward detection 2900 ms 2900 ms
Specific Snapshot
$2028 - MIL lamp request state
-
-
-
-
86 / 120
6.1.48 P0651 – Power Supply 2
DTC 0651h
Power Supply 2
Fault
Type
17h Always
16h Always
17h Power supply 2 voltage is above maximum threshold 250 ms 2500 ms
16h Power supply 2 voltage is below minimum threshold 250 ms 2500 ms
Specific Snapshot
-
87 / 120
6.1.49 P0657 – Actuators Power Relay
DTC 0657h
Actuators Power Relay
Fault
Type
11h End of powerlatch phase.
Hardware detection of short circuit to ground (actuator relay cut request and Failure set at next Failure reset at next
11h
power latch phase is ended) driving cycle ms driving cycle ms
Specific Snapshot
$200E - Key state
-
-
-
88 / 120
6.1.50 P0703 – Open Brake Pedal Switch
DTC 0703h
Open Brake Pedal Switch
Fault
Type
29h Engine running and DTC 0571 not present
10 transitions ON <->
An open active brake switch failure is detected if this switch is stuck at ON
29h 1000 ms OFF of open brake
or OFF until there is a calibrated number of transition
switch ms
Specific Snapshot
89 / 120
6.1.51 P0833 – Begining of Clutch Pedal Move Switch
DTC 0833h
Begining of Clutch Pedal Move Switch
Fault
Type
29h Vehicle speed > 2 km/h
On clutch switch
(30 0 gear changes without clutch contact detection) OR (Gear is 2 or over
29h 10 ms activation detection
AND 30 0 gear changes with clutch contact always ON)
ms
Specific Snapshot
$2059 - Clutch pedal - minimum travel switch state - wire
-
-
-
-
90 / 120
6.1.52 P1351 – Ignition Coil - Cylinder 1 and 4
DTC 1351h
Ignition Coil - Cylinder 1 and 4
Fault
Type
13h Circuit Open
13h Circuit Open
13h Engine running and either minimum battery voltage > 6000 mV OR Engine speed < 8000 rpm
13h Hardware detection of open circuit. IGC voltage is under minimum threshold < 250 ms ms < 20 ms ms
11h Hardware detection of short circuit to ground. < 250 ms ms < 20 ms ms
12h Hardware detection of short circuit to battery < 250 ms ms < 20 ms ms
Specific Snapshot
$2807 - Ignition advance
-
-
-
-
91 / 120
6.1.53 P1352 – Ignition Coil - Cylinder 2 and 3
DTC 1352h
Ignition Coil - Cylinder 2 and 3
Fault
Type
13h Circuit Open
13h Circuit Open
Specific Snapshot
$2807 - Ignition advance
-
-
-
-
92 / 120
6.1.54 P1633 – Additional Fuel Tank Solenoid Control
DTC 1633h
Additional Fuel Tank Solenoid Control
Fault
Type
13h Circuit Open
13h Component is not commanded since Low mask time calibration for Q1702 transistor, this calibration depends on loads.
11h Component is not commanded since Low mask time calibration for Q1702 transistor, this calibration depends on loads.
Component is commanded since High mask time calibration for Q1702 transistor (this calibration depends on loads) and PWM
12h
> 1,176470588 %.
Hardware detection of open circuit or short circuit to ground (Comparison of
13h 1000 ms 2000 ms
command state to output voltage)
11h 1000 ms 2000 ms
Hardware detection of short circuit to battery (Comparison of command state
12h 240 ms 2000 ms
to output voltage)
Specific Snapshot
-
-
-
-
93 / 120
6.1.55 P1644 – Relay of Air Heater Passenger Compartment 1
DTC 1644h
Relay of Air Heater Passenger Compartment 1
Fault
Type
13h Circuit Open
13h
11h
13h Hardware detection of open circuit ms ms
11h Hardware detection of short circuit to ground ms ms
Specific Snapshot
-
-
-
-
-
94 / 120
DTC 1645h
Fault
Type
13h Circuit Open
12h
13h
11h
12h
12h Hardware detection of short circuit to battery ms ms
13h Harware detection of open circuit ms ms
11h ms ms
12h ms ms
Specific Snapshot
-
-
-
-
-
95 / 120
DTC 1646h
Fault
Type
13h Circuit Open
13h
11h
12h
13h ms ms
11h ms ms
12h ms ms
Specific Snapshot
-
-
-
-
-
96 / 120
6.1.58 P1656 – Electromagnetic Torque Control
DTC 1656h
Electromagnetic Torque Control
Fault
Type
87h Message Not Received
82h Corresponding Rolling Count Value being unproperly Updated
87h Engine running
64h Always
82h Always
87h Elapsed time since the last ETC CAN frame event > 0,25 s 250 ms 2000 ms
64h Number of single ETC data coherency failure is superior at 3 wu 10 ms 2000 ms
82h Number of successive single ETC clock failures is superior at 3 wu 10 ms 2000 ms
Specific Snapshot
-
-
-
-
97 / 120
6.1.59 P2100 – Intake Throttle Actuator Control - H Bridge
DTC 2100h
Intake Throttle Actuator Control - H Bridge
Fault
Type
01h No Electrical Specific SubType
01h +APC and component activated
01h Hardware detection of undervoltage / overcurrent / overtemperature 280 ms 2790 ms
Specific Snapshot
$2457 - Throttle valve offset - min position - track 1
-
98 / 120
6.1.60 P2119 – Intake Throttle Actuator Offset Learning
DTC 2119h
Intake Throttle Actuator Offset Learning
Fault
Type
07h No Mechanical Specific SubType
91h Component Parameter Outside its Expected Range
75h Unable to Move the Component to the Emergency Position
07h Powerlatch phase AND no DTC present linked to Inlet Throttle
91h [Powerlatch phase OR First key-on of ECU life] AND no DTC present linked to Inlet Throttle
75h [Powerlatch phase OR First key-on of ECU life] AND no DTC present linked to Inlet Throttle
|LIH offset read on each track - LIH offset learnt for corresponding track| > Failure during 2 Success during one
07h
0,5 % Vsens successive PWL ms PWL ms
91h Inlet Throttle track 1 or 2 position NOT between 6 % Vsens & 14 % Vsens 4000 ms 4000 ms
75h Inlet throttle LIH position NOT between 13,2 % Vsens & 24,5 % Vsens 4000 ms 4000 ms
Specific Snapshot
$2457 - Throttle valve offset - min position - track 1
-
99 / 120
6.1.61 P2120 – Accelerator Pedal Position Sensor - Track 2
DTC 2120h
Accelerator Pedal Position Sensor - Track 2
Fault
Type
accelerator pedal sensor 2 output voltage > 0,7380254154 Uref ratio AND
17h 250 ms 1000 ms
accelerator pedal sensor 2 output voltage < 0,03812316716 Uref ratio AND
16h 250 ms 1000 ms
Specific Snapshot
-
100 / 120
6.1.62 P2135 – Throttle Correlation Between The Two Sensors
DTC 2135h
Throttle Correlation Between The Two Sensors
Fault
Type
2Fh Signal momentarily Implausible or Discontinuous
64h DTC 0120h not present during the current driving cycle AND DTC 0641h not present
2Fh DTC 0120h not present or memorized during the current driving cycle AND DTC 0641h not present
64h No coherency between IT sensor 1 and IT sensor 2 positions 275 ms 7000 ms
IT speed difference between sensor position 1 & 2 > 1 % Vsens during 0,004
2Fh 130s ms - ms
s OR Difference between IT sensor 1 & IT sensor 2 position > 4 % Vsens
Specific Snapshot
-
-
101 / 120
6.1.63 P2502 – Charging System Voltage Circuit
DTC 2502h
Charging System Voltage Circuit
Fault
Type
17h Ignition key is ON AND engine not running.
16h Ignition key is ON AND engine not running.
17h DF pwm = 100% for a duration over 2,55 s 10 ms 2000 ms
16h DF pmw = 0% for a duration over 2,55 s 1000 ms ms 2000 ms ms
Specific Snapshot
-
-
102 / 120
6.1.64 P2503 – Charging System Voltage Low Voltage
DTC 2503h
Charging System Voltage Low Voltage
Fault
Type
21h Signal Amplitude Below a Specified Range
21h Engine running . The diagnosis is activated after initialisation time (2 s)
21h Alternator load is inferior at minimun value (5,09803922 %) 11900 ms 100 ms
Specific Snapshot
-
-
103 / 120
6.1.65 P2632 – Second fuel Pump Control for additional fuel tank
DTC 2632h
Second fuel Pump Control for additional fuel tank
Fault
Type
13h Circuit Open
13h +APC and Pump not activated since Low mask time calibration for Q1703 transistor, this calibration depends on loads
11h +APC and pump not activated since Low mask time calibration for Q1703 transistor, this calibration depends on loads
+APC and Pump activated since High mask time calibration for Q1703 transistor, this calibration depends on loads AND . The
12h
pump is activated when PWM of electrovanne > 1,176470588 %
13h 1000 ms 2000 ms
11h 1000 ms 2000 ms
Hardware detection of short circuit to battery (Comparison of command state
12h 600 ms 2000 ms
to output voltage)
Specific Snapshot
$281C - Gas pump command state
-
-
-
______________ Begin of FID_Enveloppe_2A44_v03.xls__C101h__.doc ______________
104 / 120
6.1.66 PC101 – Lost Communication with Transmission Control Module
DTC C101h
Lost Communication with Transmission Control Module
Fault
Type
87h Always
87h AT torque request above max duration < 10s ms < 10s ms
Specific Snapshot
-
-
-
-
________________ End of FID_Enveloppe_2A44_v03.xls__C101h__.doc ______________
105 / 120
6.1.67 PC121 – Lost Communication With Anti-Lock Brake System (ABS)

Control Module
DTC C121h
Lost Communication With Anti-Lock Brake System (ABS) Control Module
Fault
Type
87h Always
87h Absence of ESP frame reception - ms - ms
Specific Snapshot
-
-
-
-
106 / 120
6.1.68 PC402 – Invalid Data Received From Transmission Control Module
DTC C402h
Invalid Data Received From Transmission Control Module
Fault
Type
63h Function actived for Greater than a Specified Time Period
64h Always
82h Always
63h Always
64h Unplausible AT torque request < 10s ms < 10s ms
82h Invalid data received from transmission < 10s ms < 10s ms
63h Invalid data received from transmission < 10s ms < 10s ms
Specific Snapshot
-
-
-
-
107 / 120
6.1.69 PC415 – Invalid Data Received From Anti-Lock Brake System Control
Module
DTC C415h
Invalid Data Received From Anti-Lock Brake System Control Module
Fault
Type
64h During an ASR or MSR regulation
82h During an ASR or MSR regulation
64h ESP torque request coherency detected failure - ms - ms
5 successive frame 2 successive frames ok
82h Incoherency of clock value between the last 2 frames
failures ms ms
Specific Snapshot
-
-
-
-
________________ End of DED_6.0.0.0.0.0.0_000_3K401030100011000012000000000000000002001020000000(2.0).doc ______________
6.2 Status and parameters

The available datas are defined hereafter :
DID (hex) Class

Reserved
0000 00FF Reserved by ISO/SAE
Supplier specific data
0100 0FFF Reserved for future use
1000 1FFF Nissan GMP
2000 23FF RSA GMP - Common ECM System
2400 27FF RSA GMP - Common ECM Air
2800 2BFF RSA GMP - Common ECM Fuel
2E00 2FFF RSA GMP – Specific Software
3000 EFFF Reserved for future use
Reserved
F000 FFFF Reserved by ISO/SAE
For more informations see DDT database

108 / 120
6.3 Configuration operation(s)

Two types of configuration are possible:
- Configuration by calibration / reprogramming
- Configuration by automatic detection
6.3.1 Configuration by calibration / reprogramming
Configuration in terms of diagnostic service (WriteDataByLocalIdentifier ! $3B)

6.3.2 Configuration by automatic detection
In terms of diagnostic service, configuration by automatic detection can be ensured with the $22
(ReadDataByIdentifier) service. For more details on automatic detections, see the chapter 3 of the associated
DFS.
6.4 Programming operation(s)

Operation conditions :
Factory Network
function conditions (see vehicle) for undertaking the operation. Key ON Key ON
Engine stopped Engine stopped
ECU unlocked
Operations to be performed :
ORDER
(in witch FUNCTIONS SERVICES
functions must
be called)
1 Initialisation of ECU for reprogramming. Depending on protocol used in target applications
2 Communication management Depending on protocol used in target applications
3 Reading of ECU Identification ReadDataByLocalId
4 Unlocking of ECU SecurityAccess #1 and #2
5 Partial or Global erasing of the Flash StartRoutineByLocalId
6 Request for Status / Erasing StartRoutineByLocalId
7 Modification of B.R. (Optional) StartDiagSession
8 Downloading of the ECU RequestDownload
9 ECU Self-check request StartRoutineByLocalId
109 / 120
10 Request for Status / Self-check StartRoutineByLocalId

11 Writing of Log zone RequestDownload
12 Writing of appli-key RequestDownload
13 Reading of ECU memory contents RequestUpload
14 End of reprogramming Depending on protocol used in target applications
110 / 120
______________ Begin of DED_6.5.0.0.0.0.0_000_3KXXXXX0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.0).doc ______________
6.5 Actuators command (30h)

Execution conditions:
• Inactive ignition cut off
• Out of power-latch phase
• Engine and car are stopped
• Between 2 achieved ECU power-latch, allowing maximum number of successive requests (See picture
below)
• ECU in +APC/key ON
• Vehicle speed (DiD $2003) <= @MON_VS_THD@
• Accelerator pedal position (DiD $202E) <= @MON_ACCEL_THD@
• Out of power-latch phase (+APC)
• If gearbox is not manual :
- Validity status of gearbox information
- Neutral position of gearbox
• Engine speed (DiD $2002) <= @MON_ENGSPD_MAX@
• Boost pressure (DiD $2401) <= @MON_SPG_MAX@
• Coolant temperature (DiD $2001) <= @MON_WATERTEMP_MAX@
• Following DTC not raised: : $C121, $C415, $0225, $0226, $2120, $0335, $012A, $0115
Stop conditions:
• Conditions of execution are not respected
• Communication lost with diagnosis tool.
• End of test
Description du cycle de commande :
Cycle 1 Cycle n
1 or PWM
(ON state)
T_INI T_ON T_OFF
0 or PWM
(OFF state)
Time
Remarks:
• Actuator’s command is not necessarily audible by the human ear ( ).
• Heaters relay can work if electric consumers inhibition as been removed.
• Injectors command does not work if measured rail pressure is less than 10 bars.
This service is used to drive select actuator for a choosing number of cycles.
Component Description Value

Electronic throttle (gasoline) MAXI CYCLES NUMBER @NB_CYCLE_ACTUATEUR_01@
ON STATE DURATION @TPS_ON_ACTUATEUR_01@
OFF STATE DURATION @TPS_OFF_ACTUATEUR_01@
Fuel pump MAXI CYCLES NUMBER @NB_CYCLE_ACTUATEUR_02@
111 / 120
Relay FAN1 MAXI CYCLES NUMBER @NB_CYCLE_ACTUATEUR_03@

Relay FAN2 MAXI CYCLES NUMBER @NB_CYCLE_ACTUATEUR_04@
Canister drain valve MAXI CYCLES NUMBER @NB_CYCLE_ACTUATEUR_20@
Relay clim. AC out MAXI CYCLES NUMBER @NB_CYCLE_ACTUATEUR_27@
Fuel injector 1 MAXI CYCLES NUMBER @NB_CYCLE_ACTUATEUR_35@
Additional tank pump MAXI CYCLES NUMBER @NB_CYCLE_ACTUATEUR_49@
Electro valve PWM of additional
MAXI CYCLES NUMBER @NB_CYCLE_ACTUATEUR_50@
tank
________________ End of DED_6.5.0.0.0.0.0_000_3KXXXXX0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.0).doc ______________
______________ Begin of DED_6.6.0.0.0.0.0_000_3KXXXXX0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.0).doc ______________
6.6 Routines execution
For each routine, the launch request is $31xx00h (xx is the routine identifier)
During the test you can check the status with the request $31xx01h, answers can be:
71xx00h: routine not launched
71xx01h: routine ongoing
71xx02h: routine finished
71xx03h: routine shut down (conditions nok)
6.6.1 Static test (31 07 00 h)
This service allows the actuator driving commands that are normally not activated during a +APC phase, and to
do their electrical diagnoses.
Drive actuators during that test are listed in table below.
Service “StartRoutineByLocalIdentifier / Static Tests” allows simultaneous actuators drive.
Purpose of that service is a return of diagnosis on every UCE outputs.
112 / 120
The driving durations must be long enough to have a correct return of diagnosis without impact on target
actuator.
Static test duration (all of outputs driving) must not exceed 2 seconds.
Target outputs are:
Target outputs are : DTC (hex)

Fuel pump 2632h
Canister drain valve 0443h
Spark plug 1 1351h
Spark plug 2 1352h
Spark plug 3 1352h
Spark plug 4 1351h
Fuel injector 1 0201h
Routine execution conditions:

• Coolant temperature (DiD $2001) <= @MON_WATERTEMP_MAX@
• Out of power-latch phase (+APC).
• Engine not autonomous.
• Battery voltage (DiD $2005) > @MON_VB_MIN@
• No routine in progress.
• Following DTC not raised $0335, $012A, $0115, $0225, $0226, $2120, $0560
Stop conditions:
• Executions conditions are not respected.
• Loss of communication with diagnosis tool.
• End of test
Command cycle description:

• Command cycle launch simultaneously and at the same time, all unitary actuators command which are
defined in table.
• The number of successive commands between 2 cold ECU reset is limited to 10.
Remarks:
• Actuator’s command is not necessarily audible by the human ear.
• Heaters relay can work if electric consumers inhibition as been removed.
________________ End of DED_6.6.0.0.0.0.0_000_3KXXXXX0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.0).doc ______________
• Injectors command does not work if measured rail pressure is less than 10 bars.
______________ Begin of DED_6.6.X.0.0.0.0_020_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.1).doc ______________
6.6.2 MONITOOL (31 21h)
113 / 120
6.6.2.1 Protocol of communication:
This section presents all of MONITOOL wefts, which are sent by diagnosis extern tool on CAN
and ECU possible responses.
6.6.2.1.1 General plan:
MONITOOL is a function, which extends diagnosis coverage (development for plant and after
sale). Its integration in ECM allows internal variables control and outputs, in respect of diagnosis
tools scenarios.
6.6.2.1.2 Activation request:
Byte Name of service Encoding

#1 StartRoutineByLocalIdentifier $31
#2 Monitool mode $21
#3 Launch routine $00
#4 Security time out $00 - $FF
#5 Security clock $00 - $FF
#6 Number of controlled parts (N) $00 - $FF
#7 Requested identifier n°1 $00 - $FF
Value for requested identifier n°1
#8 $00 - $FF
(MSB)
114 / 120
Value for requested identifier n°1

#9 $00 - $FF
(LSB)
~~~ ~~~ ~~~
#3N+4 Requested identifier n°N $00 - $FF
Value for requested identifier n°N
#3N+5 $00 - $FF
(MSB)
Value for requested identifier n°N
#3N+6 $00 - $FF
(LSB)
Additional information:
• N may be equal to zero (for communication validation or time measures). The corresponding
positive response for a no identifier request is "Routine in progress".
• It is forbidden to request more than once the same identifier in the same launch request.
• If MONITOOL is running with active bypass and a new launch request is sent:
- MONITOOL must continue if the request is valid.
- All the old bypass which have been re-specified in the new launch must take their new value.
Moreover, for the old bypass, which have not been requested again, they also must be
maintained with their replacement value.
Status request
#3 Status routine $01
#4 Security time out * $00 - $FF
#5 Security clock $00 - $FF
*: 10ms scaling/bit
Positive response implementation

#1 StartRoutineByLocalIdentifier OK $71
Routine is disabled $00
#3 Routine in progress $01
Routine aborted $03
*1: this response should be sent also in case of a “Status request” without a previous “Launch
request” (MONITOOL deactivated).
*2: the clock difference between the received frame and the previous frame is zero or greater
than one.
Negative response implementation

#1 Negative response $7F
Power latch phase
$22
or vehicle immobilizer is active
#3 $7F (-B)
Required diagnostic session is not
or
active (*)
$80 (-A)
(*): when a Monitool abnormal stoppage occurred, the ECM must return in default session
6.6.2.1.3 Stop request:
115 / 120
Request implementation
#1 StopRoutineByLocalIdentifier $32
#3 Routine output parameter $00
Positive response implementation

#1 StopRoutineByLocalIdentifier OK $72
#3 Routine output status $xx
Negative response implementation

#1 Negative response $7F
#2 StopRoutineByLocalIdentifier $32
#3 Routine output parameter $xx
6.6.2.1.4 Reading of supported identifiers:
To read supported identifiers, read MONITOOL weft with service 21 01h
6.6.2.2 Values calculation to send on CAN by identifier:
A common messaging base has been established to spread calculation method of send values
by start requests, on all RSA applications.
________________ End of DED_6.6.X.0.0.0.0_020_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.1).doc ______________
______________ Begin of DED_6.6.X.4.0.0.0_020_XXXXXX3XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX1XXXXXXXXX(1.4).doc ______________
6.6.2.3 Activation conditions and MONITOOL deactivation:
MONITOOL scenario launch must respect security and functional conditions. Many parameters surveys are
activated when MONITOOL is used.
To launch a MONITOOL request when another routine is in progress is not authorized.
6.6.2.3.1 Embarked vehicle watching:
These watching are continuously made in order to secure COTECH staff, with sure vehicle immobilization
during MONITOOL tests.
The parameters surveys are:
• Vehicle speed <= @MON_VS_THD@

• Accelerator pedal position <= @MON_ACCEL_THD@
• Following DTC are not raised: $C121, $C415, $0225, $0226, $2120
If one of these points is not respected, MONITOOL is cut immediately.
116 / 120
6.6.2.3.2 Embarked engine watching:
These watching are continuously made for all bypasses in order to protect engine components during
MONITOOL tests.
The parameters surveys are:
• Vehicle speed <= @MON_VS_THD@

• Accelerator pedal position <= @MON_ACCEL_THD@
• Engine speed <= @MON_ENGSPD_MAX@
• Boost pressure <= @MON_SPG_MAX@
• Coolant liquid temperature <= @MON_WATERTEMP_MAX@
• Following DTC not raised: : $C121, $C415, $0225, $0226, $2120, $0335, $012A, $0115
If it is a diesel engine, these specific surveys are added:

• Exhaust gas temperature before turbine <= @MON_TBT_MAX@
• Rail pressure <= @MON_RAILP_MAX@
• Following DTC not raised: $0544, $0190
If one of these points is not respected, MONITOOL is cut immediately.

Calibrations have to be a compromise between components security and free driving in scenarios. These
calibrations are specific to the project.
6.6.2.3.3 Bypass watching:
These watching are specific for every bypass and allow the no degradation of engine components during
MONITOOL tests.
It exist 2 types of bypass watching:
Additional diagnoses: Created by RSA profession.
Replacement value limit sent by diagnosis tool : Value sent on 2 bytes according to common diagnosis
messaging base. Values perimeter is wider than RSA functional dictionary, and wider than security zone.
Security zone is limited by a minimum C_MIN_LID_XSC[XXX] and a maximum C_MAX_LID_XSC[XXX]

(with XXX MONITOOL identifier number in decimal). If for one bypass, command is not in security perimeter,
MONITOOL is cut off.
Calibrations are a compromise between components security and driving freedom in scenarios. These
calibrations are specific to the project.
6.6.2.3.4 ECM / Tool communication watching:
All tests are made on communication between tool and ECM, notably the loss of wefts.
Security clock: it is a test on loss of wefts. It is made by verification of increment of clock between 2 messages.
If the increment is not equal to 1, MONITOOL is cut off.
117 / 120
Time-out: it is a test on maximal duration (in milliseconds), between 2 requests. Verification of interval between
2 messages. MONITOOL is cut off if defined time out duration in an other weft, is sold without new weft
reception.
________________ End of DED_6.6.X.4.0.0.0_020_XXXXXX3XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX1XXXXXXXXX(1.4).doc ______________
______________ Begin of DED_6.6.X.0.0.0.0_030_XXXXXX3XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(3.1).doc ______________
6.6.3 Lbup routine (31 0A 00 h)
Safety conditions constraints:
Engine protection:
• Engine coolant temperature (DiD $2001) <= @MON_WATERTEMP_MAX@
• Following DTC not raised $0335, $0105, $0115
User protections:
• Following DTC not raised $C121, $C415, $0225, $0226, $2120, $0560.
Routine execution conditions :

• No routine in progress
• Safety conditions constraints are respected
• Engine stopped
• Following DTC not raised: $0225, $0226, $2120
Stop conditions:
• Execution constraints are not respected,
• Stop request by diagnosis tool StopRoutineByLID 32h 0Ah 00h,
• Lbup routine is running.
________________ End of DED_6.6.X.0.0.0.0_030_XXXXXX3XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(3.1).doc ______________
118 / 120
______________ Begin of DED_6.6.X.0.0.0.0_040_XXXXXX3XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(2.1).doc ______________
6.6.4 Catalyst routine (31 08 00 h)
Safety conditions constraints:
Engine protection:
• Following DTC not raised $0335, $012A, $0115
User protections:
• Accelerator pedal position (DiD $202E)<= @MON_ACCEL_THD@
• Following DTC not raised: $C121, $C415, $0225, $0226, $2120, $0560.
Routine execution conditions:

• Engine stopped
• Following DTC not raised: $0225, $0226, $2120
Stop conditions:
• Execution conditions are not respected
• Stop request by diagnosis tool StopRoutineByLID 32h 08h 00h
• Catalyst routine is running.
________________ End of DED_6.6.X.0.0.0.0_040_XXXXXX3XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(2.1).doc ______________
119 / 120
______________ Begin of DED_6.6.X.0.0.0.0_060_XXXXXX3XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX10XXXXXXXX(5.0).doc ______________
6.6.5 Fuel Feed inhibition routine (31 04 00 h)
Safety condition constraints:
Engine protection:
• Intake manifold pressure (DiD $240B) <= @MON_MAP_MAX@
• Exhaust gas temperature before turbine (DiD $2439) <= @MON_TBT_MAX@
• Rail pressure (DiD $2801) <= @MON_RAILP_MAX@
• Following DTC not raised: $0335, $0544, $0105, $0190, $0115
User protection:
• Accelerator pedal position (DiD $202E)<= @MON_ACCEL_THD@
• Following DTC not raised: $C121, $C415, $0225, $0226, $2120, $0560.
Routine execution conditions :

• Engine stopped
• Following DTC not raised: $0120, $0201, $0202, $0203, $0204, $0220, $0225, $0226, $0638, $2100,
$2119, $2120, $2135.
Stop conditions :
• Execution constraints are not respected.
• Stop request by diagnosis tool StopRoutineByLID 32h 04h 00h.
________________ End of DED_6.6.X.0.0.0.0_060_XXXXXX3XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX10XXXXXXXX(5.0).doc ______________
• Fuel feed inhibition routine is running.
120 / 120

Diagnostic Document for V42 ECU 2A Software

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Diagnostic Document for V42 ECU 2A Software

Uploaded by

Copyright:

Available Formats

DED_V42_2A_X79-X90-X35_K7M-K4M-F4R(4.0).

______________ Begin of DED_1.0.0.0.0.0.0_000_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.5).doc ______________

DIAGNOSTIC USER DOSSIER

V42 ECU / 2A Software

Written by: Reviewed by: Approved by:

AUTHOR(S) NUMBER OF PAGES TYPE OF DOCUMENT

KEYWORDS INPUT MODE

NO. DATE PAGES REVISED REASON(S) FOR REVISION

5.5 EOBD fault management 33

6.1.47 P0650 – Malfunction Indicator Lamp (MIL) Control Circuit 66

2IC : factory correction of the SIEMENS injectors

Y ________________ End of DED_1.0.0.0.0.0.0_000_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.5).doc ______________

______________ Begin of DED_2.0.0.0.0.0.0_000_3XXXX0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.0).doc ______________

2 Control Unit Identification

The corresponding identification we can see on 2180 request is the following:

________________ End of DED_2.0.0.0.0.0.0_000_3XXXX0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(1.0).doc ______________

______________ Begin of DED_3.0.0.0.0.0.0_000_3KXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX(3.0).doc ______________

ECU PIN DESCRIPTION

ECU PIN DESCRIPTION

ECU PIN DESCRIPTION

A.A1 Not used

A.A2 On/Off cruise control Input 0V/Vbat 0V Vbat H H N N N N N N No DTC

A.B2 TDC engine signal Low Side PWM H H H H No DTC

A.B3 Heat Fan in Input 0V / Vbat 0V Vbat No DTC

A.B4 Diagnosis K link Network H H H H No DTC

A.C1 Fan 2 relay command Low Side 0V Vbat H H H H DTC $0481

A.C2 Not used

A.C3 On/Off speed limiter Input 0V/Vbat 0V Vbat H H N N N N N N No DTC

A.C4 Clutch signal Input 0V/Vbat 0V Vbat H H N N N N N N No DTC

A.E1 CAN L3 (private engine) Network H H H No DTC

A.E2 CAN H3 (private engine) Network H H H No DTC

A.E3 Close brake on signal Input 0V/Vbat 0V Vbat H H No DTC

A.E4 Open brake on signal Input 0V/Vbat 0V Vbat H H N N N N N N No DTC

A.F1 Not used

A.G4 Power ground 1 Ground 0V 0V N N N N N N No DTC

A.H1 Power ground 2 Ground 0V 0V N N N N N N No DTC

SW = software detection (Plausibility)

Y = yes / hardware diagnosis

B.A1 Injector 1 Output Low Side 0V Vbat H H H H Y Y Y DTC $0201

B.A2 Injector 2 Output Low Side 0V Vbat H H H H Y Y Y DTC $0202

B.A3 Injector 3 Output Low Side 0V Vbat H H H H Y Y Y DTC $0203

B.A4 Injector 4 Output Low Side 0V Vbat H H H H Y Y Y DTC $0204

B.B3 Knock control Input Input 0V H H SW No DTC

B.B4 Knock control ground Ground 0V 0V N N N N N N No DTC

B.C4 Steering Pressure Input Input 0V H H No DTC

B.E3 Air temperature ground Ground 0V 0V N N N N N N DTC $0095

B.E4 Engine Speed Input (-) Input 0V H H SW SW No DTC

B.F3 Engine Speed Input (+) Input 0V H H SW SW No DTC

B.F4 Water temperature ground Ground 0V 0V N N N N N N DTC $0115

B.H4 Intake Manifold Ground Ground 0V 0V N N N N N N No DTC

B.J4 Freon Temperature Input Analog 0V H H No DTC

B.K1 Vehicle Speed Input PWM 0V H H No DTC

B.K2 Freon Pressure Ground Ground 0V 0V N N N N N N DTC $0530

B.K3 CAN L2 Network H H H DTC $0530

B.K4 CAN H2 Network H H H No DTC

B.L3 Intake VVT Output Low Side 0V Vbat H H H H Y Y Y Not used

B.L4 Water Pump Output Low Side 0V Vbat H H H H SW SW Not used

B.M1 Not used

B.M2 VBR Power Supply Input 0V Vbat H H H H SW No DTC

SW = software detection (Plausibility)

Y = yes / hardware diagnosis

N° pin Signal Name Signal Type