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

[_Madman_]

So, does anyone know why DSM ECUs have 4 fuel and 4 ignition maps?

I found somewhere that EVO ECUs use them to compensate for MIVEC stuff, and they have an extra set of high/low maps. But I don't see how it could be related to DSMs.

 

[Ceddy]

So, does anyone know why DSM ECUs have 4 fuel and 4 ignition maps?

I found somewhere that EVO ECUs use them to compensate for MIVEC stuff, and they have an extra set of high/low maps. But I don't see how it could be related to DSMs.

The High and Low Octane Maps are interpolated between based on the Octane number.
Octane is a trim modified by knock over a long period of time.

Basically zero knock, high octane map used.
Lots of knock, low octane map used.
Some knock, average of maps used.

The second set of maps are selected by a bit located before the periphery bits.
I am unsure if it that bit signifies California/Federal Emissions or FWD/AWD, or something else. All the ROMs I have looked into deeply so far have the bit set to zero, making the first set of maps used.

So the four maps are:
Hi Octane Cali, Hi Octane Fed
Lo Octane Cali, Lo Octane Fed


The periphery bits, ROM Ids, and a couple other items; have sets of eight items.

 

[ed_GST]

how many of you have reflashed your ECU and removed your previous fuel controller ?

 

[rstchris]

Sounds like you have your DEF files messed up somehow.

I would delete your current DEFs, and delete EM2055 and EM2056 if you have them.

Then redownload the DEFs and copy them to the eclipse folder.


You need to use the correct DEF for the ROM, or you could edit things in the wrong spot.
You shouldn't edit any of the ROM Ids in the ROM or DEF, they are there for info only.

You could edit the fuel and timing maps because they are at the same location in all the ROMs, but its better to do things right the first time or you will run into problems later on.

My ecu is now a GST, the def was fine but somehow the rom image got stupid. I deleted it and redownloaded and flashed it. So far it runs fine. The axis's are fixed. How about a fix for the genric obd2 MAP codes?

 

[kawboy]

Is there any kind of support for 6 bolt swaps?

 

[Ceddy]

How about a fix for the genric obd2 MAP codes?

What code are you getting? You may be able to turn it off in the periphery bits, but need the code number.

 

[Ceddy]

Is there any kind of support for 6 bolt swaps?

Do you have a 1G CAS? I'm running it with a 6-bolt, with a 1G Black Top CAS.
If you have a 1G CAS you should be fine, its just the 95-96 with the inverted CAS and Crank Trigger setup the sometimes have problems. You need the same hardware as in all the 6-bolt swap guides, like a 2G TPS if you have a 1G Throttle Body, etc..

The 95-96 inverted CAS problem isn't any new, people doing 6-bolts in 95-96 have dealt with it for years, and there are a couple fixes.

 

[kawboy]

One of my cars has a blacktop cas and it still gets the occasional random misfire on a stock ecu

 

[rstchris]

What code are you getting? You may be able to turn it off in the periphery bits, but need the code number.

P0105, MAP. I didn't find a fix for it, I was getting the p1400 as well but I turned it off.

 

[m_0ney_pit]

Did i see immobilizer in the periphery bits?

 

[Ceddy]

Did i see immobilizer in the periphery bits?

The periphery bits are the same for all flashable ecus, so I just copied them over.

I'm not sure if the DSMs have Immobilizer code that could be enabled or not.

That's one of the bits I definitely wouldn't play with.

 

[rstchris]

Aswell as getting rid of the P0105 code I am interested in fan control. My fan comes on @ 203 an my overflow is purging by then. What are the odds of that in the future?

 

[Ceddy]

Aswell as getting rid of the P0105 code I am interested in fan control. My fan comes on @ 203 an my overflow is purging by then. What are the odds of that in the future?

The fan controls shouldn't be that hard to find.

Whats your set-up that is causing the P0105? No MAP?

 

[rstchris]

The fan controls shouldn't be that hard to find.

Whats your set-up that is causing the P0105? No MAP?

If you can do it (fan control) just let me know how many beers I should throw in. The car didn't have a map sensor in the 6bolt swap when I got it so I put one in and still the code remains. I triple checked for ref. voltage, gnd and probed the pin at the ecu connector so I assume there is a bad connection inside the ecu.

 

[Ceddy]

P0105, MAP. I didn't find a fix for it, I was getting the p1400 as well but I turned it off.

P0105, is the MAF Barometric Pressure Sensor, not the MAP.

You must be logged in to view this image or video.

 

[rstchris]

Oh! I see, as soon as I read this I scrambled to the books and punched myself. Thank you. I do have another MAF if thats the issue. So, thats a big nevermind on the P01050.

 

[antilag]

First off, great work Ceddy. I had just got my evo ecu to work but after seeing this I went back to my stock ecu.

I have a 6 bolt swapped 98 gsx with 7/97 build date and the ecu version was 20560009. I have cross flashed the 0010 and so far it is working perfectly with the evo maf converted. I also changed the baro compensation values to match the evo as well because there was quite a difference which seemed to help.

