Gotcha! So I should probably edit these #'s in excel for better control?

 

I beleive that's just how hex works but I'm no expert. Even if you try to set data with "=" 15.0 becomes 15.0528 and shows as 15.1 in the cell. 14.9 is 14.9333.

 

Its just the value is some calculation from a hex value.. so a fraction value calculated and converted back to hex may get rounded when converted back..

 

Yea that. ^^^

 

anything yet?


After I download that http://www.speedelement.com/images/...O8%20JM9693.hex

what do I do next?

Also I got an evo8 all I could find was the 1.28. Will that work or does it have to be 1.27

 

Download the new 1.28 version. if you have your cable already all you need to do is hook up the cable, start the software, hit the download button and follow the on screen prompts.

 

ECUFlash for dummies! this write-up is amazing. good work man...

 

I managed to get evereything to scan the ECU but for all my maps the RPM and load values are waaaaaaaay messed up.

In the RPM column its like:
191
191
191
169304
389720
347820
2000
3000
4000

And in the load it goes up to 400!

It cant be real values the car runs fine, must be backwards axis

 

Are you talking about reading the ECU rom with the cable? Your problem isn't the rom, its the definition, your Rom's definition is likely different than the one it got matched to (inherited?)

Its not too difficult to find the new ones, but you need to take down the ECU Identifier and see if it matches anything..

If your car had been reflashed with Techtom in the past, it might have a identifier that may not be in one of the definitions and Jason from Mynes (providing he has the time to still support this) can create a definition for a newly found ROM.. I can do it too, but I'm nowhere as proficient at it as these other guys, nor could I guarantee I could come up with something fast enough to make you happy. I'm in the process of working on one for another mitsubishi we did an experiment on.

 

ThANKS

 

Yep it looks like you got everything covered.. Its just odd that if you matched the ECU definition correctly, that the axis would be screwed up..

However, did ECUFlash ask you which one it is? Or did it find it automatically? if it had asked you, then it might not recognize the rom image (since it was reflashed, and likely with techtom some of the rom images used might have different identifiers not seen on any or few if any USDM model cars, which is why it might not have matched)

The best person to ask is the tuner you got your reflash from, if he does through the e-mail flashing, its possible he has your reflashed map on file and can convert it for you to use..

But I would refrain from adjusting anything, if the axes are wrong, then there are one or two other tables that could be wrong too, and it would really suck to have a no-run condition because of it..

FWIW the identifier on the external label isn't always the ECU/Rom identifier, especially if the car was brought in for any service or recall work during its warranty period. Even my car had an original 03 USDM flash, but its external labeling was something I couldn't match to anything in the USDM market..

 

I can't paste the actual map - (I'm using a vendor's product) but I will give the RPM scale just in case someone knows offhand what I'm doing wrong. One more thing, this is from the "READ FROM ECU" option:

191*
191
191
191
191
191
255996
255996
137383
39
500
1000
1500
2000
2500
3000
3500
4000*

My load values go up to 400,

The above RPM and load tables are what may happen if you load the wrong ECU identifier for the year (04 has 3 or 4 different ECU ID's*

The actual map appears normal (at least to me) and I furthermore know that the ECU was scanned correctly because rev limit was 7805, the high and low octane maps were almost identical, the figures at the left of ign and afr charts were identical to stock, and so on.

Is it possible that the ECU doesnt read the actual given RPM value, say, 191 in my case, but reads it as corresponding rows? The car runs normal in fact, really halls bookie for the slowest known EVO 8 produced (04 SSL)

Hope I didn't clutter this thread toooo much,

Thanks

 

nice description

 

Okay, so it sounds like there is no pre-existing definition for your ECU type.. At least on your computer or version of ECUFlash..

Typically when you open a map it recognizes, it just opens, it doesnt ask if you want to inherit or copy anything.. If it asked you anything like that, it means it didn't match anything..

Its pretty common to have some of the load/rpm etc.. axis definitions move around from rom versions and that is why you may see most of the table info correct, but the axis values look wrong.. Their not actually wrong, but the definition is looking for them in the wrong place.

I probably could help if I saw the map, but its likely the tuner you are dealing with has seen this already, and created a matching XML definition for it, and he can probably send it to you.

 

For everyone whos curious's information, the ECU identifier I used was wrong so the RPM/load tables were messed up. Working now!
- thanks.

Wheres my concerta