Chrome, European '99 ECUs and the immobilizer

Hi all Chrome wizards!

I drive a 1999 Euro-spec Twin Turbo (VR4 to US folks). I acquired this one only recently and figured I'd be satisfied with the performance for a while, but.... you know. Less is not more in this case.

Anyway, from what I have gathered there are some unclear issues regarding the compatibility of Chrome with European ECUs. According to this thread, Chrome is not compatible with Euro ECUs: https://www.3sgto.org/threads/11123-...cu-immobilizer.

However, IF I have understood correctly, you can load Chrome into an Euro ECU without issues, according to the experiences of Marty K. and The-Stig in this thread: https://www.3sgto.org/threads/14400-...-Evoscan/page3.

Further, apparently the immobilizer present in European cars has presented problems for some, but others claim that installing Chrome (which is based on a US ROM) over the stock ROM should by itself eliminate the immobilizer, as its code is not present in the Chrome ROM. But contradicting that, the following thread has discussion regarding disabling the immobilizer via code (in the ECU). Also mentioned in this thread, a version of Chrome for Euro ECUs has been under development at one time (Ange has a version with limited functionality) (discussion regarding Euro Chrome on page one, immobilizer coding on page three): https://www.3sgto.org/threads/13173-99-euro-ecu-support.

Finally, I understand that Chrome has the functions present for controlling ECS and Active Aero, despite these features not being present in US '99 models. The European models were never updated past mk2, so the 1999 model is no different from other post-1994 models (with exceptions of the ECU and updated lifters).


So, what I'm asking is:

1. Can I install and run Chrome on my stock, 1999 European ECU?
1.1. Does the standard version available on the Chrome online store work, or do I need a special Euro version?

2. After installing Chrome, do I have to make Euro-specific adjustments to make my car run normally (pre-modifications)?
2.1. Are there e.g. special modifications needed for Active Aero and ECS to function when running Chrome?

3. Do I need to disable the immobilizer, or will it be automatically disabled by the lack of code in Chrome?
3.1. Is there some way to maintain the immobilizer function? I try to keep as many of the OEM functions as possible.

I'd be eternally grateful if the guys involved in Chrome tuning could spare the time to chime in regarding these issues. Flash tuning seems to be the absolute best way to tune, and I've always had problems with the idea of tricking the ECU (and its safety mechanisms) with piggyback systems.

Best,
NikkeR


EDIT: Realized I had omitted the actual questions from the post :numbness:

