Hello. I am new to the forum, EvoX platform and ECUflash. I have read Merlin's guide to ECUflash and watched the introduction videos on youtube to better familiarize myself. I recently purchase a 2014 EvoX GSR. The car is not running and most likely has a blown motor. (Not confirmed yet) I was able to download and open the ROM files and have started to look over them. I was told the car was full bolt on and tuned on E85. It has since been returned to mostly stock. The timing maps look to be too aggressive for pump gas so I believe it was tuned for E85. I have the following questions and would appreciate if anyone would be willing to look at the ROM file and provide some insight. ROM ID 59580304.
1. When I plugged the Tactrix cable into car and computer I got two icons to read the ROM. I downloaded both. They seem identical except one has checksum errors upon opening and the other does not. Is this normal? Why does ECU flash detect two? Which one is the car using?
2. Does the newer XML definition have Mode23 already enabled? Merlin's write up covers how to enable but I already seem to have access to these setting in the Misc section. I took thee closest XML definition and modified the ROM ID and internal ID so ECU flash would open my ROM.
3. The fuel injector scaling seems extremely low at 203?? Is this even possible? Is the definition in my XML file taking the value from the wrong place or is there a multiplier somewhere? Any way to determine what injectors were being used?
4. Since the car is mostly stock and I may run pump gas moving forward can I flash a stock rom to the ECU and start tuning from new? Is there an immobilizer number with the EvoX ROM similar to the Evo8-9? Are there values I would need to match if using a stock ROM so as to not brick the ECU / ignition?

Thank you for taking the time to read this. I am uploading the ROM as a reference. Any help is greatly appreciated.

 

Hi,

a1. Ask the ecuflash developer why there are two 'read from ecu's flash memory ' icons in the latest version.
If just check sum does'nt match and no differences in the contents, no neeed to worry about.

a2. What is the "newer XML definition"?
If you mean that you opened your rom with ecuflash using 5958004.xml and check it but not sure mode23 was enabled or not, as long as looking your ROM with ecuflash using 59580004.xml, mode23 is already enabled.
FYI: If you want to use TephraXMOD V3 features, contact tephra and get the .xml definition for 59580304(your rom is a TephraXMOD V3).

a3. What is the ECUID of the xml file you're using? If you used 59580004.xml, the address seems to be correct.
Since your ROM is a TephraXMOD V3, so 'Injector Scaling Replacement' might be used. If you continue to use TephraXMOD V3, since you don't know which feature of TephraXMOD V3 is set in your ROM by previous owner, you have to reset the tables of TephraXMOD V3 properly so that it matches your current mods. If you don't use TephraXMOD V3, get and write a stock 59580004 rom.

a4. There's no immobilizer information in an ECU rom. No problem if you write a rom getting from someone else.

To me, pump gas timing map looks more aggressive than your timing map.

 

crimson red, thank you for looking into this for me.

1. I will check with the developers and post their response.

2. Yes, I opened the rom using 5958004.xml and thank you for the clarification. How do you know that my rom is a TephraXMOD V3?

3. I am not sure of the ECUID, it shows as blank when I open the ROM in ecuflash. Yes, is used 59580004.xml. If i get the Tephra .xml file will I be able to see which features were set by the previous owner?

4. If writing a rom from someone else, do I need to use my internal ID #?

Also, thank you for the clarification on the timing maps.

 

a2. Your rom id is 59580304. It is an extended id from 59580004.

a3. Using 59580004.xml for 59580304 is right. 59580304 is added some tables to 59580004 by tephra.
Yes. Using tephra's .xml for 59580304, you can see and edit TephraXMOD V3 tables including 'Flex Fuel'(Your car might be used it), 'Injector Scaling Replacement' and so on.

a4. Do you mean 'internalidhex' tag in your .xml? It is always same to the rom id(written in the 'xmlid' tag).
You can write a stock 59580004 rom without any problems. Ecuflash uses 59580004.xml to open the rom.
No need to edit the 59580004.xml.

 

Thanks for the clarification. This is making much more sense now.

posted on tephra.it are patches for the injector scaling. Can they be applied to the 59580004.xml I am using? There are no directions on the site as to how to edit the .xml file. I tried placing the scaling name line in the base evox .xml after the other scaling names. I placed the table names at the end of the 59580004.xml I am using. The injector scaling rescale 1-5 show up in misc section but no Fuel injector scaling replacement or fuel injector scaling alt map?

from tephra.it/v3

