| EXPERIENCE OF USING SCANTOOL |
| 1. What are the essence and operating principle of scantool OBD? |
| - Scantool OBD reads data memory in ECU on vehicle, decodes
information and displays malfunction, do not look for the fault directly from sensors as before.
- Nowadays, in ECU system with OBD, defining the faults of a vehicle is the duty of ECU, it is the technology of each vehicle manufacturer, therefore, this is called equipment for reading fault code. - OBD (On-board diagnostic) means new generation vehicle, there is a trouble diagnosis function in ECU |
| 2. Basic steps to determine engine malfunction by scantool |
| Step 1
Troubleshooter checks vehicle operation status, diagnoses by visual and experience, observes abnormal warning lamp on instrument panel. Step 2 - Define make, model, year of manufacture - Determine and select suitable scantool (OBD-I or OBD–II) Step 3 - Connect scantool with vehicle. (Note: must not disconnect with battery before diagnosing) - Read the faults stored in ECU. Print, save file or note them - Clear the code which was being stored in ECU: + If vehicle is OBD-II, use equipment to clear all the fault code in ECU + If vehicle is OBD- I, unplug the battery cable about 30 seconds and then reconnect Step 4 Start engine and drive to make engine temperature increase. Take actions: parachute brake, rev up, turn left and right to have different operating status and load. That helps ECU get the fault code again and the check indicator may be on. Step 5 Stop the car, stop engine, ignition key is “ON” position and read the fault code, being stored in ECU. These current fault codes need to repair, other faults which is illusive do not display again, because the old faults are not cleared or someone unplugs a cable and then reconnects. Step 6 - Repair or replace damaged component, clear the faults in ECU again and reset ECU. - Start engine and observe system operation again. |
| 3. If the code is not defined successful, this is because of some following reasons |
| Case 1
Vehicle and scantool can not connect together because of unsuitable protocol, wrong set up, port connection, baud rate… Example: baud rate must be set 38400 Case 2 ECU is damaged because of chain rupture or IC fail Case 3 No power source from vehicle to ECU Case 4 No trouble code has been stored in ECU. Usually, ECU can mange about 65% malfunction relating to electrical system, sensors…the other 35%, belong to mechanic fault that can not be stored. It means OBD scantool only read electrical faults Case 5 User run many programs simultaneously (there are 3-4 windows in taskbar) Case 6 If scantool uses USB- COM cable, illusive USB- COM is installed incorrectly (watch video clip) Note: - When check engine light turns on, the car should be taken to workshop to check and repair. - If before repairing, battery cable was unplugged or engine is cold, it should be started again to warm up engine and take actions as above tips. |
| 4. User guide for each parts of DTDScantool |
| I. OBD-II SCANTOOL 1. Equipment introduction - Area of application: read the faults of engine and relative electrical system (not other system), because OBD- II only works with engine. OBD- II scantool can define the engine malfunctions of vehicle that is of OBD II international standard (Use for most of new cars (02 seats to 16 seats) and light trucks use 12V battery manufactured for Japan, Europe, USA, Asia market). Reference in car list. - Functions: + Read and clear fault codes stored in ECU. + Reset ECU + Display data current of sensor and engine parameter on vehicle. - Action: the vehicles belong to OBD II standard is completely the same as the way of diagnosing. 2. Using basic steps - Except for common steps in using scantool, troubleshooters need to follow some following particular steps: - Ignition key is OFF position, connect diagnostic cable with vehicle (Blue indicator in ECU is on) - Turn on computer, run DTD-Code - Connect USB cable with converter box - Turn on ignition key - Click “connect to engine”. If status reports display about 4-5 seconds and loose, connection is successful. If the report still displays, connection is unsuccessful. To confirm whether connection succeeds or not? Click on sensor to know current parameter sensors such as engine speed, throttle body angle, engine load, engine temperature…(if engine can start, start engine to confirm this connection is recommended) * Other notice In sensor box if the connection indicator above is blue – successful, if it is yellow- unsuccessful, click “reset interface” to confirm again. * Read fault codes - Back to home screen, click “read code”, a new window opens to display the code. The code is on the left of the window. - Enter correctly the code in to OBD II software to decode (enter “0” not “O”) - Read result and repairing hints. - If you need to know more information about electrical circuit, color wire, position of damaged part, search in Alldata, Autodata, Mitchell5 software… II. EFI SCAN scantool (use for OBD-I TOYOTA) 1. Equipment introduction - Area of application: read the fault code of engine, ABS, and electrical system on Toyota and Lexus – old generation- not belong to OBD II international standard yet (especially used for Toyota models which have 16-pin connector like OBD-II but not work with OBD-II Scantool, updated to 2009). Reference in car list. - Function: read current fault code in engine and ABS ECU . - Action: use and connect cable is different among vehicle with DLC1, DLC2, and DLC3 2. Basic steps to use - Connect computer data link cable and EFI SCAN ECU (Notice: follow the instruction to connect correctly) - Connect wire correctly. - Key ignition is ON position (Indicator on EFI SCAN is on) - Turn on computer and EFI SCAN - Select the function of reading faults code (command button on the right) - Set necessary check parameter in engine or Abs (default is engine) - Select “ON/OFF” to reset and connect to vehicle - Observe the reports in screen until “ready” displays (check indicator flickers, if not, check cable connection E to E1 and T to TE1) - Select “diagnose” to look for the faults (this function runs when sand glass runs and informs looking for the fault no more than 45 seconds, if sand glass does not run or looking do not end or too long…start engine again, may be, cable W is not in the right position) - When looking the faults end, read the report and repairing hint on the screen - If you want to read the faults again, click “reset” and waiting for “ready” - After repairing and replacing damaged components, to clear the faults in ECU, disconnect battery cable in 30 seconds or more and then connect. - Start engine and check the result with EFI Scan. |