Following a trend... ECU Bricked...
Nov 25, 2009, 09:18 PM
#1
Following a trend... ECU Bricked...
Yup, following the recent thread. ECUFLASH decided to go blue screen on me DURING a flash. I tried to do exit programing state while still on, did nothing. I tried flash while still on did nothing. I tried resetting the battery did nothing, ofcourse. When I turn the key to the ON position fans kick. Meaning it is still in PROGRAMMING STATE. Took to the ECU out to BENCH it.
Following these guidelines.
I tried combinations of 8 + 12 connected to 103. 103 + 12 and 103+ 8 and just 8 +12 connected. Each time I try I get a message stating:
Kernel Get Version
Interface Close
I am at the end of my mind trying to bench this anyone else want to chip in. Maybe I am missing a step or something? Go figure it has to happens on Thanksgiving....
Following these guidelines.
Code:
If it don't work then: 1) When a flash craps out half way through: a) DO NOT TURN THE CAR OFF b) YOU CAN RESTART THE LAPTOP c) TRY REFLASHING 2) If you did a) above then (until Colby fixes the inbuilt recovery mode) you need to bench your ECU - Basically: Use http://www.roadraceengineering.com/e...-ecuwiring.htm as a reference Looks like you need to hook up: Power/Grounds: 73 = +12v? 81 = ground 82 = +12v? 93 = ground 104 = +12v? Just ensure the "power pins" have +12v and the continutity between the ground pins and chassis is 0ohms: To OBD connector: 90 = CANH 91 = CANL 80 = Kline 103 = pin 8 or 12 ??? If in doubt I would start by measuring the voltage output on the pins you will be "emulating". And also measuring the continuity between the OBD and ECU harness for the OBD connections. A friend has done this and was able to recover their ECU
Code:
Pin 8 or 12 on the obd plug IS NOT connected to pin 103 on the ecu which is the reflash pin. i had this problem on my ecu so i had to send it to Colby (all the way from New Zealand). follow the above instructions from tephra, that should fix your problem.
Kernel Get Version
Interface Close
I am at the end of my mind trying to bench this anyone else want to chip in. Maybe I am missing a step or something? Go figure it has to happens on Thanksgiving....
Nov 25, 2009, 10:17 PM
#2
i'll ask my friend what he did...
when it blue screened - did you reboot your laptop and then retry the flash?
keeping the car ign on the whole time?
from the diagram I have - pin8 on the OBD connector should connect to pin 103 on the ECU
when it blue screened - did you reboot your laptop and then retry the flash?
keeping the car ign on the whole time?
from the diagram I have - pin8 on the OBD connector should connect to pin 103 on the ECU
Last edited by tephra; Nov 25, 2009 at 10:22 PM.
Nov 26, 2009, 07:39 AM
#4
I think I am missing a step somewhere... since sometimes I will get the ECU to read my HW Version and ECU HW # and then start to continue but then it says "interface closed" and stop there. So it's like almost working, but just not all there.
Nov 26, 2009, 09:03 AM
#6
So this is what I get from the log.
As far I get on the bench...
As far I get on the bench...
[12:00:58.720] J2534 API Version: 04.04
[12:00:58.720] J2534 DLL Version: 0.50.2598 (DEBUG) Jun 26 2009 15:02:29
[12:00:58.720] Device Firmware Version: 1.10.2658
[12:00:58.932] -- loading kernel --
[12:00:58.932] -- connecting to kernel --
[12:00:58.932] kernel get version
[12:00:59.306] ECU HW part number : 1860A978
[12:00:59.330] ECU SW part number : 1860A97903
[12:00:59.349] -- unlocking ECU --
[12:00:59.349] starting session...
[12:00:59.365] requesting seed...
[12:00:59.388] sending key...
[12:00:59.916] interface close
[12:00:59.927] interface close
[12:00:58.720] J2534 DLL Version: 0.50.2598 (DEBUG) Jun 26 2009 15:02:29
[12:00:58.720] Device Firmware Version: 1.10.2658
[12:00:58.932] -- loading kernel --
[12:00:58.932] -- connecting to kernel --
[12:00:58.932] kernel get version
[12:00:59.306] ECU HW part number : 1860A978
[12:00:59.330] ECU SW part number : 1860A97903
[12:00:59.349] -- unlocking ECU --
[12:00:59.349] starting session...
[12:00:59.365] requesting seed...
[12:00:59.388] sending key...
[12:00:59.916] interface close
[12:00:59.927] interface close
Last edited by Clipse3GT; Nov 26, 2009 at 09:28 AM.
Trending Topics
Nov 26, 2009, 11:14 AM
#9
Former Sponsor
iTrader: (2)
Join Date: Sep 2009
Location: california
Posts: 189
Likes: 0
Received 0 Likes
on
0 Posts
you get further than i do mine stops at kernel read interface closed lol just go on tactrix website its right there.
http://www.tactrix.com/product_info....products_id=50
http://www.tactrix.com/product_info....products_id=50
Nov 26, 2009, 01:03 PM
#10
Thanks mate!
I will overnite/same day it to him.
We really need to figure out how to bench the ECU properly.
There is probably a extra step we are missing form the recipe we have up top.
There is probably a jumper configuration that switches it out of program state or you have to flip a DIP switch in the ECU.
I will overnite/same day it to him.
We really need to figure out how to bench the ECU properly.
There is probably a extra step we are missing form the recipe we have up top.
There is probably a jumper configuration that switches it out of program state or you have to flip a DIP switch in the ECU.
