problems with OP2 and trying to log 06 sti. help!

User topics relating to software that logs data from ECUs

Moderator: Freon

problems with OP2 and trying to log 06 sti. help!

Postby deserted1 » Thu Jan 29, 2009 9:10 pm

2006 USDM Impreza STi.

I just got my Openport 2, granted I paid alot for just using it as a logging device. My ECU is flashed with my APV2 and a protune.

I want the ability to datalog on my car and being that I don't feel the APV2's logging is complete enough I wanted to try RomRaider's logging. Well I cannot get the OP2 to connect to my ECU, the laptop can see the OP2 and the drivers from ECUflash installed flawlessly. ECUFLash sees the OP2 and so does RomRaider.

Neither program can actually connect to my ECU, the closest I get is with ECUFlash and thats trying to read my ecu. Granted I know this wont work but still trying anything at this point.

Here is a log of the ECUFlash and what it says when trying to read the rom.

[20:03:36.687] EcuFlash Version 1.41.2483
[20:03:36.687] OS Version Windows XP
[20:03:36.687] Qt Version 4.4.0
[20:03:36.703] 26 memory models read.
[20:03:36.703] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[20:03:36.921] 342 ROM metadata models scanned.
[20:03:36.921] checksum module "subarudbw" loaded.
[20:03:36.921] checksum module "mitsucan" loaded.
[20:03:36.921] flashing tool "wrx02" loaded.
[20:03:36.921] flashing tool "wrx04" loaded.
[20:03:36.921] flashing tool "sti04" loaded.
[20:03:36.921] flashing tool "sti05" loaded.
[20:03:36.921] flashing tool "mitsukernel" loaded.
[20:03:36.921] flashing tool "mitsukernelocp" loaded.
[20:03:36.921] flashing tool "mitsubootloader" loaded.
[20:03:36.921] flashing tool "shbootmode" loaded.
[20:03:37.015] flashing tool "shaudmode" loaded.
[20:03:37.031] flashing tool "subarucan" loaded.
[20:03:37.031] flashing tool "mitsucan" loaded.
[20:04:32.484] J2534 API Version: 04.04
[20:04:32.484] J2534 DLL Version: 0.50.2464 Jan 29 2009 10:58:58
[20:04:32.484] Device Firmware Version: 1.05.2463
[20:04:40.484] kernel get version
[20:04:40.859] SSM2 init
[20:04:41.000] SSM2 ECU ID is 43 12 59 40 06
[20:04:41.093] Requesting Seed...
[20:04:41.140] Sending Key...
[20:04:41.187] interface close
[20:04:41.203] interface close



Can anyone help me figure out whey when I try to connect RomRaider Logger to my ECU, it just says Unable to send ECU INIT - check cable and ensure ignition is on. It just refuses to connect.
deserted1
 
Posts: 11
Joined: Thu Jan 29, 2009 8:12 pm

Re: problems with OP2 and trying to log 06 sti. help!

Postby deserted1 » Fri Jan 30, 2009 4:31 pm

bueller, bueller?
deserted1
 
Posts: 11
Joined: Thu Jan 29, 2009 8:12 pm

Re: problems with OP2 and trying to log 06 sti. help!

Postby Turbo Dan » Wed Feb 11, 2009 10:15 pm

I've had the same issues and message on several different cars I've attempted to use the OP2 and EcuFlash on. I'm in the process of trying to trouble shoot it myself but would be very interested if any one else has come across this issue and possibly found a fix.

Thanks,
Dan
Turbo Dan
 
Posts: 2
Joined: Wed Feb 11, 2009 10:02 pm

Re: problems with OP2 and trying to log 06 sti. help!

Postby Corn » Thu Jul 21, 2011 8:30 pm

Hi,

i'm new here but i had similar problem with my 06 sti, i connected the green connectors under dash on drivers side nearby ashtray and it put car into diagnostic mode. After that i could read my ecu with ecuflash. Co-drivers side was already connected in my case.

Hope this helps or you have figured out it yourself earlier.
Corn
 
Posts: 1
Joined: Thu Jul 21, 2011 8:23 pm

Re: problems with OP2 and trying to log 06 sti. help!

Postby radsdau » Sun Jul 24, 2011 3:23 pm

Normally if it fails after the message 'Sending Key...' it means it's been locked, normally by EcuTek or Cobb.
radsdau
 
Posts: 674
Joined: Wed Feb 08, 2006 6:56 pm


Return to Data Logging Software

Who is online

Users browsing this forum: No registered users and 9 guests

cron