A long time ago I tested a European flash ECU on my car, using the stock rom image and adjusted the injector size that was appropriate for my car. What I came across was the immobilizer preventing me from starting the car (cranking was fine, it just wouldn't run). I spent time researching on the web on other Mitsubishi vehicles to try and figure what to do. I eventually made an educated guess at the rom location, and changed the four digit hex code to all zeros. That defeated the immobilizer.

Currently I run a 1999 3000GT VR4 ECU with it's stock rom image (non-Chrome), and the ECS functionality works just fine. Don't forget, the ECS has it's own computer, so it makes sense that it is unaffected. I don't have an active aero, so I can't comment on that.

If The-Stig can run Chrome on his Euro ECU, then I think the answered is settled, it works. The immobilizer should not be an issue, as it's done in the engine ECU software.

Quote:

---

Originally Posted by BlackStealth

A long time ago I tested a European flash ECU on my car, using the stock rom image and adjusted the injector size that was appropriate for my car. What I came across was the immobilizer preventing me from starting the car (cranking was fine, it just wouldn't run). I spent time researching on the web on other Mitsubishi vehicles to try and figure what to do. I eventually made an educated guess at the rom location, and changed the four digit hex code to all zeros. That defeated the immobilizer.

Currently I run a 1999 3000GT VR4 ECU with it's stock rom image (non-Chrome), and the ECS functionality works just fine. Don't forget, the ECS has it's own computer, so it makes sense that it is unaffected. I don't have an active aero, so I can't comment on that.

If The-Stig can run Chrome on his Euro ECU, then I think the answered is settled, it works. The immobilizer should not be an issue, as it's done in the engine ECU software.

---

Many thanks for your reply BlackStealth, this is great news! Looks like my car's going to be faster next Summer.

If it's not too much trouble, could you give me idiot-proof instructions for locating the correct rom and changing the code? My coding skills are limited to a couple of R classes, so I am for all intents and purposes a complete idiot when it comes to this. :confusion:

Quote:

---

Originally Posted by NikkeR

Many thanks for your reply BlackStealth, this is great news! Looks like my car's going to be faster next Summer.

If it's not too much trouble, could you give me idiot-proof instructions for locating the correct rom and changing the code? My coding skills are limited to a couple of R classes, so I am for all intents and purposes a complete idiot when it comes to this. :confusion:

---

I run 99' 3000GT EU spec. Flashing chrome disabled immo for me automatically. How I know - i installed remote start at the same time. So it will remote start without a key. Flashing back EU fw will not start the car with remote start.

Problem is that EU cars are missing MAP sensor. This will error out. You can get EVO map sensor and need to drill holes to the spot on the intake manifold. It's not a big deal. But you still need to figure out the pinout on the ECU. It gives errors for the sensor in ECU if you don't fix it. There was something else missing, but I can't recall what it was. BUT there is alot bigger problem - If airflow reaches 1600hz it will shut down the engine :jaded:

Don't know what's up with that. Because MAP is missing it will cripple the engine?
So in the end..i could do antilag and all kind of fancy stuff, but could not use it since I was hitting the 1600hz easily all the time.

There are few good non performance tweaks on the chrome version also. For example it will turn on fuel pump on igniton (not on cranking), making it start way better.

Thought I should update this.

I changed my plans slightly and instead of uploading Chrome I managed to modify my stock ECU software with BlackStealth's help. The reflash capabilities available for the '99 Euro ECU are much more limited than those available for Chrome, but enough for my application.

With EcuFlash I could change injector size and voltage latencies, target AFR and timing by engine load x rpm as well as "boost limit".
I had 550cc Bosch EV14 injectors installed, they came from a local injector specialist as a flow-matched set of 6 injectors with flows and latencies measured on a flow bench. I simply plugged the flow values and latencies provided on the injector test sheet into EcuFlash, reflashed the modified stock software via Openport 2.0 and it idles and drives smoother than stock :cool:

Unlike Chrome, the stock ECU does not allow for controlling boost. I am using BlackStealth's OLEDBC (LCDBC with an OLED screen) instead, which comes with so many handy features that it would be useful to have even if I had ECU-controlled boost. I'm still troubleshooting a boost overshoot issue - likely either normal full-throttle boost spike (wastegate lag) or a leaking wastegate vacuum hose - but otherwise everything seems to work fine.

The "boost limit" parameter in the ECU limits the maximum engine load value allowed by the ECU before it cuts the fuel. When I was testing and tuning the OLEDBC settings on the road, I briefly got it to work and going full throttle was like being rear-ended by a freight train... and then hitting a brick wall. For a split second I was sure I'd broken something... until I remembered that BlackStealth had advised me to increase the boost limit to the highest available value. Fuel cut during full throttle acceleration feels surprisingly violent.

The last one could cause the issue jannoke described in the previous post.

I haven't yet modified the AFR and timing tables, but will tune for a leaner AFR once I get the boost issue sorted. There's a general rule to tune for 11.5 AFR at max boost, tapering to 11.0 by rev limit which should be doable based on datalogging on the road. I'm not aware of a similar rule of thumb for timing, and the forum wisdom of "tuning until knock" seems somewhat risky to an amateur. Might leave the timing map untouched for now and have a specialist tune it on a dyno once I throw in larger turbos and intercoolers.

Hope someone finds my amateurish experimenting useful. Many thanks again to BlackStealth for helping out!