current (short circuit) 

P0983 

ON/OFF electromagnetic valve S4 low 

current(open circuit) 

P0985 

Electromagnetic valve S5 over current 

(short circuit) 

P0986 

Electromagnetic valve S5 low 

current(open circuit) 

Refer to3.5.7.20 DTC P0985 P0986 

P0998 

Electromagnetic valve S6 over current 

(short circuit) 

P0999 

Electromagnetic valve S6 low 

current(open circuit) 

Refer to3.5.7.21 DTC P0998 P0999 

P099B 

Electromagnetic valve S7 over current 

(short circuit) 

P099C 

Electromagnetic valve S7 low 

current(open circuit) 

Refer to3.5.7.22 DTC P099B P099C 

P099E 

Electromagnetic valve S8 over current 

(short circuit) 

P099F 

Electromagnetic valve S8 low 

current(open circuit) 

Refer to3.5.7.23 DTC P099E P099F 

P1605 

EMM Data mismatch 

P1610 

EMM communication error 

P1611 

EMM Data error 

Refer to3.5.7.12 DTC P1605 P1610 P1611

U0100 

EMS CAN signal is not used ,these CAN 

signal is necessary for TCU 

U0121 

CAN signal of brake system ECU 

(ABS/ESP/TCS) can not used , some 

CAN signal is necessary for TCU running

U0146 

Lost with Gateway communication 

U0401 

EMS CAN signal is over range or invalid, 

these CAN signal is necessary for TCU 

U0415 

CAN signal of brake system ECU 

(ABS/ESP/TCS) is over the range or 

invalid , some CAN signal is necessary 

for TCU running 

Refer to3.5.7.28 DTC U0100U0121 

U0146 U0401 U0415 

1279

 
 

U1601 

TCU application software lost or 

damaged 

U1606 

TCU standard error –platform 

U1607 

TCU standard error - Activation derived 

standard 

U1608 

TCU VIN(Vehicle Identification code ) 

code error 

U1609 

TCU hardware (pcb) standard error 

Refer to3.5.7.29 DTC 1601U1606 U1607 

U1608 U1609 U160E 

U160E 

Doctor hardware underlying software 

reason cause special DTC 

Refer to 3.5.7.30 DTC U160E 

1280

 
 

 

3.5.7.7 Data glow table 

By reading the Data Flow Table on the fault diagnosis tester, you can inspect switches, sensors, actuators working 
state without dismantling any components. Before the control system diagnosis, observing and analyzing data is 
the first step, so that the diagnose time could be shortened. 

Note: Data under normal conditions is listed in the following table for reference only. Do not determine whether a 
part is faulty solely based on these reference values. Under normal circumstances you can compare the vehicle 
that needs to be repaired with a normal working vehicle in the same state to determine whether the current vehicle 
diagnostic data is normal or not. 

1.  Run the engine to reach normal working temperature. 

2.  Rotated ignition switch is OFF position。 

3.  Connect the fault diagnosis tester. 

4.  Rotated ignition switch in the ON position. 

5.  Select “Engine”/”Read data stream”. 

6.  Refer to the following table and inspect the data of each item. 

1.  First step: At cold engine, turn the key switch to ON position, inhibit the engine (for about 30s) 

Start - Normal/default Session

 

PowerOn Reset - ECU Reset

 

Clear (all/group/single error) - Fault memory 

 

Read (environment data) - Fault memory 

 

Read (all identified - SAE J2012) - Fault memory 

 

Read (all supported - SAE J2012) - Fault memory 

 

Read (all identified – 2Byte Hex) - Fault memory 

 

Read (all supported – 2Byte Hex) - Fault memory 

 

Read (most recent DTC) - Fault memory 

 

Read - VIN-Current

 

Read - Software Version

 

Read - Calibration Version

 

Read - Bootloader Version

 

Read - CAL-ID

 

Read - CVN

 

Request Seed - DSI Seed

 

1281

 
 

Send Key - DSI Key

 

Start - Reset Adaptive Shift Data

 

Start - Activate Adaptive Green Offset

 

Start - Reset Adaptive Tcc Data

 

Start - Activate Adaptive Tcc Green Offset

 

Start - Set Km Travelled

 

Write - VIN-Current

 

Send (Response) - Tester Present

 

Send (No Response) - Tester Present

 

 

1282