The Central Hub for DSM Community and Information

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. This is where the DSM platform history is documented and archived. Log in to help us in our mission, and to remove most ads from the browsing experience.

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

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

No ceddy said in his post that he would let someone else do it because he was not going to break the law, and as of right now ceddy and Jeffo are the only ones doing coding for these ecu's as far as I know. If someone knows of anyone else please chime in. So sorry now way to cheat the emission testing equipment as of yet.
 
Yeah you can do the Readyness stuff. Keeping it on the DL, kinda.

Edit:
May be I should say you can patch a rom, yourself.

All my roms are in stock form readyness wise.
 
yes! I have one I can post it has the BOOST gauge on KNOCK working!

But you would have to mod if for your settings, as mine is not STOCK anymore as I have started tuning mine and I also have mine patched for BIG MAPS.

I could list everything I changed and you can look at 1.8 and copy the settings over.
 
yes! I have one I can post it has the BOOST gauge on KNOCK working!

But you would have to mod if for your settings, as mine is not STOCK anymore as I have started tuning mine and I also have mine patched for BIG MAPS.

I could list everything I changed and you can look at 1.8 and copy the settings over.

Wouldnt it be a little different, because you a AWD ecu? I is not AWD LOL. -_-
 
What you end of doing if you have a flashable ecu is just flash it for the rom Ceddy has definitions for. This happens to be a GS-T rom image.

So we all are using a GS-T rom if your using Ceddy mods cause its easier to write one set of definitions as it would take a few different ones for everyone to be using there own ROM image modded. I forget how many different ones there are.

For example my 1998 was made Nov. 1997 I have revision 9. The one that ceddy is using I believe is revision 11. It would take more work to write definitions for all the different revisions. But since the rom's are interchangeable between the 1997-1999 ecus we all can use 1 general one.

As I am to understand the difference between GS-T and GSX rom is speed limiter.
 
I have a question I couldn't find an answer to. I plan on swapping a 6 bolt shortblock into my 99 and I saw the Magnus harness for the Crank sensor and CAS. If I need it, I'll get it. But with the Ceddymods, can I just disable the ECU's need to see a signal from the crank angle sensor eliminating the need for that harness? Thanks.
 
But with the Ceddymods, can I just disable the ECU's need to see a signal from the crank angle sensor eliminating the need for that harness? Thanks.

Everything in the ECU depends on the crank and cam angle input so the car won't run without them.
 
I have a question I couldn't find an answer to. I plan on swapping a 6 bolt shortblock into my 99 and I saw the Magnus harness for the Crank sensor and CAS. If I need it, I'll get it. But with the Ceddymods, can I just disable the ECU's need to see a signal from the crank angle sensor eliminating the need for that harness? Thanks.

No, you need the Crank Signal.

The CAM Signal tells the ecu when the cylinders switch. The Crank Signal tells the ecu when cylinder #1 is TDC. With out the Crank Signal the ecu wouldn't know which cylinder is which.

The 1G CAS combines the CAM and Crank Signal in one unit.


I think the easiest approach with a 6-bolt swap is a 1G CAS with a Magnus type harness.

You could also use a 97-99 CAS and Crank Trigger with a Kiggly Trigger Plate setup.
 
I was able to make my own harness out of the wires and plugs I already had, my friend purchased the magnus harness. The only issuse I had with the 6bolt swap was the MDP sensor connected and still setting off the CEL but that fixed now with ceddy mods.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------


I finally got my injectors scaled. I only have 550miles on my rebuilt and been tuning since 350miles.

For anyone using PTE 680's I am at a scaling of 535cc and I'm at 11.2 on my wideband with a target AFR of 11.0 so I'm as close as I can be without going under. Just thought this might help someone else out.

Anything higher then 545cc was way off giving a AFR of 11.9-12.5. At 600cc I was in the 13's.

And with a 16g and FMIC I am able to run a max of 21-22psi without knock, start knocking @ 23psi I'm still adding timing but I'm at about 10 degrees of advance from 4-7k, still have more too add.
 
I had the same problem after making an account at www.myrollingroad.com. The site would never let me have access to the file.:cry:
So I did a quick google search of mutmonitor20.zip
This site (www.club4g.com) has it.
Best part is you dont have to register with the site.
Just click the attachment file and download.:hellyeah:
Incase you cant find the attachment file on the forum, below is a direct link of the file.
--Your welcome--
DOWNLOAD:thumb:

LOL, wish I could understand Thailand language..
 
I finally got my injectors scaled. I only have 550miles on my rebuilt and been tuning since 350miles.

For anyone using PTE 680's I am at a scaling of 535cc and I'm at 11.2 on my wideband with a target AFR of 11.0 so I'm as close as I can be without going under. Just thought this might help someone else out.

Anything higher then 545cc was way off giving a AFR of 11.9-12.5. At 600cc I was in the 13's.

And with a 16g and FMIC I am able to run a max of 21-22psi without knock, start knocking @ 23psi I'm still adding timing but I'm at about 10 degrees of advance from 4-7k, still have more too add.

Did you make changes to the latency values? Check and double check the authenticty of the numbers you find for any given injector cause if it's not right tuning will be a long hard job with crazy changes to maf scaling.
 
I didn't change and latency values yet as I was to understand to do WOT tuning and scale your injectors and then look at your trims and tune your latency.

I'm being told I may not have 680's so I take back the info posted above until I get a solid answer.
 
You should start by adding at least 200uS to each deadtime, and then see what the TRIMs do. I usually find that the PTE/FIC/Delphi 650's need ~270uS of extra deadtime.
 
If you're asking for EvoScan, you have to purchase and download it from the site...

EvoScan OBDII Mitsubishi MUTII DataLogger Scantool
Ced, thanks but i have already bought and d/l Evoscan 2.7

Hey gsttuner22 I think what everyone is trying to figure out is what MUT program are you talking about that you need someone to post for you. As far as I can tell from your other threads so far you have all the programing you need to be able to flash your ecu and to be able to log it.
Yeap, i do have all the ones i need but i was just looking for the MUT from Myrollingroad.com, the one you have to register for and what not.


I had the same problem after making an account at www.myrollingroad.com. The site would never let me have access to the file.:cry:
So I did a quick google search of mutmonitor20.zip
This site (www.club4g.com) has it.
Best part is you dont have to register with the site.
Just click the attachment file and download.:hellyeah:
Incase you cant find the attachment file on the forum, below is a direct link of the file.
--Your welcome--
DOWNLOAD:thumb:

LOL, wish I could understand Thailand language..

haha, thanks again man. i really appreciate it.
 
So I went out tuning last night and ran into problem after problem after problem. I probably won't remember all of them for this post, so I'm going to add to it after I talk to my friend that was helping me out.

First, EvoScan was sucking major. Regardless of what settings were used I could not pull any DTCs from the car. I had OP 2.0 selected and tried it with MUTIII, OBDII 96+, and the DSM one. Every time it said no response from ECU.

Then, for logging the program would lock up when I started with the DSM box selected. All the logging had to be done with MUTIII selected. I don't know if that's the right way for it to be done, cause I've never seen anyone mention it but having the DSM box checked makes sense.

EvoScan won't read my AEM wideband either. All pulls had to be done with me watching the wideband and just seeing if it's "OK". It worked before I formatted my computer, but now won't. AEM is selected for the wideband and I have the proper COM port selected.

To scale the injectors, we logged fuel trims to see where they were. Of course, the trims never changed and were locked at .1008 or something like that. Then in trying to scale them in Open Loop, the scaling was way off. I have 850s, yet they have to be scaled down to around 475 for the car to idle anywhere decent. I'm beginning to think that the used injectors I bought aren't FIC 850s now. I would know more by logging duty cycle, but of course when logging that, it doesn't work.

We were then doing pulls and logging Load Calculated and it started maxing out at 255. We tried logging Load11bit4, Load MUT 2Byte, and Load 1 Byte but all those values were different from each other and each one maxed out at something different and too low to be of any use.

After doing some pulls and checking the logs, the timing that the car is running is no where near what is in the maps. The timing was consistently 3 or 4 degrees higher than what was in my timing map. Is there some dynamic timing advance in the ECU that hasn't been defined yet?

Thinking I was having a lot of issues with EvoScan somehow, we found a place with free wifi and I downloaded MUT Monitor. The program is simple and clean, yet you can't log to a file. It connects to the ECU just fine, but when checking "Log to File" and setting a file path it just gives file path errors. We tried everything to get that working to no avail.

At this point I'm so painfully frustrated with everything it's not even fun. I stopped doing the Evo ECU stuff because it was overly complicated compared to this, but now I'm running into the exact same stupid problems with injector scalings, not being able to log trims, I can't set up the basics so doing WOT pulls is impossible. The car does run better than before, but that's only after spending at least 3 or 4 hours last night messing with stuff, practically blindly and anything would be better compared to the base tune I had with the Evo ECU. After all the time spent, the car should be doing everything damn near perfect.