Would you like me to send you the 0009? I know the easiest thing for everyone is to flash to one of the versions on the first page, but strictly for information sake I will send it if you would like.

I do have a question on latency values. I have fic 650 and the latency you have listed is .210. Do I add that to the existing values? I have already put 647 into the injector size.

Thank you to everyone,
Jeremy

 

[ed_GST]

Glad you have succeeded with the cross flashing

About your injector latency question... Yes, you have to add the .210 to the existing values

 

[Ceddy]

First off, great work Ceddy. I had just got my evo ecu to work but after seeing this I went back to my stock ecu.

I have a 6 bolt swapped 98 gsx with 7/97 build date and the ecu version was 20560009. I have cross flashed the 0010 and so far it is working perfectly with the evo maf converted. I also changed the baro compensation values to match the evo as well because there was quite a difference which seemed to help.

Would you like me to send you the 0009? I know the easiest thing for everyone is to flash to one of the versions on the first page, but strictly for information sake I will send it if you would like.

I do have a question on latency values. I have fic 650 and the latency you have listed is .210. Do I add that to the existing values? I have already put 647 into the injector size.

Thank you to everyone,
Jeremy

Yes, for Inj Latency you add to all values in the table.

I just found out the evo5base and evo9base (Inherited to DSM and Evo8) have the MAF Table scaling set to different units. I am changing all the DEFs to match the Evo8. But it will take a little time before I have everything changed then posted here.

Edit: The Evo8 MAF Conversion pic on first page is correct. There is a problem with the Evo7,8,9 DEFs that some have the MAF Scaling as AirFlow8 and some UInt8. Which will display different units. Sorry for the confusion.

I'd like to check out the 0009. My email is ceddy @ ceddy.us

 

[antilag]

I emailed the 0009 hex to you.

When I did my maf scaling I used my buddies evo 8 maf smoothing, maf filtering, baro compensation maps and it seems to work very well since I am using his original evo maf.

I was wondering if anyone has rescaled thier maps yet up to say 260 load or so? I know the evo boys start around 70 to start raising the load scale but they also have an extra 4 columns to work with to keep it smooth. We are quite limited with only 14 columns, just wondering where people are starting to raise the load values and what kind of incriments they are raising them by?

 

[Ceddy]

I emailed the 0009 hex to you.

When I did my maf scaling I used my buddies evo 8 maf smoothing, maf filtering, baro compensation maps and it seems to work very well since I am using his original evo maf.

I was wondering if anyone has rescaled thier maps yet up to say 260 load or so? I know the evo boys start around 70 to start raising the load scale but they also have an extra 4 columns to work with to keep it smooth. We are quite limited with only 14 columns, just wondering where people are starting to raise the load values and what kind of incriments they are raising them by?

Whats your turbo setup? And what do expect your max AirFlow to be?

I was going to post an edited 20550011 with rescaled axis for the Fuel and Timing tables, haven't gotten that far yet though.

The RPM axis I was going add more points 5000-6500, because that's where most people have problems tuning out knock. And take some out points out and low rpms.

The Load I was going rescale to a higher Load, and make the timing drop off like the EVOs do. If you look at the EVO maps the timing drops off quickly at high Load and RPMs.

If anyone has input on this it would be welcome.

 

[antilag]

I only have an e316g, but with the head I have and 20psi I wouldn't be suprised to see close to 40lb/min. I do plan on going with a 60lb/min turbo when it is all said and done.

The evo timing maps are very conservative. I am computer illiterate or I would post the timing map for the evo that we have tuned here. It prevents any drastic drop off and goes to 300 load point. At the 7500 rpm and 260 load: stock is 9*, we have 22* and it keeps everything very smooth. This is a meth injected car running 28psi on a 35r though

 

[ed_GST]

there are various load columns that have the same values one next to the other
those can be merged to give room for higher load columns

in the timing maps
from 0 to 30 have the same values
also think that from 50 and 60 can be merged too

with that we should have 4 extra load columns

 

[Ceddy]

This is an Ignition map I've been working on. Its good up to 300 Load, which is 52 lb/min at 7500 rpm.

First the 500 and 750 RPM axis were removed, and 5250 and 5750 were added for more resolution where its needed more.

The Load axis was extended to 300. The last item 300 was increased to 380, in case Load exceeds 300. The table lookup can act funky if the lookup is off the map.

All values below 200 Load are from the 2G map, all values above 200 are from the Evo8 map. Any missing values were interpolated.

This should be a good stock, starting map for up to 50 lb/min.

Extended Map

You must be logged in to view this image or video.

Stock Map

You must be logged in to view this image or video.

 

[antilag]

That is very conservitive for timing. Weather you are at 25lb/min or 50lb/min I would still want 20+ degrees of timing at top end. Assuming you have a base of 5-8* you would still want to have 16 degreees advance at top end, as long as all the supporting mods are there for it of course. If they are not, nobody should be running 50lb/min.

I realize you are taking the side of caution and using that map as only a starting point, but my map at 7000rpm and 240 load is at 21* currently with no knock and is very smooth through out which is off our tuned evo map.