does this mean that we can use 23808590 (for 0022) in EvoScan to log the stock boost error? The Evoscan I am using (0046) currently has 23808B50 listed for this, and it does not log. perhaps this is fixed in Evoscan0070...

 

You will need to use the "for logging" address listed in the XML

 

I am trying to log the boost error for a 2010 GSR, but I am having no luck. Here is my data setting in EvoScan (I've enabled the logging function in EcuFlash):

It just shows a constant -6.159. Do I have something incorrect?

 

Any of you guys try it out yet? How well does it work?

 

It'll be on mine in two weeks. I know my tuner wished it was out for the X when we were tuning my FPred, so I am sure it works as well as it did for the 8/9's.

 

I'm messing with it right now on a 2008 GSR.

It works awesome. I've made a couple of mistakes while setting the WGDC and it spiked a bit high, then the ECU pulled it right back to the boost curve I wanted and held it there to redline.

It's pretty easy.

My only issue now is that I don't like to run at the Max Error Correction. But it always gets maxed out when the car spools, because I am always under my target until I build some boost. It's ok if you floor it at an earlier RPM, but if you do it at a later RPM, the Error Correction gets maxed out.

I have increased the amount of WGDC it pulls when you over boost, and that works awesome. I like to set the Correction Interval to 3 (aka .3 seconds) so it does a bit more correction.

When this car is done, I'll post up the tables I used.

 

Are you liking it better than the load method of boost control?

 

I'm not sure yet. It is easier you use. But my car is already setup with load based right now, and I don't feel like retuning it.

 

Bump for my question on logging boost error, post #33.

 

One reason I personally like this system is that you can use it just as a tuning tool if you would like. Set the boost so that your load isn't changing it while you tune mivec, timing, and fuel...

I ran this full time on my IX, but I think I'll go back to load based once I'm done tuning to allow for changing weather conditions.

 

You need to log this as a 2byte

Or use A3 instead of A2

 

I did not see a definition posted for the 5269xxxx roms. I would like to test this on my MR wich is using Tephra's 5269xxxx. When I dropped the 52680022 into the 52690022 the addresses didn't check, though the tables showed up.
The addresses I get are
Variable boost control: Instead of 0C774 I have 346A
SLHR: Instead of 5101 I have 20B4
Boost error ram address: instead of C590 I have 7D03
Boost error load address in load error table: matches.

Also if anyone has the logging data line for Evoscan for the 5269xxxx roms, I would appreciate the sharing...

 

Make the (20 & 17.5 areas of the boost correction table 0)

 

Tephra you are the boss!

 

OMG, you just made my day. I never thought of not having it add WGDC when it is way off. Maybe I'll just make it a small number, like 1, so if it is way under target, it can still try to build some more... but making it 5 when the cap is 10 means it only takes 2 correction steps to max the system out. But at a 1, it would still take 10 correction steps.. and the turbo will have spooled by then.