So I guess to make this something other than just a rant, does anyone have any input on what the heck is going on with my car? Why is it this complex when it should be as simple as changing a few tables here and there? Also, is anyone near the Chicago area that has done this and would be willing to look at it? I'm really at a loss right now, almost makes me want to get rid of the car completely...

I'm so ready to sell all the stuff I wasted my money on and just get DSM Link.
 
Use MUTIII, DSM is for 95/96

Log Load 2Byte.

Injector Tuning -> http://ceddy.us/?page_id=379

Reset ecu after changing Injector Scalings.


You have to load the .xmls like its says in the directions, looks like you didn't load the .xml into EvoScan. So most of the items are not going to work correctly...



Sounds like you are frustrated over the "tuning", you have to tune any ems.
EcuFlash is definiately DIY, a more user friendly, dumbed down ems may be better for you.

Or have someone tune your car for you.
 
Use MUTIII, DSM is for 95/96

Log Load 2Byte.

Injector Tuning -> http://ceddy.us/?page_id=379

Reset ecu after changing Injector Scalings.


You have to load the .xmls like its says in the directions, looks like you didn't load the .xml into EvoScan. So most of the items are not going to work correctly...



Sounds like you are frustrated over the "tuning", you have to tune any ems.
EcuFlash is definiately DIY, a more user friendly, dumbed down ems may be better for you.

Or have someone tune your car for you.

If you recall, I sent you a PM about the XML for EvoScan and that since I'm using v2.7 it doesn't work.

I will also willfully admit my tuning knowledge is very minimal, however, the person helping me is a popular Subaru tuner that is doing the same work you are doing with definitions but with the Subarus. I believe he even PMed you about lending a hand in the work you are doing.

I'll read over that link and do a little more work. I'm also waiting to hear back from the EvoScan people about sending me v2.6. They are so slow to respond, it's painful.
 
I have 850s, yet they have to be scaled down to around 475 for the car to idle anywhere decent.
That is probably because you haven't added any deadtime/latency compensation to the maps. You should start with ~300uS extra latency added to each of the stock deadtimes.
Its easy enough to make sure they are 850's. Delphi laser etches every injector with a part number around the top circumference of the injector body. It is very faint. Just Google that number. For 850's you want to start with ~840cc.
 
Check the cabling, EvoScan 2.6 reads pretty much everything, even older models and unknown JDM ECUs. There have been problems with messed up OBD2 wiring on some cars. Bad contact can make a huge difference.

The EvoScan works very well. Although it's been half a year with my car sitting with a broken tranny in a garage in the other city, maybe developers have broken something. But I'd blame bad wiring 1st, operator 2nd, cooked ECU 3rd, and EvoScan 4th...
 
I recently bought an ecu (#md346676) for my 97 gst, would I have to do anything special to hook it up or is it jusy plug and play? I haven't got the cable to do any tuning but I just want to go ahead and get it in the car.
 
I recently bought an ecu (#md346676) for my 97 gst, would I have to do anything special to hook it up or is it jusy plug and play? I haven't got the cable to do any tuning but I just want to go ahead and get it in the car.

It is plug and play.

You won't have a Speed Limiter with the AWD ecu, thats about the only difference.
 
I noticed on your tuning page Ced, that your smoothing table is in % and not g/s, as well as you Adder is in g/s and not units.

Compared to mine I am just wondering if all you did is edit the map definition to Percent128 and then change your values to the displayed.

Also, what is the purpose of changing the smoothing table to a % as opposed to g/s ?


**EDIT** What color schema you using ced? :)
 

Attachments

You must be registered for see attachments list
The logic used by the ecu is:

(MAF_Scaling[Hz] + MAF_Adder) x MAF_Smoothing[Hz] / 128 = Airflow for Fuel Calcs

MAF_Smoothing is used for fine tuning, and correct unit is Percent128.


MAF_Scaling and MAF_Adder should both have the same units, g/s. Or raw units if you prefer that for some reason.



I have units changed in newest version 1.9, but not released yet, so you will need to change units yourself.
 
Add Value - Be Respectful - No Trolling - No Misinformation - Participate Often!
Support Vendors who Support the DSM Community

Build Thread Updates

Latest Classifieds

Back
Top