 |
RomRaiderOpen Source ECU Tools |
|
RomRaider
Documentation
Community
Developers
|
|
Page 1 of 1
|
[ 5 posts ] |
|
| Author |
Message |
|
potato5
|
Post subject: working on manual tune Posted: Wed Apr 30, 2025 12:50 am |
|
 |
| Newbie |
Joined: Wed Apr 30, 2025 12:24 am Posts: 3
|
|
Hello everyone, I've been working on trying to get a manual tune working for my 2005 usdm outback 30r, I reached out to a few lad but also decided to take the project on late one night while staring into the void with chatGPT. here is a short summery of what we have done so far I've given it my rom + roms from similar year 2005 2006 legacy and outback models all with EZ30 engine and automatic or manual transmissions from ADM EDM and JDM GPT had found key areas where the roms were different and similar and marked down 4 sections shared by all manual and auto roms where the code lived in the same address but was different between auto and manual. I continued teaching it as best as I could the wiring differences between auto and manual to it could have a better understanding. We tried building a rom with the what we learned but quickly found an internal id code miss match that a test write with ecuflash didnt like. We then pivoted and included USDM legacy GT manual and automatic roms and chatGPT rescanned everything again finding that the structure of ADM EDM and JDM roms matched but was different from USDM roms though all used the same or similar code to identify manual or automatic operation. our final version of our rom used my original USDM outback 30R rom with manual logic transplanted from a same year usdm legacy GT. I recognize that I may still be vary ignorant but to me I see no reason this flash shouldn't work if the changes we made to my original rom are the same changes we see between automatic and manual versions of the same vehicle across markets.
ive attached a copy of my rom if anyone wants to see
|
|
| Top |
|
 |
|
bludgod
|
Post subject: Re: working on manual tune Posted: Wed Apr 30, 2025 11:56 am |
|
 |
| Moderator |
 |
Joined: Sat Jul 06, 2013 8:55 am Posts: 3264 Location: NI
|
|
have you actually flashed and tested this though or is it all theory at this point?
_________________
Good luck and may the logs be ever in your favour!
|
|
| Top |
|
 |
|
potato5
|
Post subject: Re: working on manual tune Posted: Wed Apr 30, 2025 12:09 pm |
|
 |
| Newbie |
Joined: Wed Apr 30, 2025 12:24 am Posts: 3
|
|
I haven't flashed this one yet, I'm sourcing a second ECU in case I brick mine and I'm also looking for a new cable for my tactrix. For now this is all theory and I'd like to test flash soon. I'm just looking for extra input for anything I may have missed. I will absolutely be posting the ROM if it works once I get my hands on another ecu.
|
|
| Top |
|
 |
|
potato5
|
Post subject: Re: working on manual tune Posted: Mon May 19, 2025 4:28 pm |
|
 |
