ECUFlash - Getting close!

[Td-d]

Hey guys - heads up - the BRZ roms have an extra checksum group relative to the older roms, and RR still needs to be edited to manage this. Use Ecflash to fix he checksum for the moment.


Sent from my iPad using Tapatalk HD

[EAGLE5]

I re-flashed with the newest version given. Worked well. Before I flashed, I opened up ROM Raider and saved, fixed the checksum, then opened up a hex editor and zeroed the date. That got ROM Raider happy and EcuFlash happy. The car now reads and writes fine, so I image in made the ECU happy too. I'll try now just zeroing the date and see if it still works on an e85 flash. Fingers crossed.

[stugray]

Originally Posted by jsimon7777

My intention is to make a guide for this to make it easier for others.

This is exactly what is needed. I have serious software/hardware experience, and reading some of the traffic on this thread has made me hesitate from messing with my car. It is my DD.

I have 'flashed' new software to $500Million NASA spacecraft (when millions of miles away) and this still scares me.....

[bfrank1972]

Originally Posted by stugray

This is exactly what is needed. I have serious software/hardware experience, and reading some of the traffic on this thread has made me hesitate from messing with my car. It is my DD.

I have 'flashed' new software to $500Million NASA spacecraft (when millions of miles away) and this still scares me.....

Lol! Ok sorry for off topic but I can't stand my curiosity, what do you do for a living???


Sent from my iPad using Tapatalk - now Free

[stugray]

what do you do for a living???

Spacecraft Test Engineer - Command & data handling (C&DH) for Deep impact, Stardust, Genesis, etc...

that should have made you poke around rather than sit still hesitating

When you do it for a living, it seems more like a chore to worry about UN-bricking your DD....

My primary job is writing procedures for this very task. I would be willing to help do so, but just have not seen a clearly worded step by step for this process so far.

[bfrank1972]

Originally Posted by stugray

Spacecraft Test Engineer - Command & data handling (C&DH) for Deep impact, Stardust, Genesis, etc...

When you do it for a living, it seems more like a chore to worry about UN-bricking your DD....

My primary job is writing procedures for this very task. I would be willing to help do so, but just have not seen a clearly worded step by step for this process so far.

I envy your career.

About to embark on this myself - documentation pulling together everything we know so far would be handy. More than willing to help out with that myself once I get my Tactrix cable in...

[EAGLE5]

Installed the latest EcuFlash beta, or at least I ran the installer, but it didn't take. I deleted the EcuFlash folder and ran the newest beta installer again, this time with success. Put in the 1c ZA1JA01C definition and opened the Vishnu ROM. It said the checksum needed fixing and so I fixed and tried to save, but the file would not write. Tried 5 times with no success. Then I opened in ROM Raider and fixed the checksum. The file would then open in ecuflash, but still give a checksum error. I closed ecuflash and used a hexeditor to ffffff out the date in the ROM, as suggested by VGI at http://www.ft86club.com/forums/showp...&postcount=314 and then I opened the ROM in ecuflash without any checksum errors. I then flashed the vishnu ROM successfully with no checksum errors. The ROM reads out and writes peachy keen.

What went wrong in the newest version?
1. It would not install over the older version until I deleted the EcuFlash folder.
2. It would not save the ROM as a bin.

What made it work?
1. Fix checksums in romraider.
2. fffff out the date at 0x0013F5CC-0x0013F5CF
3. Make sure I had the right definition: https://raw.github.com/TD-D/SubaruDe...Z/ZA1JA01C.xml (thanks tdd!)

I cross posted to the ROM Raider forum thread.

I am running OpenPort 2.0 rev E on WinXP.

[ztan]

Will be interested to see datalogs with all the knock data.

I've gone back to my stock ROM from the Vishnu 1.3x maps (with the lowered knock correction advance tables) after getting quite a lot of knock in the 2000-3800 range with 0.5-1.0 load. No knock at WOT, but a bit of daily driving was pulling my IAM down.

I'm going to back up to scaling injectors and MAF before trying other maps again.
In RR, I've got defs for "Injector scaling" and "Injector scaling BRZ" - does anyone know if these are for port and direct respectively or how best to go about scaling these seperately?
Datalogging, I'm pretty sure the FFF887C8 address logs port injection, will have to try some of the other addresses to see where direct injection data lives unless someone has it to hand.

[Td-d]

Duplicate post

[Td-d]

Originally Posted by ztan

Will be interested to see datalogs with all the knock data.

I've gone back to my stock ROM from the Vishnu 1.3x maps (with the lowered knock correction advance tables) after getting quite a lot of knock in the 2000-3800 range with 0.5-1.0 load. No knock at WOT, but a bit of daily driving was pulling my IAM down.

