 |
RomRaiderOpen Source ECU Tools |
|
RomRaider
Documentation
Community
Developers
|
|
Page 1 of 1
|
[ 2 posts ] |
|
| Author |
Message |
|
Alan M
|
Post subject: ECUflash reading issue on FSTI 2005 JDM model Posted: Tue Feb 23, 2021 11:29 pm |
|
 |
| Newbie |
Joined: Tue Feb 23, 2021 11:17 pm Posts: 1
|
|
Hi all!! Hopefully someone can shed some light on my query and I have the right arena/forum for help. This is my first post in years as my old account hasn't been opened for a while and I couldn't get it active. Long story short, I've been away from Subarus for a couple of years but was tempted back from VAG by a spotless FSTI (and having four children so needed the room). I've mapped and logged my old WRX and STI Impreza with no issues with the old ECUflash setup I had and the Tactrix cable. Trouble is that setup with the older version doesn't like the FSTI and neither does a newer install of ECUflash when I tried that. When I read the ECU or attempt to the read stops after a few seconds. This happens on both installs on ECU Flash. I'll add the print screen info below. Any help would be greatly received. Just to add I've been looging with Romraider with the intention of scaling my MAF before scaling injectors. MAF work using the CL spreadsheet has been great but I'm kinda stuck at this point. Anyway read details below (a couple of attempts made as can be seen) - Older version of Ecuflash
[22:48:07.867] EcuFlash Version 1.44.3721 [22:48:07.867] OS Version Windows 7 [22:48:07.867] Qt Version 4.8.0 [22:48:07.883] 63 memory models read. [22:48:07.883] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata [22:48:07.977] 507 ROM metadata models scanned. [22:48:07.977] checksum module "subarudbw" loaded. [22:48:07.977] checksum module "mitsucan" loaded. [22:48:07.977] checksum module "mitsuh8" loaded. [22:48:07.977] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded. [22:48:07.977] patch module "Mitsu CAN RAM Parameter Logging" loaded. [22:48:07.977] flashing tool "wrx02" loaded. [22:48:07.977] flashing tool "wrx04" loaded. [22:48:07.977] flashing tool "sti04" loaded. [22:48:07.977] flashing tool "sti05" loaded. [22:48:07.977] flashing tool "mitsukernel" loaded. [22:48:07.977] flashing tool "mitsukernelocp" loaded. [22:48:07.977] flashing tool "mitsubootloader" loaded. [22:48:07.977] flashing tool "shbootmode" loaded. [22:48:07.977] flashing tool "shaudmode" loaded. [22:48:07.992] flashing tool "subarucan" loaded. [22:48:07.992] flashing tool "subarucand" loaded. [22:48:07.992] flashing tool "mitsucan" loaded. [22:48:56.935] using metadata XML ID read_sti05 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_sti05.xml [22:48:56.967] J2534 API Version: 04.04 [22:48:56.967] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:48:56.967] Device Firmware Version: 1.17.4869 [22:48:56.967] Device Serial Number: TAbUZ8mP [22:49:01.473] kernel get version [22:49:01.676] interface close [22:49:01.707] J2534 API Version: 04.04 [22:49:01.707] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:49:01.707] Device Firmware Version: 1.17.4869 [22:49:01.707] Device Serial Number: TAbUZ8mP [22:49:02.019] VIN read not supported [22:49:02.128] interface close [22:49:02.159] J2534 API Version: 04.04 [22:49:02.159] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:49:02.159] Device Firmware Version: 1.17.4869 [22:49:02.159] Device Serial Number: TAbUZ8mP [22:49:02.347] SSM2 init [22:49:02.487] SSM2 ECU ID is 3B02594216 [22:49:02.565] Requesting Seed... [22:49:02.612] Sending Key... [22:49:03.236] interface close [22:49:03.251] interface close [22:49:23.508] using metadata XML ID read_sti05 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_sti05.xml [22:49:23.539] J2534 API Version: 04.04 [22:49:23.539] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:49:23.539] Device Firmware Version: 1.17.4869 [22:49:23.539] Device Serial Number: TAbUZ8mP [22:49:25.929] kernel get version [22:49:26.132] interface close [22:49:26.163] J2534 API Version: 04.04 [22:49:26.163] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:49:26.163] Device Firmware Version: 1.17.4869 [22:49:26.163] Device Serial Number: TAbUZ8mP [22:49:26.350] interface close [22:49:26.382] J2534 API Version: 04.04 [22:49:26.382] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:49:26.382] Device Firmware Version: 1.17.4869 [22:49:26.382] Device Serial Number: TAbUZ8mP [22:49:26.553] SSM2 init [22:49:26.959] SSM2 init [22:49:27.364] SSM2 init [22:49:27.770] SSM2 init [22:49:28.176] SSM2 init [22:49:28.581] SSM2 init [22:49:28.987] SSM2 init [22:49:29.392] SSM2 init [22:49:29.798] SSM2 init [22:49:30.204] SSM2 init [22:49:30.718] interface close [22:49:30.734] interface close [22:49:55.249] using metadata XML ID read_sti04 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_sti04.xml [22:49:55.280] J2534 API Version: 04.04 [22:49:55.280] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:49:55.280] Device Firmware Version: 1.17.4869 [22:49:55.280] Device Serial Number: TAbUZ8mP [22:49:57.791] kernel get version [22:49:57.994] interface close [22:49:58.025] J2534 API Version: 04.04 [22:49:58.025] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:49:58.025] Device Firmware Version: 1.17.4869 [22:49:58.025] Device Serial Number: TAbUZ8mP [22:49:58.212] interface close [22:49:58.243] J2534 API Version: 04.04 [22:49:58.243] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:49:58.243] Device Firmware Version: 1.17.4869 [22:49:58.243] Device Serial Number: TAbUZ8mP [22:49:58.415] SSM2 init [22:49:58.820] SSM2 init [22:49:59.226] SSM2 init [22:49:59.632] SSM2 init [22:50:00.037] SSM2 init [22:50:00.443] SSM2 init [22:50:00.848] SSM2 init [22:50:01.254] SSM2 init [22:50:01.660] SSM2 init [22:50:02.065] SSM2 init [22:50:02.580] interface close [22:50:02.596] interface close [22:51:03.853] using metadata XML ID read_sti05 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_sti05.xml [22:51:03.884] J2534 API Version: 04.04 [22:51:03.884] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:51:03.884] Device Firmware Version: 1.17.4869 [22:51:03.884] Device Serial Number: TAbUZ8mP [22:51:07.840] kernel get version [22:51:08.043] interface close [22:51:08.074] J2534 API Version: 04.04 [22:51:08.074] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:51:08.074] Device Firmware Version: 1.17.4869 [22:51:08.074] Device Serial Number: TAbUZ8mP [22:51:08.261] interface close [22:51:08.292] J2534 API Version: 04.04 [22:51:08.292] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59 [22:51:08.292] Device Firmware Version: 1.17.4869 [22:51:08.292] Device Serial Number: TAbUZ8mP [22:51:08.464] SSM2 init [22:51:08.870] SSM2 init [22:51:09.275] SSM2 init [22:51:09.681] SSM2 init [22:51:10.086] SSM2 init [22:51:10.492] SSM2 init [22:51:10.898] SSM2 init [22:51:11.303] SSM2 init [22:51:11.709] SSM2 init [22:51:12.114] SSM2 init [22:51:12.629] interface close [22:51:12.645] interface close
|
|
| Top |
|
 |
|
bludgod
|
Post subject: Re: ECUflash reading issue on FSTI 2005 JDM model Posted: Wed Feb 24, 2021 10:23 am |
|
 |
| Moderator |
 |
Joined: Sat Jul 06, 2013 12:55 pm Posts: 3297 Location: NI
|
|
are you sure your using the latest version of ECUFlash with the latest drivers? STI04 should be right way to read it.
When you join your greens and key on does the car go into test mode OK you can hear the fans cycling etc. ? If not sometimes there other set of greens haven't been hooked up at the factory (they are on the passenger side lower dash just behind the top of the carpet area).
Can you log the car OK?
_________________
Good luck and may the logs be ever in your favour!
|
|
| Top |
|
 |
|
Page 1 of 1
|
[ 2 posts ] |
|
Who is online |
Users browsing this forum: No registered users and 2 guests |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|
|
|