Mitsubishi Eclipse 3G Club banner

"Big Map"...reality is here

187K views 2K replies 66 participants last post by  cesarnoll064 
#1 · (Edited)
This has all been talked about for a while, theories of how to go about it and so on. I have recently been working with somebody on creating the "Big Map" for the 01-03 Galant, and 01-05 Eclipse V6 platforms running boost. Currently however we only have this one ROM finished for the 05 (which I believe should suit the 03-05 V6), the 01-02 ROM will be worked on next when this initial patch is finalized...please be patient.


Current Features on this patch;
"Big Maps" High/Low Octane Ignition and Fuel (30 x 30)
Knock on CEL
MUT Table
2Byte Load
MAF Clipping Coefficient
Injector Battery Voltage Latency Compensation
Accel Enrichment
Open Loop Load #1 and #2
Min Coolant Temp for Closed Loop
Injector Scaling
MAF Scaling
MAF Smoothing
MAF Sensor Filtering
MAF Size
Rev Limit
Speed Limit
Desired ISCV initial step position with AC on/off - Drive/Neutral
Desired Idle RPM Neutral/Drive


High Octane Fuel Map


High Octane Ignition Map


Knock on CEL, MUT Table





This patch is all done by "Acamus" and he is doing this on a "donationware" basis. Any and all donations are greatly appreciated to show appreciation for his hard work, and continued support with developing this patch.
V6 Patch Donation


Input/Feedback/Suggestions welcome
 

Attachments

See less See more
4
#355 · (Edited)
Acamus added a table that switches Pin 32 with a duty cycle based on Load and RPM. AFAIK, we're supposed to make sure the ROM runs like usual, and if possible, monitor or log MUT_86 for solenoid duty. Pin 32 is used on GTS models to control the variable induction solenoid, but I confirmed that the pin works properly on GT models when run with the right ROM.

I didn't get the car flashed last night like expected, but I'm going to flash it before I leave work. I'll probably hook up an LED to visually confirm that the duty cycle is varying like expected.
 
#364 · (Edited)
Acamus added a table that switches Pin 32 with a duty cycle based on Load and RPM. AFAIK, we're supposed to make sure the ROM runs like usual, and if possible, monitor or log MUT_86 for solenoid duty. Pin 32 is used on GTS models to control the variable induction solenoid, but I confirmed that the pin works properly on GT models when run with the right ROM. I'll probably hook up an LED to visually confirm that the duty cycle is varying like expected.
It would be better to get some cheapo oscilloscope now that the duty can be measured at the pin also.
Otherwise we have only qualitative result i.e. LED will change its illumination intensity according to the duty.
 
#357 ·
Acamus, I was unable to get my car to start using the newer version of the BigMaps ROM that you sent me. It seemed like it was an immobilizer issue, although I tried using both normal and disabled immobilizer settings, and several points in between.

Dragon, were you succesful?
 
#358 · (Edited)
i just finished moving all my tables over (copying from one rom to another)... I did notice one thing though, this rom doesn't have the EGR tables defined (tables 1 and 2) :scratch:

i'll have results in a few minutes here...

edit... nvm, i just noticed the tables under "EGR" ..
 
#360 ·
I don't think that would make a difference considering that I've run several different ROM ID's on my car without trouble. My guess is that the problem is well above my abilities to correct.

Acamus, I compared the ROMs using EcuFlash, and it's coming up with differences in FB01, 02, 04, 10, 11, and 12. Does that sound correct to you? Also, Dragon, does that match what you saw as well?
 
#362 · (Edited)
I'm either not explaining it clearly or you never thought about it. Does this look familiar? This is what comes up when you flash a new ROM or use the compare to ROM function in EcuFlash. These are my results . . .


[19:36:33.298] -- comparing ECU flash memory pages to image file --
[19:36:33.298] seg start len ecu CRC32 img CRC32 same?
[19:36:33.314] FB01 00000000 00001000 C52F74D1 80F658CE NO
[19:36:33.345] FB02 00001000 00001000 D8C583AF BCC276F5 NO
[19:36:33.361] FB03 00002000 00001000 AA9D4386 AA9D4386 YES
[19:36:33.392] FB04 00003000 00001000 40B3D23B 30B4D2F9 NO
[19:36:33.407] FB05 00004000 00001000 E6EE62AB E6EE62AB YES
[19:36:33.423] FB06 00005000 00001000 C579DA04 C579DA04 YES
[19:36:33.454] FB07 00006000 00001000 404C8C7D 404C8C7D YES
[19:36:33.485] FB08 00007000 00001000 FFE56802 FFE56802 YES
[19:36:33.579] FB09 00008000 00008000 CE599970 CE599970 YES
[19:36:33.782] FB10 00010000 00010000 8604836B 79B7D65D NO
[19:36:33.985] FB11 00020000 00010000 CBADAFDC B3F05D4C NO
[19:36:34.187] FB12 00030000 00010000 29DA1495 32E21ED3 NO
 
#363 ·
^ the results are Ok, EcuFlash just compares if there is a change in the block of memory and if it is so it writes it to the ECU.

I have found one bug in the implementation :p
Here is a quick definition that you do not have to port your tunes again.

HTML:
<table name="Bug FIX (0x40->0x4A)" address="3f30e" category="Solenoid (Pin 32)" type="1D" level="1" scaling="Hex8"/>
 
#370 ·
Read the thread...see no mention of 2000's. :(

Any chance I can get one of these ROMs for my 2000 GT Manual - H8539F - 21810021? I've got $$ for ya if I can finally remove my emanage and safely tune up past my current 10psi limit.
 
#372 ·
ecuflash crashes everytime i try to open the new rom. Care to take a look into that issue? (just to be sure it was the rom itself i was able to succesfully open 2 other roms, so the problem isn't ecuflash, the problem is the new rom)
 
#378 ·
ceddy wants nothing to do with it.

My problem with wiring in my 01 ecu last time around was that it wanted more (precat) O2 sensors. I don't suppose this ROM could be made to not need those inputs...?
 
#384 · (Edited)
I just tried it with a 00 in there... Still wouldn't start up. I dunno if this piece of info would help at all but i just noticed when i tried to get the DTC's off the ECU after i flashed it with the project rom, Evoscan would not connect to the ecu. Not only that, i tried starting up evoscan to start datalogging with the key in the "on" position and it also would not connect to the ecu.
 
#386 ·
It starts up... dunno if the pin is putting out the desired amount of voltage though. I'll have to find my volt meter and connect it up to pin 32 sometime later today. Thanks again!

(will donate some more for taking your time in to helping us out ;) )
 
#388 ·
Dragon, nice catch with the EvoScan test. I didn't even think about trying that when I was testing the ROM.


I copied the ROM to my car and it seems to work well. Logging in EvoScan showed that the solenoid tuning MUT address was changing, but the scan frequency was insufficient to determine the rate of change. I might try picking up a cheap PC based oscilliscope to completely verify operation.
 
#389 · (Edited)
Thanks for the props

:scratch: .... how do you log pin 32 in evoscan? Better said, what address did you input into evoscan to pick up on the change?

A little OT but i thought i'd mention it anyways... I'm fearing that my ECU is reaching a point where it no longer will be "completely" flashable. The reason i say that is because when reading off the ECU about half off the maps and tables come back as garbage :'(
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top