[Cyruz]

not gonna be able to do more runs tonight, wife is coming home - maybe tomorrow or sat if i can get some free time. but i will try to get it for you

[Joshboody]

Thanks Shiv, I always have many questions, and you always have very informative responses... so much thought goes into your tune. One day i'll pull the trigger on a purchase.

Timing correction is very important in 3rd, but from my logs 1st and 2nd may not need as much cause of the decreased load. Any thoughts for customized maps per gear in the future? timing target looks to be at least 2deg difference from 2nd to 3rd. And if you were doing high speed runs, increased retard correction would be very important i would think.

[Kelvin1000]

In about two weeks, we will be doing away with ~75% of our existing boost control logic and adopting something MUCH more effective

Do tell... it seems pretty good the way it is right now...

[OpenFlash]

Originally Posted by Kelvin1000

Do tell... it seems pretty good the way it is right now...

It does work well. However, we achieved this by adding code upon code upon code. Lots of enhancements to eliminate instability while improving response while making the whole thing user adjustable within a certain throttle/boost response range.

Short story:
This whole boost control scheme started life back with PROcede v2 when we only had access to 3 sensor signal/inputs. We used a simple % increase function with respect to DCin/DC out to support the increased boost targets. Then with v3, we added a couple more sensor inputs that improved stability/adaptability. Then made the offset additive instead of multiplicative. Then gave it its own 16x16 3d table. Then added a global offset that activates during quick changes of throttle. Then added a closed loop PID system designed to keep DCin within a certain plausible range. Then added various corrections to keep throttle open as much as possible, during the engine conditions that were important to us. ALL of this was done to make sure that the DC output resulted in an ACTUAL boost pressure that is as close as possible to the DESIRED boost target.

Well since we can now read actual boost target through a CANbus channel (with rev.2 only), we can make our PID system control actual boost in an effort to keep boost ERROR (Actual-Target) at or close to 0%.

This simple logic structure eliminates just about all the patchwork we've done in the last 3 years and steps up the game a few BIG notches with respect to stability, response time AND desired throttle activity. In other words, we don't have to undershoot targets to keep throttle open most of the time. We can hit the targets DEAD ON and modulate DC from there. This means max power and max response with no side effects.

This also means that the boost control logic, unlike what you would see in other tuning platforms (reflashes included) will be self-corrected. It wont matter what combinations of mods you have as the PROcede will adapt to it immediately. This is especially important now that upgraded turbos are hitting the market. Up until now, we had to re-map the boost offset DC table (and associated tables) from scratch to accommodate any 1 particular turbo upgrade. This will no longer the case very soon.

So yes, it's very exciting. And yes, CANbus integration really changes the game and gives us a huge advantage over the other tuning systems, flashes or piggybacks.

Cheers,
shiv

[Kelvin1000]

Sounds great and sounds like you should put this in a new thread.

It also sounds like you might need some beta testers...

[kenneth]

mmmmhhhh yummy!

Does that mean one or two steps closer to autotune?

[OpenFlash]

Originally Posted by Kelvin1000

Sounds great and sounds like you should put this in a new thread.

It also sounds like you might need some beta testers...

Yes and yes. But still another week away before we release that. Still focusing right now an the latest beta map with respect to o2 sim and misfire. But you know what's coming

shiv

[OpenFlash]

Originally Posted by kenneth

mmmmhhhh yummy!

Does that mean one or two steps closer to autotune?

Let's just say that it is one out of three steps towards autotuning. But it's the one most people will take advantage of the most.

Shiv

[Kelvin1000]

Originally Posted by shiv@vishnu

It does work well. However, we achieved this by adding code upon code upon code. Lots of enhancements to eliminate instability while improving response while making the whole thing user adjustable within a certain throttle/boost response range.

Short story:
This whole boost control scheme started life back with PROcede v2 when we only had access to 3 sensor signal/inputs. We used a simple % increase function with respect to DCin/DC out to support the increased boost targets. Then with v3, we added a couple more sensor inputs that improved stability/adaptability. Then made the offset additive instead of multiplicative. Then gave it its own 16x16 3d table. Then added a global offset that activates during quick changes of throttle. Then added a closed loop PID system designed to keep DCin within a certain plausible range. Then added various corrections to keep throttle open as much as possible, during the engine conditions that were important to us. ALL of this was done to make sure that the DC output resulted in an ACTUAL boost pressure that is as close as possible to the DESIRED boost target.

Well since we can now read actual boost target through a CANbus channel (with rev.2 only), we can make our PID system control actual boost in an effort to keep boost ERROR (Actual-Target) at or close to 0%.

This simple logic structure eliminates just about all the patchwork we've done in the last 3 years and steps up the game a few BIG notches with respect to stability, response time AND desired throttle activity. In other words, we don't have to undershoot targets to keep throttle open most of the time. We can hit the targets DEAD ON and modulate DC from there. This means max power and max response with no side effects.

This also means that the boost control logic, unlike what you would see in other tuning platforms (reflashes included) will be self-corrected. It wont matter what combinations of mods you have as the PROcede will adapt to it immediately. This is especially important now that upgraded turbos are hitting the market. Up until now, we had to re-map the boost offset DC table (and associated tables) from scratch to accommodate any 1 particular turbo upgrade. This will no longer the case very soon.

So yes, it's very exciting. And yes, CANbus integration really changes the game and gives us a huge advantage over the other tuning systems, flashes or piggybacks.

Cheers,
shiv

I love when things have less moving parts. Simplicity is often underrated...

[kenneth]

Did you try different ways of mashing of the throttle? Perhaps you are being too smooth....

[Kelvin1000]

Originally Posted by shiv@vishnu

Let's just say that it is one out of three steps towards autotuning. But it's the one most people will take advantage of the most.

Shiv

Less compromises = More Fun

[JacksonHandy]

Originally Posted by Nick.CBR

lol - me too

For whatever reason my 6AT car has almost zero traction issues. Did 330 rwhp the other day so I know she's running strong but just refuses to burn the tires. I do have 265/19's out back which probably helps traction...

Nick

Haha yeah. I've got 265s but they're not on right now because of the winter times.

Shiv,

DIBS on beta testing the new stuff.