Ok - I recompiled my advanced boost controll patch - so i will be easilly ported to any ecu..Ready to release final howto... But I have some questions to the community about how to make it perfect at once...

The first version discusssed here http://www.aktivematrix.com/forum/viewtopic.php?t=345

What I have now
-5 3d tables WGDUTY=F(LOAD,RPM) .Size suggestions?
Each table used for each gear.
1- Lowboost table for clothed throttle.

2d Table to detect gears comparing calculated RPM/SPEED value with the boundaries.

How it works:
It detects gear and uses an appropriate table, gets WGDUTY1 from the table.
It takes WGDUTY2 from the low-throttle table and makes approximation like used between Hioctane and Lowoctane maps -so if you have TPS=100% it takes WGDUTY1 if TPS=0% it takes WGDUTY2 if TPS=50% it takes (WGDUTY1+WGDUTY2)/2 .
I did it to make boost lower on part throttle because in my config if i lift up a throttle a half after 28 psi of boost i can cruise with turbo flowing to blowoff quite a long time....

I decided to remove the boost retard on knock - cause it moves you down the load axis and makes impossible to tune correctly...

Also removed lower boost mode if CE- if you see CE and afraid you can drive half throttle.

Any suggestions???

And the main question...
I have both MAP sensor and LOAD calculated from MAS- I have load orientated tables-athough in my case they are close to boost in KPA i see. I think its more correct to limit load cause load is already calculated the boost incide the cylinder..If you put wider cams you will get more boost incide in higher RPM due to VE and its more correct to rely on load...

 

Make mode also for euro cars there we dont have map and dont have any manuals how to install it.

 

It sounds like this is an open loop system without any correction is this true?

Or will it still be closed loop like stock where it adjusts your boost as necessary?

If it is open load then I would say Load on the axis makes sense.

However, if there is closed loop correction I would like to see it reference MAP sensor as the value to check.


I really like the idea of having the TPS interpolation and also the idea of having gear dependent boost, although I also would prefer to have it be closed loop so that weather changes or even load from going up or down a hill would be accounted for.

 

I thought it sounded like a closed loop system but i could be wrong.

 

It would be nice to keep the correction for air temps for people like me that live in SC, where we can see between 30's to 100's with anywhere between 0% and 4,984,295% humidity.

Maybe have the correction table be based on outside ambient air temperature?

 

Example table
www.bez-bashni.com/boosttable.JPG

I cannot classify its correctly - on one side its opened loop - hard numbers from the table - but you can make tabe with a form wich will reduce duty after some desired boost and it will not let boost rise in any conditions...So what? Closed or opened..?.

 

I would say open, and I see what you mean as far as entering values so if it starts getting to high a load, it will adjust itself. But you're not really adjusting the current value with a + or - another value but rather you are telling it a WGDC to have.

Without testing it would be hard to tell if this form of indirect correction would work well.

 

It works well... When I found that theres a little overboost on 5 gear I added gears..Of cause if you set correct duty...-it even doesnt osscilate.. The question what to add if I missed something...
P.S. In case of load-based boost correction theres already temperature comensation ...More temperature - less load..

 

I think its pretty complete then.

How do you plan to distribute it?

Do you also plan to do the same thing for your other rom mods.
I am very interested in the work you have done on both the anti-lag style two step and also the ability to set final timing.

 

the best thing also can be
1) desired boost on launch
2)and 2 maps for boost(high, very high) that can be changed during driving(some buttons)

 

may be you need something for you mods, to compensate your time and brain use... (dont now it is in english).
Couse your mods are quite important for avry one use ecuflesh and ALL OF US.
May be we can made fund of bezzz to send you some money use paypal ( that everyone whant\can) to thank you for your job.

 

Load is accessible to all people, map only to those with a jdm or moto map sensor.
Also all tables refer to load anyway, so i say might as well keep it with load.
I think main gripe with load is that it changes through gears and in this case there's a separate table for each gear, so that's a non-factor.

 

I agree that load method has wider application potential however it is very complex for the reasons you state. I think the map based would be a more reliable and predictable method.

 

I'd opt for the load based as it would suit a wider number of people. I have been thinking that load based setups would be better at compensating for change in temperature and air density.

MB