ECUflash First Flashed DSM ECU! (98/99 Flashing FAQ)

[steve]

Any capacitance on the board bleeds off in seconds. Any additional capacitance in the car is isolated from most of the ECU by the MPI relay. Only the backup power input isn't and I've yet to see an issue from plugging or unplugging a ECU with the backup power being hot.

Draining the charge on a audio cap using the headlight is preferable to shorting the battery leads.

 

[draculia]

Ceddy, the definition files you uploaded still have the wrong RPM axis address for the Open Lood Load 1? section. For 20550010 using the address of "2ee66" as displayed in the .xml will show the correct rpm values. For the 2055011 definition the address "2e546" is what works. This is the same address that's used for the fuel maps, which is of the same y axis 14 element length.

 

[rstchris]

I tried the new definitions on "edit" post #1 to no avail. I have a 98gsx and keep getting the def. error menu. Has the md346676 been done yet? Any suggestions?

 

[Ceddy]

Ceddy, the definition files you uploaded still have the wrong RPM axis address for the Open Lood Load 1? section. For 20550010 using the address of "2ee66" as displayed in the .xml will show the correct rpm values. For the 2055011 definition the address "2e546" is what works. This is the same address that's used for the fuel maps, which is of the same y axis 14 element length.

I haven't finished updating the DEFs yet. I'll add the Open Loop Load Axis, and should have a DEF for the 2364 soon.

While the axis you gave is probably has the correct values, it isn't the axis used for table look up for Open Loop Load. If you tried to rescale that axis it would rescale the Fuel Map axis not Open Loop Load axis.

The only way to find the correct axis is to go through the code and find where the table look up is done for that map. I'm marking all the maps that have their axis confirmed with an asterisk *.

 

[Ceddy]

I tried the new definitions on "edit" post #1 to no avail. I have a 98gsx and keep getting the def. error menu. Has the md346676 been done yet? Any suggestions?

The 2056-0010 has been done. But if you have a different revision it won't work.

If you check out location 0x21A with a hex-editor it will show the four byte ROM ID.
Should look like: 20 56 00 10

Once you know your ROM ID you can find out if a DEF has been done for it yet.

 

[draculia]

Ah yes. I had a feeling it wouldn't be that easy.

 

[shark]

rstchris,
What is the build date on your 98?

My 98 was built in Oct 97.

I would recommend you send your hex/bin file to ceddy if you havent already.

red

 

[rstchris]

rstchris,
What is the build date on your 98?

My 98 was built in Oct 97.

I would recommend you send your hex/bin file to ceddy if you havent already.

red

Built, july 97. I don't really know what i'm doing and just trying to grasp all this, what is the file I need to send? I can post a photo of the opened ecu if that helps.

My ecu is the same as the first one in post #97 with the exception of the bottom left corner of the biggest chip, mine has "6m3 I"

 

[shark]

I successfully made minor changes to my rom and flashed the ecu

rom = 20560010

Took it out to get gas and do a datalog run on the onramps and my clutch master took a dump and had to limp it home

So no playing for a few days till I get it fixed.

red

 

[draculia]

Built, july 97. I don't really know what i'm doing and just trying to grasp all this, what is the file I need to send? I can post a photo of the opened ecu if that helps.

My ecu is the same as the first one in post #97 with the exception of the bottom left corner of the biggest chip, mine has "6m3 I"

Now assuming that you have the required hardware and software: Openport 2.0 cable with Mitsu flashport adapter, and ECUFlash, the main thing you need know is the ROM ID. There are two ways you can do this easily. One is to use any DEF file that Ceddy uploaded and check the ECU Internal ID #1 selection under the Misc section.

The other is to download a hex editor, and open the ROM that you download from the ECU. Once open there should be some section of the screen that shows the offset address. You want to look at offset 0x021a, it might show up differently depending on the editor that you use, but you want 21a preceded by a bunch of zeros. From that point if you read to the right for a total of 8 digits you will see the complete ROM ID.

I have included some example pics to show you what it might look like.

Once you find out your ID you just need to download the correct DEF file for it from post #1 and copy it to this directory if you installed ECUFlash in the default location: C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\eclipse\

Now if your ID is not listed in post one, then send the ROM to Ceddy.

 

[draculia]

OK, I have another question. Am I able to change the scaling definitions without messing anything else up. Specifically, the injector Latency values are kept in a uint8, but it will max out at 3.8something for whatever reason. If I change this to an uint16 I can use any value I want. I know this will increase memory usage ever so slightly, but it's not going to throw anyhting off is it?

 

[Ceddy]

OK, I have another question. Am I able to change the scaling definitions without messing anything else up. Specifically, the injector Latency values are kept in a uint8, but it will max out at 3.8something for whatever reason. If I change this to an uint16 I can use any value I want. I know this will increase memory usage ever so slightly, but it's not going to throw anyhting off is it?

No, the data size must be the same. uint8 = 1 byte, uint16 = 2 byte.

The only values you really have look look at on the Latency Table are 11.72v and 14.06v.
Hopefully your car will never be at 4.69 volts, so you don't have to worry about values maxing out down there.


This gets complicated because they use the word scaling for everything.

The scaling for individual items is a conversion from machine language to units we can understand.

