foxbat

This is my first time using the 88580714 V7 & I encountered a serious issue with ignition timing. I used it to tune a JDM E9 RS with a GT ECU (not the car's original ECU).
I kept getting knock counts around 6000-7000 rpm 250-260 load. Naturally, I kept reducing timing until timing figures became very low for the amount of load & gas used (93). Then I noticed that timing figures logged are actually much higher than the actual, corresponding cells in the timing table! As an example, the logged number at 7000rpm 250load is 10 while the number for 7000/250 in the table is 6!. Also, judging by the same log file, it seems that low oct timing isn't kicking in when knock is encountered! Low oct timing is at least 3 degrees lower than the main table.

Is it possible that my logged load numbers are off? Or perhaps the GT ECU doesn't like this rom version?
Before I started tuning I had to change mut00 & mut01 to 6b22 and 6b23 to be able to log load 2byte.

One more issue, I couldn't get launch control rev limit to work, the normal rev limit is 7606 default, I set stationery rev limit to 5500 but it didn't work!

I'd appreciate your feedback regarding the above issues.

Tuxevo

iTrader: (8)

Does your 2byte to 1byte load conversion in ecuflash and evoscan match up? IE, 1.2 and 1.2 or 1.4 and 1.4

foxbat

Well, I'm actually logging load 2byte, load 1byte is not even working. I don't think I have to worry about the conversion when logging 2byte... correct?
Anyway the 2byte to 1byte factor in ecuflash is 1.2 (default)
1byte eval in evoscan is 1.2 also (default)
2byte eval is 0.3125 (default)

Tuxevo

iTrader: (8)

I've never used the 8858 rom, but I was under the impression that all V7 roms used 1byte load as a reference as the representative value in the tables. If that is the case, I would think the first order of business is to be able to accurately log 1byte.

10isace

iTrader: (12)

Revive
Foxbat, did you ever get 1 byte or 2 byte load to log with the 8858 rom? I'm having trouble too. Neither one logs anything. MUT table appears to be correct, so I'm not sure what it is.

1 Byte Load = 840B at MUT41
2 Byte Load = 6B22 at MUT00 and 6B23 at MUT01

I'm going to try 8450 and 8451 for 2 byte load at MUT00 and MUT01 as that's what I have in the 8859, but I think that's the stock addresses. IDK, haven't used 2 byte load in awhile.

german_evoVII

I am running these roms more often, because we have some Race Cars here which using that version.

Load Logging:
2 Byte Load = 6B22 at MUT00 and 6B23 at MUT01 are correct, but are the uncompensated load.

So, as long as the turbo is inside the Efficiency Map, the Load will be app. The Boost in Kpa ( Absolute ) minus round about 10 to 15 Load ( Example: 26psi are 1.8 Bars or 280Kpa --> Load is 260- 270 in the medium RPM Range )

In High Rpm situations ( High Airflow ) it can happen that the "normal" load tapers to 210, but the comp load will be lower than that like 180 - 190 while still running 21psi aka 1.5 Bars aka 250Kpa. You see that the difference is about 40 load instead of 15 and the compensated is even lower...

If you get outside the Eff. Range of the Turbo, the Air Mass will go down, but the Boost could be stable. Same applies if you are getting a slight Vacuum inside the MAF.

Ignition timing will be calculated by "compensated Load"

As far as i know that will be 2byte load comp:
MUT 00 = 6B28
MUT 01 = 6B29
but not sure about that...

For the Rev limiter
Almost any JDM 9 RS has the Top Clutch switch installed, but is missing the wiring to ground an the ECU.., So there is no connector at the switch.
The only switch which is installed an wired ist the Lower one for the Engine Start - Clutch Breaker...

You have to wire it in for function of the NLTS, Rev Limit and Launch Maps

Steffen

JohnBradley

iTrader: (30)

Evo IX and earlier use 3 forms of 2 byte load -

Raw load
Load + baro
Load + baro + IAT 75*+

If you have correlations issues between your load value you log and the value that the car runs there is a good chance its this messing with you.

foxbat

That was a while ago, I had load 2byte working but the readings were off as I explained in my first post. If the reason is what JB mentioned then I wonder how to fix it? Is it by logging 2byte load comp, as German Evo mentioned?
The missing clutch wiring must be reason causing the rev limit not to work, although I have to mention that the rev limit was previously working fine on the same car when using an older v5.1 rom!

german_evoVII

Clutch switch was not required for the v5.1, but it is for V7 ...

I also had that problem when converting from an 5.1 to 7 Rom

Reason is the Launch control AND NLTS...

Try to log the comp Load and see if that correlates to the Timing map values...

10isace

iTrader: (12)

Thanks guys!!!

I was waiting until I could figure it out to reply. AUDM Evo IX running SD. Using the SpoolinUp EDM/JDM SD harness. Was trying to log load using the Baro hooked up to the map sensor with Baro at pin 51 IIRC. Changed the read baro ADC and change the request id in evoscan. Still no luck that way, so just switch the baro pin to 92 and all is good.

What do you Aussies use for SD in terms of wiring the map sensor? Anyone try the SpoolinUp SD harness going through the Baro pin? Just courious what needs to be changed in MUT table. Thanks!