AUTOBEST 258031 Manual De Instrucciones página 12

• Vérifi ez que le contact est enclenché sur le véhicule (position KOER).
• Activez le Test LED dans le MENU PARAMETRES. Si l'outil diagnostic ne réussit pas ce test, il y
a un problème avec les lumières LED. Reportez-vous au paragraphe
« GARANTIE ».
ENVIRONNEMENT
Préservez la santé des personnes en sauvegardant les ressources naturelles et l'environne-
ment; ne jetez pas cet appareil avec les ordures ménagères mais déposez le, lorsqu'il sera
en fi n de vie et hors d'usage, dans un centre de récupération et de recyclage des appareils
électriques ou chez un distributeur (selon réglementation et situation géographique, en application
de la directive 2012/19/UE).
*TABLEAU COMPOSITION D'UN CODE ERREUR
Exemple de code
Système
B = Carrosserie
C= Châssis
P = Sytème d'entrainement
1 = Carburant/Air/Sonde lambda
U = Réseau éléctrique
2 = Prise d'air et système de pression
3 = Système d'allumage, contrôle d'allumage raté
4 = Contrôle d'émissions et d'échappement
Type de code
5 = Vitesse et système de commande de frein
6 = gestion du moteur / Ordinateur de bord
0 = Code générique
7 = Transmission/Capteur hydraulique
1 = Code spécifique
8 = Transmission / Pression hydraulique
au conducteur
9 = Boîte de vitesse automatique
P0202
Sous-Systèmes
Le code d'erreur
indique quel
composant est
défectueux
12
sharp edges, corners or hot surfaces.
• The OBD II diagnostic device is not suitable
for permanent installation in a vehicle. Do
not use this device while driving.
• Only perform the test using the diagnostic
device in a safe environment. Keep clothes,
hair, members and the diagnostic device well
away from moving parts or hot parts of the
engine.
• During operation of the diagnostic device,
the working area must be well ventilated.
• Do not use other measuring equipment when
operating the diagnostic device in the vehi-
cle.
• Do not connect other cables to the device.
• All causes of faults on the vehicle must fi rst
be corrected before clearing the trouble code
permanently from the trouble code memory
of the diagnostic device.
• Erasing a trouble code does not solve the ve-
hicle failure or problem. These trouble mes-
sages may be displayed again for as long as
the problem has not been repaired in a car
repair shop. Have the problems repaired in a
specialised garage.
Presentation of OBD-II and diagnostics:
The term OBD-II (On-Board Diagnostics II)
refers to a standard diagnostic interface on-
board most internal combustion engine vehi-
cles produced since 2000. This system reads
the trouble codes generated by the on-board
computer system, as well as real-time data
from sensors connected to ECUs. The codes
recorded by the ECUs can also be deleted
once maintenance has been carried out.
DTCs:
DTC (Diagnostic Trouble Code): trouble code
detected by the system. This code, readable
by the diagnostic tool, gives a precise desig-
nation of the fault detected.
MIL (Malfunction Indicator Light): Malfunction
light signal: This is the name given to the light
on the dashboard in the event of a fault (gen-
erally called "service"). If it remains on contin-
uously, a malfunction is present. If it fl ashes,
the malfunction is severe and the vehicle must
be immobilised.
PCM (Powertrain Control Module) : OBDII
module that controls the engine and power-
train.
COMPOSITION OF A TROUBLE CODE
The trouble codes are displayed on the diag-
nostic tool (DTC = Diagnostic Trouble
Code). These trouble codes are transmitted
from the vehicle memory to the OBDII tool.
The following example illustrates the compo-
sition of a trouble code: *See table page 34
COMMUNICATION MODES
Communications between the computer and
the diagnostic tool are grouped into 10 data
exchange services called "modes". Mode 10 is
not used and manufacturer-specifi c.
Identifi cation of mode: The fi rst byte of an
OBD II request identifi es the diagnostic mode.
The response transmitted via the protocol is
equal to this value + 64.
For example, for a mode 1 diagnostic request,
the fi rst byte of the request is 1, and the fi rst
byte of the response will be 1 + 64 = 65
Here is a brief summary of the communication
modes allowed by the OBD II protocol:
Mode $01: Show current data (engine param-
eters) as well as the number of faults stored
in memory.
Mode $02: Show freeze frame data (same as
$01 mode) when a failure is detected.
Mode $03: Clear trouble codes detected on
the vehicle.
Mode $04: Clear trouble codes and freeze
frame data stored when the fault was detect-
ed. Also puts the MIL lamp out. Attention: if
the vehicle has not been repaired, the fault will
reappear.
Mode $05: Display of Lambda measuring sen-
sor values (oxygen sensors).
Mode $06: Display of measuring values of the
25