Conditions for ECU to switch from High to Low Octane Maps?

EVOXSILVER · Jul 9, 2009, 12:55 PM

My car has bad knock (3 to 7 knock counts) from 6600 to 7800 rpms so i've decided to pull timing from my maps. I've noticed from the logs that my car is running on low octane timing map, why?

LaXGSR · Jul 9, 2009, 01:10 PM

Quote:

Originally Posted by EVOXSILVER

My car has bad knock (3 to 7 knock counts) from 6600 to 7800 rpms so i've decided to pull timing from my maps. I've noticed from the logs that my car is running on low octane timing map, why?

Are you sure it's running on the low octane timing map? Note that the ECU will make corrections based on knock, air temperature, altitude, etc. There are various compensations made by the ECU that would cause you to see lower timing than your high octane map (even with no knock present). If the ECU sees a lot of knock continuously, then the "octane level" will be dropped, causing it to interpolate between the high/low octane maps. Log octane level and see what is it at.

EVOXSILVER · Jul 9, 2009, 01:26 PM

LaXGSR thank you for your quick answer,
You're right i'm not sure it's running on low octane map but the timing values from the logs are very close to the low octane timming map even with no knock counts. Last time i logged the octane level it showed me a static value which won't change through whole rpm range.
My air temperature is pretty high, about 90F.
Altitude is sea level
Knock is present on 6500 to 8000 rpms, 230 to 200 load cells.
i've attached the log if it can help.

PS: Wondering if my ETS intake would be heat soaking? does it make sense?

LaXGSR · Jul 9, 2009, 01:43 PM

It's very possible that your intake is just getting heat soaked and the ECU is compensating for that. You can log intake air temperature and manifold air temperature for a better idea. Or, just try driving on the highway for 5 minutes to minimize heat soak and immediately do a pull - see if that allows your car to run more timing. I also have not personally seen octane level drop - I would try logging it during these runs though just in case it does change.

EVOXSILVER · Jul 9, 2009, 01:56 PM

I'm using evoscan mode23 for logging, do you know if anybody found the address for 526900015-18 Intake air Temperature and Manifold Air Temperature?

GST Motorsports · Jul 9, 2009, 02:17 PM

Quote:

Originally Posted by EVOXSILVER

I'm using evoscan mode23 for logging, do you know if anybody found the address for 526900015-18 Intake air Temperature and Manifold Air Temperature?

EVOXSILVER · Jul 9, 2009, 03:58 PM

Thank you very much mister GST or should i say "Mister Can Address"

impressive

EVOXSILVER · Jul 9, 2009, 06:27 PM

Just wondering if anybody knows in Evoscan to what ECU ID correspond the EVOX, EVOX 08 and EVOX 09? ie: EVOX=526900015

SiC · Jul 9, 2009, 07:00 PM

Quote:

Originally Posted by EVOXSILVER

Just wondering if anybody knows in Evoscan to what ECU ID correspond the EVOX, EVOX 08 and EVOX 09? ie: EVOX=526900015

If Hamish put my xml in the release version, the EvoX08 & 09 are the JDM/EDM version. The normal EvoX is the USDM 08 version. I'm not too sure what 52690015 is.......

EVOXSILVER · Jul 9, 2009, 07:29 PM

HI SIC and thank you for your interest,
For info, EVOX works good for me only thing is that TPS seems to be capped at 87%.
EVOX 08 does not work (it gives me out of range values)
EVOX 09 works good (RPM, Timing, Load...) and i still need to check TPS.
I'm on a map 526800018 which inherits from 526800015.

EVOXSILVER · Jul 9, 2009, 07:33 PM

Do you guys know if there is a thread with the final XML definitions for each models?
I've noticed that unfortunately the 3 different definitions for EvoX in evoscan won't show the same list. ie: EVOX has not IAT since the other 2 have.

SiC · Jul 9, 2009, 11:05 PM

Quote:

Originally Posted by EVOXSILVER

Do you guys know if there is a thread with the final XML definitions for each models?
I've noticed that unfortunately the 3 different definitions for EvoX in evoscan won't show the same list. ie: EVOX has not IAT since the other 2 have.

TPS is capped at 87% when you use the generic TPS address. I think mrfred found the address & calculation to correct the TPS reading & he also posted the latest xml for the USDM in this thread.

EVOXSILVER · Jul 10, 2009, 12:54 PM

HI SIC, my 87% is capped from the mode23 address which is 238086F9 not the generic CAN one.
BTW i haven't been able to find the lastest XML File, i found only the EVOSCAN 2.6 beta 16 which is the one i have. Please could you help?

SiC · Jul 10, 2009, 05:07 PM

Quote:

Originally Posted by EVOXSILVER

HI SIC, my 87% is capped from the mode23 address which is 238086F9 not the generic CAN one.
BTW i haven't been able to find the lastest XML File, i found only the EVOSCAN 2.6 beta 16 which is the one i have. Please could you help?

It's capped at 87% for both CAN & mode23. Please look at page 33 of the thread I posted above. mrfred posted up the latest xml in which he started adjusting the 87% to make it closer to 100%.

EVOXSILVER · Jul 10, 2009, 06:46 PM

Thank you SIC.
Have you been able to use the function "map tracer" and "VS RPM" in the graphs?
BTW can you playback in realtime a log? I can only open my logs through the graphs.