To All:

The maps were so retarded I am almost adpt to not even touch the car. It wasn't the values inside the maps that were all screwey, it was the load values and rpm values. Some of the load values went up to 20,000 (Not kidding). I was wondering if my ECUFlash definition for that car wasn't right, but according to some of the definitions I pulled off the web, it seemed right. The car previously had a UTEC, which has since been removed. It was flashed by a tuner on here (Non-block tuning tuner), and other than that, I don't know much more about the car. It has a fresh 2.3 in it, stock turbo, cams and a few other things. I would really like to get it running right, but I have never seen a map this screwed up before.

I am going to try and get a completely stock map, and load it into the car, but for some reason I am a little nervous because of the map I pulled was so fugged up. If I remember correctly, some of the values in the RPM columns went up over 200,000 rpm's. That must be one hell-uv-a revving 2.3.

What th heck could be wrong with this map? Anyone ever see this? Is is scrambled? Does his car have an STD? This Saturday I will be attempting something with it, and I think then first thing I am going to do is dump a completely stock map into it to see if it takes it... Any suggestions and/or ideas?

 

little/big endian?

 

Hmmm... Would this make everything OK (Inside the maps) and just screw up the scalings of the Loads & RPM's.. All of the values looked OK (Numbers @ loads and RPM's) except all of the Loads & RPM's.

All other cars I have done come out OK, except this specific car...

 

There are a few things that can cause that to happen, invalid definition, little endian vs big endian etc.

 

Most likely the rom's internal id number does not mach the actual id, so ecuflash uses a wrong definition. Easy fix.

 

So I looked at it again last night, and it appears that everything is OK. I have never messed with that map's xml files or anything, so i am just going to try and load in a brand new map and see what happens. This Saturday I will be doing this, so we will see what happens...

 

04 ROMs must be the most screwy. Not sure if it has anything to do with them being flashed by a tuner or not but my definitions were messed up with v 1.27/1.28 and ID was 96420008.

As soon as I use 1.29 my rom ID became 96420007 and all definitions were correct from a valid XML (I guess).

Ever since I can remember, like early 2005 when car was several months old, I could hear random loud clicking noises from the stepper area - like a half on/half off noise. Engine does not need to be on for it to happen - just ignition to "on".

I cannot confirm if this occurred before or after my first flash in Jan 05 either, ECU has some corrupt data?

My headlights also scan up and down independently when engine is cold - the car is haunted Japanese ghost engineer from factory mishap.. ooooou

 

Here is just a cut and paste of his Load (%) values:


140 160 180 200 220 240 260 280 300 320 20479.7 10913.8 20479.7 10990.6 6.25 0 40 60


And here are the RPM values (Cut and paste):


4500
5000
5500
6000
6500
7000
7500
255996
136430
255996
136398
70.3125
125
250
500



What the hell is going on here?

Is the ECU locked?

Damn, I want a motor that can rev to 255,996 rpm...

EDIT: If it matters, it's a 96420011 ROM...

Anyone have a stock ROM I can use?

 

the definition is wrong. the table address needs to be changed. you can see that its just off.

its clearly not locked - but who knows how much the rom has been changed.


edit: like others have said - it might be the wrong definition file, or somehow the romid doesnt coincide with the actual rom.

 

OK, I have to pull out the stupid card (Me, not you)on this one.....

How do I fix it?
Never had to deal with this problem before...

 

Okay, I'm a little tired of tuners altering the ECU ID's on roms to prevent "tampering" when this practice will ultimately do more harm then good.

Always make a backup of your original rom before any tuner works on your car.. **INSIST** that they save a backup and give it to you.


The image below is a quick addition that you make to the evo7base and evo9base the ECU Internal ID location is the same for most mitsubishi roms, so if you know your original ecuID, you can use this little addition to change an obscured (wrong) ecuID back.. but remember you MUST know what the right ID is already, hence why you need a backup of your rom, otherwise you'll spend quite awhile trying different values until you figure it out.

Its essential you don't modify any rom until your 100% certain your using the proper definition.

I really despise locked and/or obfuscated roms..

 

Thats a ton Malibu...

I am assuming that, since it's an 04, I will just input the 04's standard ROM ID's into that Internal ID tag until I find one that works, and the values are correct?


I am also assuming it is possible to start from scratch, by loading in a new ROM to completely overwrite the old one?

 

yeah try some 04 rom IDs, hopefully that will help.

MJ... i didn't even think tuners would be that dispicable as to change the RomIDs. Its a painfully _lame_ way of trying to protect their work. I would personally boycott any tuner that wouldn't let me adjust my own tune.

 

Unfortunately I do know of at least 2 who regularly do this. Most others don't because they understand its not good business to frustrate customers.

I have a hard time "supporting" tuners who do this, but the reputation of the tuners at this point is questionable so I think they have bigger problems to deal with than this. And no, Don't ask because its not something I choose to be involved in, If you search around you can figure it out.

 

The even more sad part is, after the UTEC was removed, the owner of the car re-contacted the tuner to have an original map and a before UTEC tuned map e-mailed to him so that he can re-load it into the car, and the tuner never got back to him. He supposidly e-mailed quite a few times, even spoke with him on the phone to no avail. So, this is the reason he is asking for my help with this now..