| Newbie |
Joined: Wed Apr 30, 2025 12:24 am Posts: 3
|
|
ok so ive been trying to flash this tune on my car for a few days now and i keep getting J2534 ERR TIMEOUT ive replaced cables, tried 2 tactrix units reinstalled ecuflash and drivers over and over with laptop reboots between test connectors are plugged in an tight i can read my stock rom, i can use the compare and test write functions i haven't tried reflashing my stock rom once i open my tuned rom i cannot flash, test write, compare, or even read the stock rom according to chatGPT it might be due to my definitions being experimental and in the definition file can see its using subarucan flash method
here is a portion of my log [21:46:56.620] D2ZX004B (255 tables) inheriting 32BITBASE (1237 tables) [21:46:56.662] using metadata XML ID D2ZX004B from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/subaru/Outback 3.0R/D2ZX004B 2005 USDM Outback 3.0R AT.xml which inherits XML ID 32BITBASE from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/subaru/Bases/32BITBASE.xml [21:46:56.662] ---notes for 32BITBASE--- 2014/06/20 [Tactrix] Tactrix definition auto cleaned|merged w/ RomRaiderGitHubAlphaMay2014. ---notes for D2ZX004B--- 2012/11/30 [Tactrix] Experimental definition from RomRaider. Removed D2TC001P definition. 2012/12/07 [Tactrix] Visually examined a portion of tables for obvious errors, but no in-car verification has been done. Standardized file name. Added user level 2 to Primary Open Loop Fueling as some addresses are incorrect. 2014/05/22 [Tactrix] Tactrix definition auto cleaned|merged w/ RomRaiderGitHubAlphaMay2014.
[21:47:10.969] J2534 API Version: 04.04 [21:47:10.969] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31 [21:47:10.969] Device Firmware Version: 1.17.4869 [21:47:10.969] Device Serial Number: TAuVekZ3 [21:47:13.753] kernel get version [21:47:13.765] kernel already resident - skipping kernel load [21:47:13.980] kernel get version [21:47:13.991] kernel version is : OpenECU Subaru SH7058 DUAL Kernel V1.07 [21:47:13.991] reading kernel comm buffer size [21:47:13.995] comm buffer size set to 512 [21:47:13.995] reading kernel flash buffer size [21:47:14.002] flash buffer size set to 4096 [21:47:14.002] -- test flashing image to ECU memory -- [21:47:14.404] -- comparing ECU flash memory pages to image file -- [21:47:14.404] seg start len ecu CRC32 img CRC32 same? [21:47:14.421] FB01 00000000 00001000 08FDE5BC 08FDE5BC YES [21:47:14.438] FB02 00001000 00001000 8F101821 8F101821 YES [21:47:14.452] FB03 00002000 00001000 D99A6BC7 D99A6BC7 YES [21:47:14.472] FB04 00003000 00001000 D72EEE1F D72EEE1F YES [21:47:14.489] FB05 00004000 00001000 6130F629 6130F629 YES [21:47:14.507] FB06 00005000 00001000 57A71D61 57A71D61 YES [21:47:14.524] FB07 00006000 00001000 CB3F2AB3 CB3F2AB3 YES [21:47:14.541] FB08 00007000 00001000 C47E5C8F C47E5C8F YES [21:47:14.791] FB09 00008000 00018000 5FA55A62 5FA55A62 YES [21:47:15.125] FB10 00020000 00020000 F73C2CA8 F73C2CA8 YES [21:47:15.458] FB11 00040000 00020000 7623322D 7623322D YES [21:47:15.786] FB12 00060000 00020000 5A6F2546 5A6F2546 YES [21:47:16.120] FB13 00080000 00020000 CDC14913 CDC14913 YES [21:47:16.454] FB14 000A0000 00020000 154803CC 154803CC YES [21:47:16.792] FB15 000C0000 00020000 FD606F40 FD606F40 YES [21:47:17.125] FB16 000E0000 00020000 B5AABED0 B5AABED0 YES [21:47:17.125] flash image is identical! exiting without writing to flash. [21:47:17.125] interface close [21:47:17.129] interface close [21:48:19.407] J2534 API Version: 04.04 [21:48:19.407] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31 [21:48:19.407] Device Firmware Version: 1.17.4869 [21:48:19.407] Device Serial Number: TAuVekZ3 [21:48:21.236] kernel get version [21:48:21.436] J2534 error [ERR_TIMEOUT]. [21:48:21.636] J2534 error [ERR_TIMEOUT]. [21:48:22.046] J2534 error [ERR_TIMEOUT]. [21:48:22.456] J2534 error [ERR_TIMEOUT]. [21:48:22.861] J2534 error [ERR_TIMEOUT]. [21:48:23.261] J2534 error [ERR_TIMEOUT]. [21:48:23.670] J2534 error [ERR_TIMEOUT]. [21:48:24.080] J2534 error [ERR_TIMEOUT]. [21:48:24.497] J2534 error [ERR_TIMEOUT]. [21:48:24.906] J2534 error [ERR_TIMEOUT]. [21:48:25.318] J2534 error [ERR_TIMEOUT]. [21:48:25.732] J2534 error [ERR_TIMEOUT]. [21:48:26.145] J2534 error [ERR_TIMEOUT]. [21:48:26.555] J2534 error [ERR_TIMEOUT]. [21:48:26.971] J2534 error [ERR_TIMEOUT]. [21:48:27.390] J2534 error [ERR_TIMEOUT]. [21:48:27.797] J2534 error [ERR_TIMEOUT]. [21:48:28.209] J2534 error [ERR_TIMEOUT]. [21:48:28.617] J2534 error [ERR_TIMEOUT]. [21:48:28.832] interface close [21:48:28.833] interface close
|
|
| Top |
|
 |
|
bludgod
|
Post subject: Re: working on manual tune Posted: Tue May 20, 2025 1:29 pm |
|
 |
| Moderator |
 |
Joined: Sat Jul 06, 2013 8:55 am Posts: 3264 Location: NI
|
|
you'll probably have to change the flash method to match what the ECU is expecting, also worth trying to change 1 or 2 values in the stock file and see if you can flash that on successfully.
_________________
Good luck and may the logs be ever in your favour!
|
|
| Top |
|
 |
|
Page 1 of 1
|
[ 5 posts ] |
|
Who is online |
Users browsing this forum: No registered users and 5 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
|
|
|