And what is the purpose of this? You guys want it to turn off earlier when doing WOT w/ ac on? or we just like messing with stuff :->

 

Why go through the labor of turning a knob when you can log, adjust, flash. JK. This ish is awesome- it never ends. More and more stuff is found everyday and I want to thank everybody for the work they put in.

 

Turning a knob? Are you talking about A/C on/off? When it's hot I turn it on, when it's cold or tolerable I keep it off? Are you sure you understand what this is?

 

I found the TPS levels this morning, and will post a map for them shortly. Default for my rom was above 82% to turn off and below 78% to turn back on.

It is MUT9A bit 0 for the true location in the code, but for some reason Evoscan wants bit 1 as the setting to make it log (as in the 1st bit that can be read).

 

First is the scaling to view it correctly, second is the map.


For 80700010, 90550001, 98640014, 94170014:

<scaling name="Percent16 (256)" units="%" toexpr="x/2.55" frexpr="x*2.55" format="%.0f" min="0" max="100" inc="1" storagetype="uint16" endian="big"/>


<table name="A/C Throttle Limits" category="Limits" address="1a28" type="2D" level="2" scaling="Percent16 (256)">
<table name="TPS" type="Static X Axis" elements="2">
<data>Off Above</data>
<data>On Below</data>
</table>
</table>


To clarify the Evoscan vs Ecuflash bit differences. Evoscan uses the decimal conversion of the binary, i.e. bit 1, 4, 8, 16, 32, etc... for its logging. This was evident from the default incorrect logging of MUT 4A for A/C, P/Steer, etc....

 

88580015 and 88590015 seems to be at 1628.



There looks to be some other conditions settings. One of which looks like an RPM below which it turns off the A/C, and then RPM needs to be lifted above another value to turn back on. Sort of an anti-stalling feature. There are some others I am still working on. These newer RPM settings I will test during the week.

 

@ Mattjin
can you check if logging 0xAC bit2 is the same as logging 0x9A bit0 ?

I haven't a logging cable at the moment.

 

I will check it out in the next day or so. I left the tuning laptop at work along with the cable, so no testing for a couple of days.

 

so just gonna edit my xml and and start up, ac on and slowly rev and datalog the evoscan that u advise above, right?

88580014 here.

 

Another map to add to the list. Below the rpm in this setting (DEFAULT = 406), the A/C will turn off.

For 80700010, and the other roms in the same earlier list :

<table name="A/C Lower RPM Limit" category="Limits" address="1a26" type="1D" level="2" scaling="RPMStatLimit"/>



EDIT: The 8858 series can be found at 1626 for this map. Most likely the same for all EVO 8 and 9, but worth checking.

 

Doesn't seem to be valid for 94170014. It shows "units" = 406. Maybe I don't have that scaling or my scaling is wrong?

 

406rpm is the default value. Someone may have forgot to make your RPMStatLimit scaling as RPM, its something you can edit if you like.

RPMStatLimit is the scaling used for almost all RPM related 1D maps. It has nothing to do with the Stationary Limit, just this is the name that was given to this scaling way back when it was first found.

 

I tried 1628 on my 88590015 rom and EcuFlash did not seem to like that location...

Anything I am missing here?

 

You are missing the scaling from post #20. You either did not add it as listed above, or you changed it.

Deepnine, I will do the checking on logging the bit tomorrow morning. Evoscan bits are displayed as decimal, so did you mean bit 2 as in 100 (bin), or 4 (dec). It would not suprise me if there is an A/C request input to log.

For those after 96530006, the Min RPM is at 1a26, TPS maps are at 1a28, and max RPM does seem to be at 21f2 as per l2r99gst's suggestion.

 

As per disassembly the both bits are of same semantic.