When you rescale an axis you are usually increasing the upper item in the axis so you don't run off the map.

The only maps that are usually rescaled are the Ignition and Fuel Maps.

 

[draculia]

Yeah, I didn't think I'd run into instances where the injector voltage would be that low, but I wanted to ask incase I came across something similar on other maps. As always, thanks for the info Ceddy.

 

[rstchris]

Now assuming that you have the required hardware and software: Openport 2.0 cable with Mitsu flashport adapter, and ECUFlash, the main thing you need know is the ROM ID. There are two ways you can do this easily. One is to use any DEF file that Ceddy uploaded and check the ECU Internal ID #1 selection under the Misc section.

The other is to download a hex editor, and open the ROM that you download from the ECU. Once open there should be some section of the screen that shows the offset address. You want to look at offset 0x021a, it might show up differently depending on the editor that you use, but you want 21a preceded by a bunch of zeros. From that point if you read to the right for a total of 8 digits you will see the complete ROM ID.

I have included some example pics to show you what it might look like.

Once you find out your ID you just need to download the correct DEF file for it from post #1 and copy it to this directory if you installed ECUFlash in the default location: C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\eclipse\

Now if your ID is not listed in post one, then send the ROM to Ceddy.

I do have openport/mitsu adpt. ecuflash. I saved both 98" files from post #1 with no luck. I'll start over with the instructions, btw, thank you. For a minute I was getting an error so I uninstalled every bit of the openport stuff and redownloaded and then just asked for def. once again. Internal ID is:F27C000A00C0

 

[shark]

rstchris
You need to download YOUR ECU's ROM using ECUFLASH
Not the rom from post #1

Then the rom id needs to be checked in YOUR ROM.
Then YOUR ROM needs to either be matched up with the correct XML def or a new XML DEF created for it.

sorry if this sounds condescending, but it sounds like you are missing the basics

hope this helps
Red

 

[Ceddy]

I do have openport/mitsu adpt. ecuflash. I saved both 98" files from post #1 with no luck. I'll start over with the instructions, btw, thank you. For a minute I was getting an error so I uninstalled every bit of the openport stuff and redownloaded and then just asked for def. once again. Internal ID is:F27C000A00C0

Internal ID should be 8 bytes and look like:
20550011,
20560010,
23640004,
etc.

If you click "Read From ECU" and Select "1996-1999 2nd Gen Evo 5/6"
Then save it.

You can mail it to me -> ceddy @ ceddy.us

I can tell you which ROM you have or if it corrupted or something.

 

[rstchris]

Sorry guys, I'm a newb. The hex editor is amazing, my id is 20560008.

 

[ed_GST]

Just got my OpenPort cable today
I was able to read the rom is a 20550011
I be doing some tuning tonight i will let you know the results

 

[ed_GST]

im using EVO 8 injectors and when adding the dead time for this injectors(-.48)
it doesn't let me go lower than .750 uS

 

[Ceddy]

im using EVO 8 injectors and when adding the dead time for this injectors(-.48)
it doesn't let me go lower than .750 uS

The Evo8s are -.048

There is some granularity to the values, and it will always round to the nearest acceptable value.

The Latency values are rounded to .015 increments. Try entering a lower number. It will accept values down to 0.000

 

[ed_GST]

Well i had flashed my ECU for about 4 times
It runs like stock with the 560cc injectors
Im still using stock Fuel and Ignition timing
Disabled Close Loop and the rear O2 sensor


Do i have to do the MAF scaling ? What difference will it make ?

 

[Ceddy]

Well i had flashed my ECU for about 4 times
It runs like stock with the 560cc injectors
Im still using stock Fuel and Ignition timing
Disabled Close Loop and the rear O2 sensor


Do i have to do the MAF scaling ? What difference will it make ?

If you have a non stock intake pipe it can throw the MAF readings off a little.
All the MAFs don't come perfectly adjusted from the factory either, they just turn the adjustment screw on the bottom of the MAF until it idles OK.

You want most of your adjustments done using Injector Size and Latency, then you can do fine adjustment using the MAF Scaling Table.

With everything adjusted properly your wideband readings should match the fuel map.
The EvoScan item "AFR Map" will tell you what the target AFR is, to compare to you wideband.

Getting everything adjusted perfectly in the beginning can be a pain, but it makes tuning everything else later on a lot easier.


I will have a major update to the 20550011 DEF done very soon. Lots of more items added.

 

[rstchris]

What are the chances of seeing a def. for the 20560008 any time soon? I can offer motivation "caugh"$"caugh" or would it be wise to just invest in the appropriate ecu?

 

[shark]

rstchris,
Since you are a 2056nnnn you could flash in the 20560010,
unplug the battery for 15 minutes
and then you can tune with the already define xml for 20560010

Red

 

[Ceddy]

What are the chances of seeing a def. for the 20560008 any time soon? I can offer motivation "caugh"$"caugh" or would it be wise to just invest in the appropriate ecu?

You should be able to cross flash the 20550011. A ecu reset needs to be done after cross flashing.

No one has really tested this yet though.

The only real difference between the GST and GSX is the speed limiter , which can be switched off in the periphery bits.


I'll have a big update for the 20550011 very soon, 20+ more maps, knock control, and more.