So who wants their ECU's "Chromed"?

[Greg E]

This thread is now outdated!! New threads here:

http://www.3sgto.org/f104/how-tune-y...ecu-10775.html
http://www.3sgto.org/f104/chrome-v2-...ual-10777.html





I finally got the first stage of my "Chromed" (patched) ROM mods figured out & my custom EVOScan file is completed & tested. This has been at least a year long project in the making and I'm now comfortable releasing it to the public.


Background

This ROM is a patched version of the last known VR4 ROM released from Mitsu. It's been tested to work on ALL 98 & 99 VR4 ECUs. You WILL NEED a VR4 ECU to utilize all the features of my patched ROM. If you're using another ECU other than the VR4 ECU (Montero, Diamonte, SL, Base...) some features will not be available and there could be some unwanted side effects. I personally don't recommend anyone purchase any other ECU other than the VR4 one at this time. There are guys who have been working on modifying other ECU's to work in our cars. One guy is Adam (Jesters Dead) and the other is Brett (99 VR4).

More info here!

Link to Adams ECUs

Link to the Clone VR4 ECU Thread!



Prerequisite

You need the following:

Laptop running windows w/ at least 1 USB port.
Tactrix 2.0 Cable - DO NOT BUY THE 1.3 CABLE!! We need the power booster from the 2.0 cable for flashing.
ECUFlash
EVOScan V2.6 (It's $25, don't be cheap! ) - After you purchase, download and install EVOScan, you'll have to register onto the website to get v2.6. My file will only work in v2.6 as of now & no other logging program available will support my patched ROM.
98/99 VR4 ECU w/ OBD2 connector and flash port (Don't believe boomslang includes this with their adapters)


Getting started

First decide if you want Load Based tables or Air Mass Based Tables. Then Decide if you're going to run a EVOX Maps sensor or not.

Go to Chrome V1.0 and download the RAR file. (Load based tables)
*Special Thanks to Brett (99 VR4) for the hosting!!!!!!!

Inside is a folder with 1 file & 2 folders inside. One is the "Chromed" ROM, one is the definition file for the ROM and the other is the definition file for EVOScan. All 3 are tied together and are meant to be used in conjunction with each other. You'll find many of the features in these definition files won't work with a stock ROM.

The 3000GT folder contains the definition file. Inside the folder is the 23861006 XML file. Extract the 3000GT folder to:
C:\Program Files (x86)\OpenECU\EcuFlash\rommetadata\mitsubishi

The Chromed ECU v1.0 contains the 23861006 ROM itself. This is the file you modify & flash to your ECU. Extract the Chromed ECU v1.0 folder to:
C:\Program Files (x86)\OpenECU\EcuFlash\

Finally, the Data.xml file is the definition file to convert EVOScan to work with our cars. Extract this file into:
C:\Program Files (x86)\EvoScan\EvoScan v2.6\DataSettings
Replace the Data file in that folder with the new one. DO NOT use the 3000GT settings. MANY OF THE LOOKUPS ARE WRONG! Leave EVOScan in MUTIII mode.

Note: Sometimes there's an issue with installing ECUFlash/EvoScan. Read this!!

Greg I still can't figure out why I can't get "air mass" to display in EvoScan. The info is in the XML file you provided, in the correct location. What am I doing wrong? I need to start logging and tuning ASAP.

can you log load?

Nope. Only things relating to airflow or load are as follows;
-Airflow Rate gm/s
-Airflow/Rev
-Air Flow Hz
-Load MUT 2Byte Mod
-Airflow MUT 2Byte Mod
-Load Calculated
-Load11Bit4
-Load 1Byte

I don't know if I just did all the steps completely wrong or what but I'm confused.

very quick. Take a screenshot of evoscan and post it. I also need a screenshot of your MUT table.

Attachment 3996Attachment 3997Attachment 3998Attachment 3999Attachment 4000

Let me know if you need more.

Ah, that's what I thought. you're still using the EVO XML for EVOScan, not mine. that's also why you can't log your wideband either.

Your data file is under the datasettings folder in EvoScan, what could I be missing?

Windows 7 and Vista have a feature called UAC. It makes a duplicate copy of your program files. This means when you try to install the EvoScan and EcuFlash .xmls, the changes won’t take effect, instead the duplicate .xml will be used

Try this! Uninstall EVOScan and ECUFlash and don’t reinstall them in C:\Program Files. Instead install to another directory created by you. For example C:\ECUPrograms\

V2 I'll have a different datasettings XML with revised instructions!

Now open up ECUFlash, go to C:\Program Files (x86)\OpenECU\EcuFlash\Chromed ECU v1.0 and open 23861006.bin. This file is a stock tune. If you've flash tuned your car before, you'll need to copy your tables to the new "Chromed" ROM. Sorry. I can assist with this if needed. It's a good idea to save this file under a different name. It'll still be linked to the correct definition file no matter what you name it or however many copies you make of it.


Chromed ECU v1.0 Features:

*larger fuel and timing maps (high and low octane)
*Ability to control fuel cut (called Boost Limit)
*Ability to run larger than stock fuel injectors
*All MAF tables defined
*Fuel Trim cut offs
*custom MUT 3 table setup for my custom data file for evoscan
*ability to log wideband thru pin 93 of the ecu (LC1 and AEM EUGO only for now)
*ability to log boost with AEM boost gauge thru the MAP sensor pin
*peripheries mapped out so the user can enable/disable CE lights
NOTE!!! Just cuz the CE light isn't on doesn't mean you will pass the OBD2 tests. I haven't even started looking into that area of the code yet
*stock boost control (98/99 VR4 ecu only!!)
*stock boost gauge modified to show engine load in a more useful manner (98/99 VR4 ecu only!!)


Chromed ECU v1.0.1 Features everything from 1.0 in addition to:

*Every table is converted from LOAD based units into Air MASS (g/cyl).
*"Boost Cut" is now named "Fuel Cut"
*"Air Mass" has been added to the EVOScan file. This is a 2byte log request that can be substituted for 2 byte LOAD.

Link found here!


Chromed ECU V1.1 Features everything from 1.0 in addition to:

*"Boost Cut" is now named "Fuel Cut"
*All the BCS tables have been adjusted to work with the EVOX Map sensor.
*Stock Boost gauge is now 100% accurate. The number you see on the gauge is what you got inside the plenum!
*BSC Corrections actually work as they should!
*Datalogging Boost (MDP) will now work with the EVOScan with the sensor installed.
*All tables are still LOAD Based like 1.0. v1.1.1 (coming soon) will have AirFlow Based tables.

Link found here!


Follow up

I've decided to make this patch DONATION-ware meaning if you use this on your car, shoot me a little something that you feel it's worth. There have been countless sleepless nights put into this project obsessing over all the little details.

Tuners: If you use my for tuning customer cars, I'm going to ask for $100. There's nothing I can do to enforce this so I'm just going to trust you guys to be honest with me on this.

paypal - nonstopmix@gmail.com

Also, the MAN behind the curtain deserves a little something for all this too. This guy is my fishing instructor. He's taught me everything about the H8/500 programing language and has played a MAJOR role in the development of this disassembly. The man is Jeff aka Gatecrasher. Please send him a little something too for dealing with my endless newb questions.

paypal - jeffv@xtreme3s.net

Special Thanks to the following board users for their generous donations!
*Chargerx3
*bboyalan
*Drummer
*Green Lantern
*Greg @ USCPerformance
*jazz9
*Jesters Deadd
*Zybrainn
*rmelton

[Greg E]

Disclaimer

While I've provided a dis-assembly for you to flash tune your ECU with, I can not accept responsibility for any damage caused to your motor or ECU from improper use. It is up to YOU the user to spend the time reading and researching how to handle this software.

If this all seems a bit much to take in, I'm offering my flash tuning services for $250. This includes free updates of any ECU patching I come up with in the future. I can tune your car via email or I can come to your door. Just PM me to setup a date & time. Most of my past customers have just made the trek out here but I'm more than willing to fly to you if you can put me up for the night and pay for my travel costs.


Tuning

I've posted up "how to's" in the past but the absolute best resource for learning how to use ECUFlash and EVOScan are on EVOm. Even though these threads/videos are based on the EVO, the 3/S shares many similarities. Take your time to really read and understand what's all going on. If you have to watch the training videos a dozen times before it sticks, then so be it. It's a LOT to take in and you're not going to become an expert over night. I've been playing with this for about 3 years and I'm still learning new things all the time!

Must Read before using software!
ECUFlash Tutorial for Beginners
Can't flash/read Rom? Start here!
ECUFlash/EVOScan Training videos
How to Tune an EVO
Injector Scaling & Latency
How to Scale your MAF


These links should contain most of the info you need to know. Of course I'm available to assist with any questions you may have, but keep in mind, I can't educate every single person individually. There's no such thing as a stupid question but it's ridiculous to have to answer the same questions that are already answered in the links above. Even so, I will do my best to help where I can.

Take your time to read and learn all this!

In the following posts, I'm just going to outline some of the things custom to the Chromed ECU ROM.

[Greg E]

Big Maps

The stock fuel map is only 15x15 cells and the stock timing map is also a pitiful 20x15 map. What I've done with the big maps is combined unused/unnecessary maps in the ROM and made 4 15x30 cell maps.



All 4 big maps share the same axis and they are completely independent from the rest of the ROM so you are free to scale them however you'd like. These maps are a translation from a the stock ROM and are not modified in any way. My EVOScan file is setup to log the RPM and Load addresses the ECU uses to look up these tables so tuning is more accurate.



Boost Limit

This is more commonly known as Fuel Cut.



How this works is the if the ECU detects the engine load is >= the value in the table for > 1 second, it cuts the fuel.

This is an excellent safety feature of the stock ECU! Especially if your wastegates accidentally get disconnected or your over boost while accelerating too hard in a high gear.

The MAX value you can set in this table is 319 load. This is a limitation in the code which I'm working to increase. For now, I doubt there will be many cars that see load values anywhere near this level. This is also why I set the max Load value in the BIG Maps to 320.

[Greg E]

Tuning with the stock Boost Controller

If you plan on running a MBC or aftermarket EBC, this post can be skipped!

While our ECU code shares many similarities with the EVO, the VR4 BCS (boost control system) is a bit more primitive.

The biggest problem and why so many aftermarket controllers do such a bad job, is that all the response characteristics of the turbo & engine change so radically with small changes in environmental conditions and/or driving style. It's difficult to get them stable and still responsive under all conditions... Mitsu's answer to this was to have a BCS that functioned off RPM and Engine Load.

The Boost control signal is a constant 16 HZ with varying duty cycle dependent on RPM. Boost solenoid is energized when the ECU pulls the white lead of the solenoid to ground. Logging this Waste Gate Duty Cycle (WGDC) from MUT request 86 shows:

RPM - WGDC
2000 - 100% Constantly energized = BCS open
3000 - 80%
4000 - 70%
5000 - 55%
6000 - 46%
7000 - 44%



The highlighted column in yellow is boost, the orange is WGDC. BTW you are seeing that correct. My stock car is boosting just over 13psi stock and it tapers to 7 by the redline. This has been verified on 2 other 99 VR4s. The service manual claims 2G cars only boost 10psi stock and as you can clearly see, that's understated! There's a reason for this. Keep reading.

Picking apart the code, I found there's actually 2 tables for WGDC. Turns out, the ECU uses the Octane value to interpolate between the 2 just like the fuel and timing tables. So if knock is detected, the ECU will lower the boost to compensate. These are the high and low octane Base WGDC tables.



This is just the start. The ECU also has a correction to compensate for Engine Load. Because of this correction, Air Temp, Barometric Pressure and even what gear you're in are compensated for. Unfortunately, this also means you're going to see more boost at the temps rise outside. This is because warmer air is less dense and the ECU will see a lower engine load as a result. So to compensate for the lower engine load, the ECU will raise the boost. This is why we have the variance between cars about how much they boost.

There are 4 tables for this. High & Low Target Engine load. 2 are not used and have been omitted from the Chromed ECU xml file.



What the ECU does is it takes the actual engine load, compares it to the target, then adds/takes away duty cycle to compensate. How much or little to compensate for derives from this table:



The WGDC correction algorithm operates on timer and I have found the delay time setting that sets interval between WGDC corrections! The stock value is 10. The scaling appears to be 1 unit = 0.08 sec, so 10 units is about 0.8 seconds. This is how often it updates the correction. Since the stock BCS isn't nearly as responsive as some of the aftermarket solenoids out there, there's really no point in changing this so it's been left out of the Chromed ECU xml file.

There are a few other tables too but I don't feel they are really needed. One is a correction for TPS, the other is a Minimum Load for Boost Control table.



The TPS table is self-explainitory. The Min Load table is just when the ECU energizes the BCS. I think they put this into the code to prolong the life of the solenoid so it's disabled during low throttle cruise.

Also discovered another table which is a correction for coolant temp.



Basically, you're stuck with wastegate pressure till the coolant gets to about 122 degreesF and you don't get your desired boost until the motor is completely warmed up. Neat little feature.

Also I discovered that 159load is NOT the max for the corrections. Just like the MAF, there's also an adder value (pictured above). The code brings in the target load value, adds the offset, then checks the actual load before making the corrections. So really, the max load you can tune the corrections for is 319load.

Tuning is fairly easy although time consuming.

First you zero out the Load Error Correction table and tune your boost curve via adjust the Base WGDC (High Octane) table. It works just like an AVCR. Log your boost, RPM & load and make adjustments as necessary to the WGDC table till you're happy with the end results. Next, take the Load column, Add the offset value to it, then plug those numbers into the Target Load tables. Finally reenter all the values back into the Load Error Correction table and you're done!

update: I have corrected the inconsistency and it works great!!

Setting the Base WGDC table to 100 (left the low octane table alone) & disabling the Corrections table my car only boosted to 16psi and fell to 10 at the redline. We all know with the wastegates disconnected, 9Bs can boost a LOT higher than that.

This is because the stock BCS is a bleeder type setup. Unlike your MBC or all aftermarket EBC's, the stock BCS bleeds air away from the wastegates in order to keep them shut longer. I've found that removing the restrictor pill in the BCS will enable it to bleed significantly more air away.

Stealth 316 - Free Boost Mod for 1991-1993 3000GT/Steath

Caution: If you do this mod, start by setting your Base WGDC tables to AT LEAST 50%. You'll get an unpleasant surprise if you don't.


v1.0.1 Works the exact same way, only instead of Load numbers, you now see Air Flow numbers!

[Greg E]

Peripheries & Disabling Secondary O2 sensors

If you're only running 2 O2 sensors, you can disable the secondary ones in the code without getting a check engine light. Unfortunately, as a result, if you're an OBD2 car, your cat efficiency tests will never be set to Ready and Pass. Just a word of warning. Same goes with any other periphery bit you disable. I'm working on a patch for this.

EDIT: I have finally got the peripheries correctly mapped out. If you leave Periphery 0 alone, you will have no issues. Even if you have a vac-reduction do not disable the periphery 0 functions. Your car will run like ass because those functions are used to calculate IPW. Just disable the CELs in periphery 2.

These are the correctly mapped peripheries. Chrome V2 will come with this, however, you V1 guys will need to open your 23861XX6 XML, delete the old tables and replace them with this code:

	<scaling name="EnableDisableBit" storagetype="bloblist" storagebits="1">
		<data name="Off" value="00"/>
		<data name="Enabled" value="01"/>
	</scaling>

<table name="ECU Periphery0 Bits (272) +0" category="Periphery" address="10272" type="2D" scaling="EnableDisableBit">
		<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
			<data>bit.15                                               .</data>
			<data>bit.14  O2 Heater Functions                          .</data>
			<data>bit.13                                               .</data>
			<data>bit.12  Purge function                               .</data>
			<data>bit.11  EGR function                                 .</data>
			<data>bit.10  Timing Retard on Accel                       .</data>
			<data>bit.09  Cat Warmup Ign Retard Function  (Leave OFF)  .</data>
			<data>bit.08                                               .</data>
			<data>bit.07  Knock Sensor/Octane Functions                .</data>
			<data>bit.06  Speed Limit Function                         .</data>
			<data>bit.05                                               .</data>
			<data>bit.04  Closed Loop function                         .</data>
			<data>bit.03                                               .</data>
			<data>bit.02  OBD2 Bytes A and C                           .</data>
			<data>bit.01  OBD2 Bytes B and D                           .</data>
			<data>bit.00                                               .</data>
		</table>
	</table>

	<table name="ECU Periphery1 Chrome Mods Bits*" category="Periphery" address="10282" type="2D" scaling="EnableDisableBit">
		<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
			<data>bit.15                                               .</data>
			<data>bit.14                                               .</data>
			<data>bit.13                                               .</data>
			<data>bit.12                                               .</data>
			<data>bit.11                                               .</data>
			<data>bit.10                                               .</data>
			<data>bit.09                                               .</data>
			<data>bit.08                                               .</data>
			<data>bit.07                                               .</data>
			<data>bit.06                                               .</data>
			<data>bit.05                                               .</data>
			<data>bit.04                                               .</data>
			<data>bit.03                                               .</data>
			<data>bit.02                                               .</data>
			<data>bit.01                                               .</data>
			<data>bit.00  Chrome Mod Lean Spool                        .</data>
		</table>
	</table>

	<table name="ECU Periphery2 Bits (292) +0" category="Periphery" address="10292" type="2D" scaling="EnableDisableBit">
		<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
			<data>bit.15 P0443 P0446 P0403 P1104 P1105 Solenoids Test  .</data>
			<data>bit.14 P0450 Fuel Tank Pressure Sensor Test          .</data>
			<data>bit.13 P0442 Evap Incorrect Purge Flow Test          .</data>
			<data>bit.12                                               .</data>
			<data>bit.11 P0135 P0141 P0155 P0161 O2 Heater Test        .</data>
			<data>bit.10 P1400 MAP Sensor Test                         .</data>
			<data>bit.09 P0403 EGR Solenoid Test                       .</data>
			<data>bit.08 P0505 Idle Control System Test                .</data>
			<data>bit.07 P0170 P0173 Front Rear Fuel Trim Test         .</data>
			<data>bit.06 P0125 Excessive Time to Enter Closed Loop     .</data>
			<data>bit.05 P030x Misfire Detected (set with bit 4)       .</data>
			<data>bit.04 P030x Misfire Detected (set with bit 5)       .</data>
			<data>bit.03 P0136 P0156 Front Rear Secondary O2 Sensor    .</data>
			<data>bit.02 P0130 P0150 Front Rear Primary O2 Sensor      .</data>
			<data>bit.01 P0421 P0431 Warmup Pre-cats Efficency Low     .</data>
			<data>bit.00 ALL OBD2 DTC Lookups                          .</data>
		</table>
	</table>

	<table name="ECU Periphery3 Bits (2A2) +0" category="Periphery" address="102a2" type="2D" scaling="EnableDisableBit">
		<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
			<data>bit.15                                               .</data>
			<data>bit.14                                               .</data>
			<data>bit.13                                               .</data>
			<data>bit.12                                               .</data>
			<data>bit.11                                               .</data>
			<data>bit.10                                               .</data>
			<data>bit.09                                               .</data>
			<data>bit.08                                               .</data>
			<data>bit.07  P0551 Power Steering Pressure Sensor Circuit .</data>
			<data>bit.06  P0500 Vehicle Speed Sensor Malfunction       .</data>
			<data>bit.05                                               .</data>
			<data>bit.04                                               .</data>
			<data>bit.03                                               .</data>
			<data>bit.02  P1103 WasteGate Actuator Malfunction         .</data>
			<data>bit.01  P0510 Closed Throttle Position Switch        .</data>
			<data>bit.00  P1600 Battery Voltage Low                    .</data>
		</table>
	</table>

[Greg E]

EVO MAF install (no, not MAP )

Here are the values you need to change to run an EVO 8 or 9 MAF.



MAF Size = 357.5
MAF Adder = 140

After that, plug in your EVO MAF and never have to worry about MAF overrun again.


Special thanks to Adam (Jesters Dead) for the underhood install instructions!!
http://www.3sgto.org/f2/montero-482-...ster-8224.html

[Greg E]

Q/A section

did you get rid of the ignition warmup reatard map? I see you disabled it in the periphs in your 1106 bin. Did you use it for the big maps?

Yes, the warmup map is gone. That bit has to be disabled otherwise the car will run like absolute crap until the water temp is over 160.

I recently deleted the EGR, evap, and rear o2 sensors. I have been able to disable most of the CELs except for P0141 Heated Oxygen Sensor Heater circuit Bank 1 Sensor 2. In periphery0 bit02 (0=Disable downstream O2 heater and sensor, both banks) , I changed it to 0, but it still didn't get rid of the CEL. I looked through the rest of the periphery bits but didn't see one that listed P0141 or bank 1 sensor 2. Anyone else have this issue?

In the Periphery2 Bits, the only ones I have set to 1 are 00, 04, 05, 06, and 08. I don't have any CELs.

will targeting leaner at low loads have any affect or will closed loop operation still pull it back to 14.7?

Closed loop still pulls it to 14.7.

Also, out of curiosity, what is your reason for leaving the (MAF) scaling table alone? I did all three for an VIII MAS as you probably recall.

The scaling table you used is setup for an EVO intake/innercooler/piping. When I used the EVO values on my stock 99, the trims got a bit out of whack.

Think of the scaling table as a HZ to airflow conversion table. Raising/Lowering the values on the right side of the table will tell the ECU to add/subtract more IDC for that particular HZ value. Use the fuel trims as a guide to fine tuning the scaling table if you have upgraded intake/innercooler/piping and you can't get the trims between +/-5%.

So is there any reason the EGR is disabled by default? I kept EGR on my car to help with combustion chamber temps and fuel economy... Any downsides to me putting a "1" in that box? I do have EVAP taken out though...?

Good catch! That bit is backwards for some reason (disabled = enabled) You should leave it as 0 otherwise you'll get a lopey idle.

Because you don't have the factory MDP sensor which the Flashable ECU uses to operate the EGR and you'll get a CE light. The valve will still function because it's operated by vacuum and throttle plate position, HOWEVER, there are some side effects without ECU control:

*won't be disabled during engine warm-up
*won't be disabled during light cruise
*won't be disabled above 4000 RPMs (not really sure what side effect this will cause to be honest)

If enough people want to keep their EGRs in their cars (better fuel mileage) I could set something up where the ECU could use the GM Map sensor. This would just be a matter of finding the table which the ECU uses to scale the factory MDP sensor and scale it for the GM sensor. Then it will work as it should. Update: I have the setting for the EVOX MAP sensor now.

I'm fairly certain there is a difference in the spring tension in EGRs between the earlier cars and the ones used in the OBD2 vehicles so a later gen EGR will need to be swapped in as well (could someone confirm this in CAPS?).

Hm.. Looks like I should just delete it then to be safe. I would love to reduce the clutter, just didn't want to take functionality from the car (some websites said it helps with fuel economy/temps but who knows how accurate that it. Disabling the trims and doing a lean cruise will probably more than make up for EGR anyway, huh?

Also, should I disable the bit that has to do with EVAP? Sorry for all the questions I just want to make sure all the bits do what I'm expecting them to lol

The evap operates under almost the exact same as the EGR. I noticed on my 98 sometimes there's this odd stumble when I let off the gas cruising down the free way. I think this is because I have the MAP periphery disabled for the EVO MAP sensor. Logging this occurrence shows a rich condition when letting off the throttle. My guess is the EVAP is sucking in fumes from the tank which is causing this. The evap is supposed to be closed but since the ECU doesn't have the stock MAP sensor, it doesn't know what to do with it.

I was going to experiment with putting the stock sensor back on and see if it goes away.

Seems like you're pretty well versed with flashing the 99 ecu. Just had a few questions

I was looking into boosting a 99 sl and figured theoretically i should be able to get away with just flashing the stock ecu for larger high impedence injectors and whatnot. Do you foresee any problems with something like this on the stock SL ecu rom file??

Im not looking to really move to the 99 vr4 rom file or 99 vr4 ecu itself which apparently (from what ive read and not quite sure) has a different knock sensor circuit? i would assume the sl ecu knock circuit would be pretty aggressive since its got 10:1 comp but i could be wrong....

Also, emissions (rear o2 sensor CELs) any way around this??? Id like to be able to throw a cat into the car when its emissions time and hopefully pass. i dont think it'll be a problem but... just curious if you had run into anything like this yet.

This topic has been beaten to death but some details get fuzzy. Let me try to clarify.

You MUST run the VR4 ROM on your SL ECU. It has too many limitations. I have not and probably will not do any more disassembling of the NA ROM. There isn't much reason to.

You can probably get away with running high impedance injectors to avoid wiring in the TT injector pack, but why....?

You will also be missing the fuel pump switch, stock boost gauge and the BCS. None of that is a big deal though.

The SL ECU knock circuitry is supposed to be wired up just like the VR4. The filtering is all done in the code (which will all be setup as it should if you run the VR4 ROM). You will be screwed trying to tune 10:1 on pump gas though. There's just too much heat and you will detonate under low boost.

I know the EGR emissions are setup similar on the SL as the VR4, but I'm also fairly certain the purge solenoid is different. Unless you wire and route everything up like a VR4 which is going to be tough/expensive (even though all of that can be disabled) you will NOT pass OBD2 tests. There is no legal way around this.

Alright I am having a problem with my car (had the problem before and I just did the fuel system/98 ECU) and am wondering if there is way I can check to make sure the ECU is flashed correctly?

ECU flash said it worked fine...

Try to flash the exact rom you are running on to the ECU again, and it will just list Yes for everything and not actually do any flashing.

Where do the old diagnostic wires end up? I have a drbII that should still work to check on abs, srs, ecs...etc, it gets its power externally so that won't be a problem. I assume it should still work unless the old ecu diagnostic wire(s) has some sort of funky voltage on it.

That will all be hooked up and function like stock thru your OBD1 connector. The conversion harness that Brett sells include a new separate OBD2 connector for the flash wire and tactrix cable.

well the GM sensor has 3 wires...one goes to the ecu (jester was nice enough to put me a nice connector to hook it to my harness) but the other two I would guess one goes to a 5 volt and one to a ground. I could be way off on that. I have a wideband in my tdo5 car and it can get annoying to have sometimes, especially at night, plus I would just like it to be a little different.

Coop

All sensors have a power, ground and a signal wire coming out of the ecu. They did this to maintain consistency with all of them.

You will need to wire the map sensor to the ecu using pin 92 as the signal, Pin 42 is power, pin 49 is ground. Wiring the sensor, you can use the EGRT since it is not used by the flashable ECU but it only has signal and ground wires. You'll have to run the power wire into the engine bay or tap the TPS power.

There is another 5V sensor for the fuel tank on the 98/99 cars just like the one on the plenum. This sensor also has its own power, signal and ground. On my car I replaced the fuel tank pressure sensor with the LC1 wideband. Jeff was the first to try this so make sure you give him the credit for this idea.

The signal for this sensor is pin 93 and I have the 5V output of the wideband hooked to this as well as the power and ground for constancy. Again Pin 42 is power, pin 49 is ground. I don't have the gauge hooked up but thats easy to setup. My version of EVOScan is set up to read the AEM and LC1 widebands thru this pin.

Hope this clears everything up.

[Greg E]

V1.0.1 is ready for testing! Setup is the same as 1.0.

http://tinyurl.com/7rldxbz

Changes:

*This converts every table from LOAD based units into Air MASS (g/cyl). All the functions of 1.0 are retained.
*"Boost Cut" is now named "Fuel Cut"
*"Air Mass" has been added to the EVOScan file. This is a 2byte log request that can be substituted for 2 byte LOAD.


Disclaimer

None of this is tested. Although the math makes sense, please report back any inconsistencies or bugs you encounter!

Going to release v1.1 which will be Load based again paired with v1.1.1 which will have the Air Mass conversions. V2.0 will not have a Load based counterpart. Everything from here on out will be Air Mass.

[Greg E]

V1.1 is ready!

http://tinyurl.com/7rldxbz

V1.1 has all the same features as v1.0 only it's been adjusted to take full advantage of the EVOX MAP (Not MAF ) sensor! The idea is to datalog boost pressure using EVOScan and the flashable ECU as well as take more advantage of ECU based boost control...

Changes:
*"Boost Cut" is now named "Fuel Cut"
*All the BCS tables have been adjusted to work with the EVOX Map sensor.
*Boost gauge is now 100% accurate. The number you see on the gauge is what you got inside the plenum!
*BSC Corrections actually work as they should!
*Datalogging Boost (MDP) will now work with the EVOScan with the sensor installed.
*All tables are still LOAD Based like 1.0. v1.1.1 (coming soon) will have AirFlow Based tables.


Prerequisite

The OBD2 cars have a 1 bar MAP sensor that can only measure up to 2.2 psi of boost and is located on top of the intake plenum. The ECU mainly uses this to operate the EGR. The EVO 10 uses a 3.25 bar MAP sensor that can measure up to 32 psi of boost. This sensor is nearly identical in appearance to the stock sensor, so it can be easily swapped in for some plug and play fun.

If you pop off the stock sensor, you'll see a space with a small hole. I believe this cavern is just an area to keep air turbulence away from the sensor so the readings are more accurate. Here are the 2 sensors side by side. Note: the EVO 10 sensor is the one with the yellow cap on it.




No one would have a clue...


Part number for this sensor is 1865A052 and it's available for $145.16 plus shipping thru

[img]http://www.omnipowerusa.com/product.asp?P_ID=157]MitsubishiParts.net - Your #1 Source for OEM Parts and Accessories

Now, you 91 to early 95 guys will need the intake plenum from a 95.5 to 97 VR4 to use these sensors and you'll have to wire it into pin 92 on your flashable ECU. ALL flashable ECU's have this pin as the MAP sensor input (not just the VR4 ECU guys!)



Tuning

Tuning is the exact same principle as LOAD/AirMass based boost control. I edited the Corrections table with more conservative adjustments to avoid the BCS "chasing" itself.



First set all the values in the PSI Error Correction to 0. Then tune your boost curve with the the Base WGDC (High Octane) tables. After you're satisfied, set the Target Boost to match (don't forget the offset value).

7psi is the MAX Target in the tables. If you want to run say 16psi, you'll need to make the offset value 9psi.

This is has been very thoroughly tested on my cars so I'm not anticipating any bugs.

[green-lantern]

Mines already been chromed