Home ] Up ] magnet-engl ] O-2En ] [ prius05 ] TesterII ] Subaru ] AEvsAFS ] DLC Honda ] Vf1 ] Tools2 ] gx470 ] O2S CR_V ] VVt ] MB ] D4English ] G20 ] P0606e ]

Diagnostic and repair Toyota Prius a 2005 and Solara a 2004 by usin AE PC-based Scan Tools

1362.jpg (62610 bytes)

 

I know (by RM1130U) that ECM of this Primus uses the ISO 15765-4 for communication protocol and the terminal  arrangement of the DLC3 complies with SAE J1962 and maches the ISO 15765-4 format. IMO: KWP2000 with CAN.

"The HV control ECU' and "The battery ECU" uses the ISO 9141-2 communication protocol. The terminal arrangement of the DLC3 complies with SAE J1962 and matches the ISO 9141-2 format.

1379.jpg (68936 bytes)

1480.jpg (112285 bytes)

1484.jpg (121520 bytes)

J1962 pins Adapter

I use different methods (Tools*) of diagnostics above Vehicle. For example,

- the DTCs for CAN communication concerning the brake control system can be read by connecting the SST 09843-18040 to the Tc and CG terminals of the DLC3 connector, and observing the blinking of the ECB, ABS and VSC warning light (2-digit code) (For details, see the Pub. No. RM1075U, etc.) - "good"

- "old and primitive" (photo:-) ScanGauge Tool by Linear Logic - "good"

- AE PC-based Scan Tools with Enhanced interface for Toyota/Scion/Lexus (EI03) 1995-2005

- Toyota/Lexus OEM Scan Tool (Intelligent Tester II) - "very good"

"old and primitive" ScanGauge Tool by Linear Logic

Connect by Intelligent Tester II and OBD-II, JOBD, EOBD Protocol Analyzer with CAN

ECU and HV battery

ECU HV battery

I try different ways for Diagnostic, but not have full possibility for diagnosis by AE PC-based Scan Tool :-( 

Take a look details in http://members.iatn.net/forums/read/msg.aspx?f=forum8&m=57593&fv=0&ar=0 

1_.gif (80375 bytes)

2_.gif (74802 bytes)3_.gif (85894 bytes)

hvbattery.gif (42643 bytes)

hvbattery9141_2.gif (42138 bytes)

hvcontrol.gif (41327 bytes)

I've again checked AE* on Prius a '05 and try did Diagnostic SRS.1_1942.jpg (129515 bytes)

Note. I use Documentation 2005 PRIUS REPAIR MANUAL (RM1130U) and AEs "scantooluserguide".

I not used others "devices" in this episode. For the checking (for Authenticity of results) I used separate another scanner (IT2 by Denso) and had a good and correct Results. I've performed such functions as reading the values of switches and sensors: AE report: "Display Type Information is DP" (The display is indicated by Driver/Passenger).

1. In "Live Data Grid"  I see ("Sensor Name" / "Value"):Passenger (Right) Side Buckle Switch / "..." (I don't understand "Value="...")

Here take a look at the differences in PIDs between the AE (the Lying) and IT2 (real and correct Data). Notice a difference

Srs1_1.jpg (81203 bytes)

Srs2_1.jpg (87686 bytes)

Srs3_1.jpg (85043 bytes)

2. This Car does not use PID "Passenger  Classification"!3. This Car use PID "Number of Past DTC", AE does not know these PIDs

4. If I put in the lock driver Belt, then (on the screen) I see a change Value of PID " Passenger Classification " ("NG" to None")! 

5. If I put in the lock passenger Belt, then (on the screen) I see a change Value of PID "Driver (Left) Side Buckle Switch" (Off to On)!

As I think and I sure, this "OEM Level" was not full correct. I don't need refund or observance of warranty! I not required refunding my money! I required small correction
And I try only to help this!

I earn on life by diagnostics, rather then "hackerswork"! I'm only Technician! I don't take accusations in attempt of larceny! With many Regrets.

 

 

Off. I'm supervising the electrical/electronics department in the Japan Cars aftermarket Service Shop from 1993 (for example, take a look this my articles)

Although my level of income is well less the national average, but I bought your interface twice and it seems to me I should buy the third to have an opportunity to work with Prius a 2005 MY and others Cars. I do not understand the reason of this and I consider it's wrong! I am scared I will be poorer by a few hundreds more dollars.

ONLY for Clarification the problems in (on) on above Prius I must (and will) comparing the serial data transfer use OBD-Protocol Analyzer.

Note. I did comparing the serial data transfer after breakage of interface`s second copy and only for searching reasons of program`s wrong working and interface`s wrong working.

J1962 Adapter No.2

My Tools for Diagnostic

Work Platz

On Solara I can't read DTC from SRS

I read on Toyota Solara (MCV31L-GCANKA) 2004MY the diagnostic trouble codes SRS with selfmade (amateur) device (aka J1962 pins Adapter No.1) by using short check wire and by flashing SRS-Lampe (code 73).

In spite of this AE sucsessfully connects with SRS (I can see Live Data) and normally it is connected to other systems (Live Data Grids, etc.) and reads, for example the DTC of ABS. 

log from AE No.1

Bad (?) Program

Correct log

Good (?) Program

-fast initialization

-opening of diagnostic session

81 58 F0 81 4A request (of tester) 

83 F0 58 C1 E9 8F 04 answer (of ECU)

Begin diagnosticses

82 58 F0 10 5F 39

82 F0 58 50 01 1B

Reading Codes

82 58 F0 13 81 5E

84 F0 58 53 01 99 01 BA (*DTC B1901)

read Codes without Scan Tools

1900_.jpg (90238 bytes)Read DTC SRS (B1901) on above Solara by Toyota/Lexus Inteligent TesterII.

Note. I did comparing the serial data transfer only for searching reasons of AE program`s wrong working.

Note. I bought this interface twice (price for second Copy was 200$US + 35 $USIn may 2006 I have paid  for the second  "cables" (aka Interface)  and shipping to Ukraine $235 USD. I'm scared I will be again poorer by a few more dollars... I I must byu third ... I don't understand WHY???

I check Interior and had understanding! The Quality is "Out of Range"!

May be this Cables is "made in the chinese village and with using the baby labour"!

I did check Version 4.4 on Solara and had same Results. SRS lampe is ON, ECU has DTC B1901/73, but AE Scanner report: "No Codes".

Note. The vehicle's ECM (e.g. SRS) conforms to ISO 14230 and ISO 9141-2 for communication protocol. The terminal arrangement of the DLC3 complies with SAE J1962 and meets the ISO 14230 and ISO 9141-2 format.

Dear Jay, please, correct yours serial data transfer!

Off No.2

 

Open KWP2000

Baud: 10416

Init type: Fast init

kw1: 0xE9

kw2: 0x8F

Trg: 0x58

Src: 0xF1

...

58 F1 81 58 F1 81 4B

F1 58 83 F1 58 C1 E9 8F 05

58 F1 81 58 F1 81 4B

F1 58 83 F1 58 C1 E9 8F 05

58 F1 82 58 F1 21 04 F0

F1 58 86 F1 58 61 04 02 02 01 01 3A

58 F1 81 58 F1 81 4B

F1 58 83 F1 58 C1 E9 8F 05

58 F1 82 58 F1 21 04 F0

F1 58 86 F1 58 61 04 02 02 01 01 3A

58 F1 81 58 F1 81 4B

F1 58 83 F1 58 C1 E9 8F 05

58 F1 82 58 F1 21 04 F0