Problem with EcuFlash

User topics relating to hardware that interfaces PCs to ECUs

Moderator: Freon

Problem with EcuFlash

Postby tanxunhong » Sun Jun 19, 2011 7:05 am

I just started playing with this stuff n met with some problem.
do need some help from you guys.
I am driving an 07 euro STI DBW.
Using Asus Win 7 laptop With OP 2.0

No problem using Romraider to do logging.
but when i try using ecuflash i met with some problem.

This is what i do,
1. Plug OBD cable n connect to USB port.
2. On ignition switch n click EcuFlash.
3. click Read From Ecu. & problem came.

This is what it shows,

[20:52:16.714] EcuFlash Version 1.43.3150
[20:52:16.714] OS Version Windows 7
[20:52:16.714] Qt Version 4.6.2
[20:52:16.714] 62 memory models read.
[20:52:16.730] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[20:52:16.855] 354 ROM metadata models scanned.
[20:52:16.855] checksum module "subarudbw" loaded.
[20:52:16.855] checksum module "mitsucan" loaded.
[20:52:16.855] checksum module "mitsuh8" loaded.
[20:52:16.855] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[20:52:16.855] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[20:52:16.855] flashing tool "wrx02" loaded.
[20:52:16.855] flashing tool "wrx04" loaded.
[20:52:16.855] flashing tool "sti04" loaded.
[20:52:16.855] flashing tool "sti05" loaded.
[20:52:16.855] flashing tool "mitsukernel" loaded.
[20:52:16.855] flashing tool "mitsukernelocp" loaded.
[20:52:16.855] flashing tool "mitsubootloader" loaded.
[20:52:16.855] flashing tool "shbootmode" loaded.
[20:52:16.855] flashing tool "shaudmode" loaded.
[20:52:16.855] flashing tool "subarucan" loaded.
[20:52:16.855] flashing tool "mitsucan" loaded.
[20:52:49.038] J2534 API Version: 04.04
[20:52:49.038] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[20:52:49.038] Device Firmware Version: 1.11.3137
[20:52:49.038] Device Serial Number: TAL2Wwkk
[20:52:50.391] kernel get version
[20:52:50.594] interface close
[20:52:50.625] J2534 API Version: 04.04
[20:52:50.625] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[20:52:50.625] Device Firmware Version: 1.11.3137
[20:52:50.625] Device Serial Number: TAL2Wwkk
[20:52:51.077] VIN: JF1GDFKH36G055402
[20:52:51.202] CVN: 35C34F53
[20:52:51.311] interface close
[20:52:51.327] J2534 API Version: 04.04
[20:52:51.327] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[20:52:51.327] Device Firmware Version: 1.11.3137
[20:52:51.327] Device Serial Number: TAL2Wwkk
[20:52:51.499] SSM2 init
[20:52:51.639] SSM2 ECU ID is 4342594006
[20:52:51.717] Requesting Seed...
[20:52:51.764] Sending Key...
[20:52:52.388] interface close
[20:52:52.388] interface close





Can anybody tell me what is happening?

please englighten me. thanks to all bros out there.
tanxunhong
 
Posts: 7
Joined: Sun Jun 19, 2011 3:28 am

Re: Problem with EcuFlash

Postby radsdau » Sun Jun 19, 2011 5:51 pm

2 possibilities:
1. You are using the wrong method to hook up to the ECU
2. The ECU is locked, perhaps by EcuTeK
Check the green test mode connectors as well, although I'd expect the symptom of that problem to be slightly different.
radsdau
 
Posts: 674
Joined: Wed Feb 08, 2006 6:56 pm

Re: Problem with EcuFlash

Postby tanxunhong » Sun Jun 19, 2011 7:26 pm

Firstly, thanks for replying.

If the ecu is lock, it can datalog too? hmm.
so if the ecu is not lock by ecutek, what am i missing in hooking up with the ecu?
hope you can englighten me. thanks
tanxunhong
 
Posts: 7
Joined: Sun Jun 19, 2011 3:28 am

Re: Problem with EcuFlash

Postby radsdau » Mon Jun 20, 2011 3:45 pm

Data logging is ok on a locked ECU; no problems there.
If it is not locked (and you are sure of this), then the only probable issues are on a non-CAN ECU, if the green test mode connectors are not joined (bear in mind on some vehicles there are 2 sets of these; just make sure the car goes into 'test mode', or used ROMRaider to check; it logs 'test mode').
If it's a CAN ECU, there is no need to go into test mode first. If it doesn't hook up, then the ECU is locked, or there is a problem with the installation of the OP2 cable drivers and/or ECUFlash.
radsdau
 
Posts: 674
Joined: Wed Feb 08, 2006 6:56 pm


Return to Interface Hardware

Who is online

Users browsing this forum: No registered users and 14 guests