I'm going to back up to scaling injectors and MAF before trying other maps again.
In RR, I've got defs for "Injector scaling" and "Injector scaling BRZ" - does anyone know if these are for port and direct respectively or how best to go about scaling these seperately?
Datalogging, I'm pretty sure the FFF887C8 address logs port injection, will have to try some of the other addresses to see where direct injection data lives unless someone has it to hand.

I think both are port scaling - the one I defined originally has the same logic that I've seen over and over in the roms - but it was pointed out o me ht the other value is that defined by oft and brzedit as the scaling. I would be interested to hear feedback from someone whether my original scaling does the job.

If you guys can put together a request list of parameters required, I can start trawling around for addresses (once I'm back from holiday )



Sent from my iPad using Tapatalk HD

[vgi]

Originally Posted by stugray

My primary job is writing procedures for this very task. I would be willing to help do so, but just have not seen a clearly worded step by step for this process so far.

it would be awesome if you could write a clearly worded step by step for this process as you go since it would be new experience for you.

I would suggest reading this full thread first:
http://www.romraider.com/forum/viewtopic.php?f=8&t=8475

two important things to keep in mind:
- When installing new version of EcuFlash before the install plug in the Taxtrix cable as the EcuFlash will update its firmware.
- When using EcuFLash, connect the cable, click on 'read rom' (or write), the prompt will ask you to turn on the ignition - do turn on the ignition, wait until the bipping stops (i think 5 bips), then wait another about 6 seconds, only then click on that pop up box confirming that the iginition is on (thank you @jamesm for this tip)

[ztan]

Originally Posted by Td-d

I think both are port scaling - the one I defined originally has the same logic that I've seen over and over in the roms - but it was pointed out o me ht the other value is that defined by oft and brzedit as the scaling. I would be interested to hear feedback from someone whether my original scaling does the job.

If you guys can put together a request list of parameters required, I can start trawling around for addresses (once I'm back from holiday )

Thanks Td-d.
Interested in the direct v. port info because:
Looking at injector scaling, I did the following:
Engine up to temp
ECU reset (stock ROM except IAM=1.0)
Started up and logged idle at 20Hz
Discarded initial data with fueling status 1 (OL not up to temp) and logged with no accelerator input.
Divided data into
first half (IPW1>0) - I assume this means port injection on. Mean STFT+LTFT = -7.16%
second half (IPW1=0) - I assume this means port injection off. Mean STFT+LTFT = +2.14%
I'm not sure what controls the injection switch over with other parameters all logging similarly.

I can imagine that fueling control may be difficult if each set of injectors is skewed in different directions, especially at breakpoints where port/direct fractions switch.

[jamesm]

Originally Posted by ztan

Thanks Td-d.
Interested in the direct v. port info because:
Looking at injector scaling, I did the following:
Engine up to temp
ECU reset (stock ROM except IAM=1.0)
Started up and logged idle at 20Hz
Discarded initial data with fueling status 1 (OL not up to temp) and logged with no accelerator input.
Divided data into
first half (IPW1>0) - I assume this means port injection on. Mean STFT+LTFT = -7.16%
second half (IPW1=0) - I assume this means port injection off. Mean STFT+LTFT = +2.14%
I'm not sure what controls the injection switch over with other parameters all logging similarly.

I can imagine that fueling control may be difficult if each set of injectors is skewed in different directions, especially at breakpoints where port/direct fractions switch.

i saw the same thing tuning my car for e85. i would log fueling error with the ports turned off and get corrections in one direction, then log with ports only and get different results. getting both 'in spec' independently fixed virtually every drivability problem i had prior to doing this, particularly rough idle, rpms hunting, dipping rpms coming to a stop, stumbling at tip-in, etc. all related to big swings in afr introduced by the disparity in required trim when the switchover happens between injection modes.

you can use the 3 port/di ratio tables to set the ratio. 100% is port only, 0% is di only.

[ztan]

Originally Posted by jamesm

i saw the same thing tuning my car for e85. i would log fueling error with the ports turned off and get corrections in one direction, then log with ports only and get different results. getting both 'in spec' independently fixed virtually every drivability problem i had prior to doing this, particularly rough idle, rpms hunting, dipping rpms coming to a stop, stumbling at tip-in, etc. all related to big swings in afr introduced by the disparity in required trim when the switchover happens between injection modes.

you can use the 3 port/di ratio tables to set the ratio. 100% is port only, 0% is di only.

Thanks.
Which table/s did you alter to affect direct injection scaling? I can see the port injector scaling easily.
Did getting this balance right also help your tip-in knock?