59580004:
<scaling name="InjectorScaling4x" units="cc/min" toexpr="29241*2*2/x" frexpr="29241*2*2/x" format="%.0f" min="1" max="1000" inc="20" storagetype="uint16" endian="big"/>
<table name="Fuel Injector Scaling Replacement" address="536d8" category="Misc" type="1D" scaling="InjectorScaling4x"/>
<table name="Fuel Injector Scaling AltMap #1 Replacement (Do others alt's well)" address="f1000" category="Misc" type="1D" scaling="InjectorScaling4x"/>
<table name="Injector Scaling Rescale #1 (0x80 -> 0x20)" category="Misc" address="55017" type="1D" scaling="Hex8"/>
<table name="Injector Scaling Rescale #2 (0x48 -> 0x46)" category="Misc" address="3bc2b" type="1D" scaling="Hex8"/>
<table name="Injector Scaling Rescale #3 (0x48 -> 0x46)" category="Misc" address="4121b" type="1D" scaling="Hex8"/>
<table name="Injector Scaling Rescale #4 (0x48 -> 0x46)" category="Misc" address="4a80b" type="1D" scaling="Hex8"/>
<table name="Injector Scaling Rescale #5 (0x48 -> 0x46)" category="Misc" address="4aadb" type="1D" scaling="Hex8"/>

 

Part of the patch(fuel injector scaling alt map and so on) reffer TephraXMOD V3 code. So It should be added into TephraXMOD V3 59580304.xml. As far as looking the values of these tables, your rom is set to use the injector rescaling patch.　You should get TephraXMOD V3 59580304.xml and add the patch into it if you continue to use the rom.

 

I was able to get in touch with Tephra and he was very helpful in setting me up with the correct .xml file. Thanks again.

I was able to apply the patch and can now see the correctly scaled values. Looks like the car was tuned on flexfuel with altmap#1 populated.

I do not understand how the boost was being controlled in the car? It does not look like direct boost is enabled. All three Boost target maps in load boost are zeroed out. This doesn't make sense to me as the boost limit is set to 319? Any idea what's going on here?

 

As far as seeing your rom, it is set to use 'psi based boost control (direct boost)'. The reason is that the 'Variable for Boost Control' table is set to 0xC76A and the 'SHLR-> SHLR2 'table is set to 0xC76A.

However, the value of 'Atomospheric Boost ' is for 'Load based boost control'. (If it is set for 'psi based boost control', the value should be 0 or 14.7).

From these points, it seems that your rom's boost settings are mixed(not correct).

And the 'Reactive Solenoid Base WGDC Map#1/#2' seems to be set for a 3-port solenoids(if it is set for stock 2-port solenoids, the values are too low) and the values are too aggressive. So even the values of 'Boost Target#1/#2' are filled with 0.0, the car might get a high-boost. But these mixed(confused) setting is not correct.

 

My understanding was that for direct boost to be used, all settings in that section need to be enabled?

I did a bit more digging and am wondering if the car was using a manual boost controller. I did read that when doing this the boost target values should be set to zero.

 

The tables in the section are not just enable/disable tables. If you decided to use the direct boost control(psi based boost control), you need to set these tables : 'Atmospheric Boost'(to 0.0 or 14.7), 'Boost Target #1A,#1B,#2'(proper values as psi), 'Target Boost Error Correction', 'Variable for Boost Control'(to 0xC75E), 'SHLR->SHLR2'(to 0x5102), 'Boost Error RAM Address'(to 0xC5CE), 'Boost Error RAM Address in Load Error Table'(to 0xC5CE).

If you can find an external boost controller like HKS EVC in the engine room, no matter ecu tables values are, your car's boost is controlled by it, not by ecu. But even in that case, I thinks this kind of mixed setting is not good(not beautiful).
Did you find an external boost controller(HKS EVC or so) in the engine room?

 

It turns out the car has the Grimspeed 3port EBCS installed. It was tucked under the factory solenoids. Only the WGDC tables seem to be set correctly and the target tables are all set to zero. Is it possible to have it work this way maybe so that the ecu does not try make any corrections? Seems odd. Either way I will be flashing a new base map to see if the motor is good with all the tables populated.

 

Be careful. Wrong tables are not just 'Target Boost #1/#1B,#2' table. 'Atmospheric Boost' table is also wrong. The value of the table is for load based boost control. If you forgot to modify this table correctly(set to 0 or 14.7), your turbo(and your motor) may be ruined instantly.

 

Car is running now. Thanks for all the help. I have other issues I need to address, major exhaust leak, leaking fuel line etc. hopefully the motor is ok but it seems to idle fine and fired up once I reflashed with correct parameters.

As a side note, I had to drain the entire tank of old e85 with a hand pump and refill with 93. Well worth it if the car runs!!