Hello,

Well after working out some bugs with the logging we were able to get some preliminary data for the 2011 Evo X.

Now I don't have a before for this car I really wish I did, but it had a 3 port on it and so we couldn't get a solid baseline. Oh well.

We are not done tuning and we don't have full logging support yet but we have enough to make the tune safe. I wish we had everything but I think we should have it fully supported soon. Special thanks to Hamish for getting it to me at 4am his time.

I will post a fully tuned sheet but this thing is making good power for the modifications which are the following:

Perrin TBE
Injen intake
GS 3port EBCS
AMS E Flash

I have yet to see any 2011 dyno charts so I figure I would post this up to show everyone. If I can find a little time I will post up the datalogs in excel so you can see some of the data. Timing is crazy lol.

http://i128.photobucket.com/albums/p189/Magnumpsi/2011EvoXAMSTune.jpg

Car has more go for sure!{thumbup}

Thanks,

Mitch Mckee

Which logging items are you looking for Mitch?

I sent Hamish a ton of logging stuff for the 2011's. If there is something you need, feel free to holla :)

I am almost tempted to go back to the mode21 stuff for logging - now that I understand it..

Much like MUT was/is - it keeps a standard list of logables from a standard request structure.

mode23 is sweet for development, but a PAIN for loggers...

/back on topic :)

Which logging items are you looking for Mitch?

I still dont have boost, load, STFT. They would be super helpful if anyone has them!

Mitch

you can use the MUT TABLE to find boost (MUT38) and STFT (MUT0F)

you can use the MUT TABLE to find boost (MUT38) and STFT (MUT0F)

I will try this and see how it goes.

Tephra, you are my hero!

Mitch

I still dont have boost, load, STFT. They would be super helpful if anyone has them!

Mitch

Try these:

Boost: 23808752

STFT: 238088D4

Load: 238087A8

2011 GSR 5689xxxx rom logging:


238087A8 Load
23808780 2ByteRPM
23808752 PSIG / Boost
23808A87 Knock Sum
238088D4 STFT
23804573 LFTF Idle
23804575 LTFT Cruise
238088E5 LTFT in use
238087AE Load (MIVEC) and (Timing if IAT GT 75F)
23808731 TPS
23809625 Accel Pedel Position
23808A43 TimingAdv
23808B91 ActiveWGDC
2380868F Intake Air Temp
23808673 Coolant Temp
23808695 Manifold Air Temp
2380AB1C IPW
23808FA4 MAF Volts
23809546 INVVT (Target)
23809552 EXVVT (Target)
2380957E INVVT (Actual)
2380958A EXVVT (Actual)
23808823 Speed
23808727 Battery
2380AAE1 Barometer
23808A8D knock_adc_processed
2380AB13 knock_base
2380AB0F knock_var
2380AB15 knock_change
23808A9B knock_dynamics
23808135 knock_flag
238086A1 Front O2
238086A5 Rear O2
238045C5 Cruise Light

Jesus Golden are we linked to the same brain now? We are constantly posting at almost the exact same time now!

It's getting a little freaky... hahah

LOL

Maybe... :nerd:

Well if it makes you guys feel any better I love you both the same amount?

Thanks a ton guys.

Mitch

Do you know the addresses for IDC, Load Error, and passive WGDC?

Do you know the addresses for IDC, Load Error, and passive WGDC?


Why do you need to log passive WGDC? It isn't affected by error correction so it never ever changes.

Why do you need to log passive WGDC? It isn't affected by error correction so it never ever changes.

I know that, but it is good to have a complete logging xml. The thing that bugs me the most is WGDC Correction. It works on the 2008 Evo X, but does not work on the 2010 (using Golden's code) and is not listed on the 2011. Since most of you Zero the upward correction, then you do not need this. I do not zero the upward correction and WGDC Correction comes in handy.

If you or golden have WGDCCorrection address for the 2010 and 2011, I would appreciate it if you can share it.

meh - I wont worry about correction or load error.

I know what the target is, and I can log ActiveWGDC, so I can roughly tell how much correction its running...

meh - I wont worry about correction or load error.

I know what the target is, and I can log ActiveWGDC, so I can roughly tell how much correction its running...

I would rather know exactly what correction is being run, rather than roughly tell.

So do you happen to have the correct addresses for WGDC Correction for the 2010 and 2011 Evo X? Would you mind sharing them?

Thanks

I know that, but it is good to have a complete logging xml. The thing that bugs me the most is WGDC Correction. It works on the 2008 Evo X, but does not work on the 2010 (using Golden's code) and is not listed on the 2011. Since most of you Zero the upward correction, then you do not need this. I do not zero the upward correction and WGDC Correction comes in handy.

If you or golden have WGDCCorrection address for the 2010 and 2011, I would appreciate it if you can share it.

I agree with tephra but I also agree with you in that is nice to have available to log.

I do not zero the upward correction. I zero the upward *additive* correction. Big difference. It can still do upward correction, up to base WGDC.

IDC is just IPW * RPM / 1200. I like to just do the math afterwards. If you look at any of the EvoScan definitions for it, you will find that the address for IDC is actually the address for RPM. So you can use the address for 2 byte RPM and make it:
[IPW] * 3.90625*x / 1200
(log 2 bytes)

I agree with tephra but I also agree with you in that is nice to have available to log.

I do not zero the upward correction. I zero the upward *additive* correction. Big difference. It can still do upward correction, up to base WGDC.

You zero the "max upwards duty cycle correction vs. tps" table. Boy is that a mouthful...LOL.

I remember once I tested setting the above mentioned table (not going to type it again) to 5 instead of 10 and the reactive turbo boost error correction would not go higher than 5. It usually maxxed out at 10. I prefer to have the ability to correct upwards because in some instances it comes in handy.

IDC is just IPW * RPM / 1200. I like to just do the math afterwards. If you look at any of the EvoScan definitions for it, you will find that the address for IDC is actually the address for RPM. So you can use the address for 2 byte RPM and make it:
[IPW] * 3.90625*x / 1200
(log 2 bytes)

Thanks Golden, I appreciate this.

Now about that WGDC Correction ;) I looked in the entire 2008 MUT table and could not find the 23808B51 that logs the correction accurately on the 2008 Evo. I even looked the MUT X and Y axis where it is supposed to be and the address is simply not there. Yet it logs WGDC Correction on the 2008 Evo X.

It is baffling to me that I could not find the address in the 08 MUT table. Can you find it? Maybe I can work backwards from the address and find the X/Y axis location and then look up that location for the 2010 and 2011 Evos.

For 568900xx, try 23808B8F
(WGDC Correction)