[OpenFlash]

Say goodbye to custom tuning and datalogging. Time to let a computer do it for you automatically.

Background:
This shouldn't come as a surprise to Procede users. But to others, it's important to point out that the Procede was developed to be the last tune you will ever need. And one that can satisfy the needs of any end user. For mild to wild. From those who just want to pick up an additional 70whp running the baseline maps and never use their laptop. To those who are always hunting for the last 10-30whp and aren't shy about conducting and analysing datalogs.

With v4, we've made custom tuning easier than ever since all our "wilder" users by adding datalog log channels that aren't available with other tunes (actual throttle, actual ignition advance, dme boost, dme target, etc,) These CANbus channels provide info that takes the guesswork out of custom tuning. Not to mention separating the factory's silly IAT compensations from our tune's boost control system. This meant no need to fiddle with IAT adjustments/decays when ambient conditions change in the quest for full boost. We've also stabilized throttle blade activity to give our boost control system a level of stability that no other tune, reflash or piggyback, comes close to offering. Add to that a total elimination of shift-bog, software-dependent lag, throttle delay and other n54 idiosyncrasies that we've all had to deal with for years. All in all, it's been a long and rewarding process to solve each and every issue that that has cropped up along the way.

Less Work. Better Results.
But now we are starting the next evolution of the Procede software. One that takes the user out of the equation. No longer will it be necessary for our power-maximizing users to conduct and interpret logged data in order to make adjustments to their own tune. This was always the end goal. We just took our time to make sure that we were feeding the Procede all the necessary input data. Without sufficient input data, auto-tuning simply isn't possible. But when configured correctly, auto-tuning has many many benefits over conventional custom tuning:

1) Auto-tuning is always active. And is basing it's tune customization on data that is recorded EVERY TIME the engine goes under load. Which means that it will constantly adapt to changes in conditions (ambient temp, octane, IAT, etc,) This simply isn't feasible with conventional manual custom tuning where the user-induced changes only really apply to the test conditions the few datalogs were conducted in.

2) Computers are far better at assessing data than you and me. This means that the Procede is not only keeping track of the number of ignition "drop outs" (indicating knock activity) but also the severity and persistence of those drop outs.

3) Laptop not required. Many of us do crazy things like run our cars at the dragstrip. This often means dumping in race gas, hooking up the computer and raising boost and dropping correction. The idea behind auto-tuning is that the user can simply add the race gas, do a few learning runs on the road (or strip) and the Procede will automatically drop ignition correction and raise boost to the limit of which the octane level will support. No need for fiddling with the computer at the track. This leaves more time for eating french fries and nachos at the concession stand.

4) Just in case you think that Auto-tuning will result in self-awareness and Judgement Day-like catastrophe, don't worry. The user will have the ability to put "limits" on max learned Boost and Ignition Correction values. So if you only want to run a max of say 12psi regardless of how knock-free and conservatively you are running, you can do that. So yes, this auto-tuning logic will benefit those who aren't wild power mongers as well.


So How Does it Work?
Quite elegantly as a matter of fact. Every time a few conditions are satisfied (above a certain load, in a gear, above a certain temp, etc,.) the Procede actively monitors CAN DME Ignition advance (Actual advance minus Procede-induced timing correction). It compares the real-time ignition advance value to the DME ignition advance target which we have internally mapped as a 16x16 RPM x Load table and subjected to IAT-induced trims. The difference between DME ignition advance target and CAN DME Ignition is DME-induced ignition retard. This is not to be mistaken for the ignition correction that the Procede induces based upon it's mapping. Instead, this DME-induced ignition retard is based upon, and reactive to, actual Knock activity.

The Procede then takes this instantaneous Knock activity value, which is represented in degrees (0=0 deg of knock retard, 10=10 deg of knock retard) and constantly updates an internally calculated running average function. This running average represents the current Aggressiveness of the tune. So as operating conditions get worse (ambient temp goes up, octane/fuel quality goes down, car is driven harder and harder, etc,), the average knock retard (aka Aggressiveness) starts to rise. And as conditions get better, it will start to fall. The rate at which this Aggressiveness value changes with time depends on the sample duration of the running average calculation. Set to one extreme, we can have the Procede respond to changes very quickly within 1 single gear WOT pull. But at the cost of stability. Set to the other extreme, it could take dozens of WOT pulls before the Procede can accurate assess the tune's current level of aggressiveness. Needless to say, we settled on a more moderate setting, requiring just 3-4 partial gear pulls to determine the tune's level of Aggressiveness.

DEMO #1
For this first demo, we are just going to show how well the Procede recognizes the tune's current level of aggressiveness. We are not going to show what it does with this data just yet. That is actually the easy part. The hard part (which is simply impossible with other tunes) is, and will always be, to internally monitor how well the current tune is working on your car. Reflashes can tell this since they can monitor the same knock data that we see. But they don't have the adjustment range to do much with it! On the other hands, conventional piggybacks have the some degree of adjustments (ie, boost level manipulation and, at times, timing control) but they have NO ability to monitor how well the tune is working! So that sucks.

In the following datalog, the tune is running approx 15psi of boost on 91oct. Ignition Correction is set to 0 (no Procede-induced timing retard). So it is completely up to the DME to react to knock. This is just an extreme case to show the effectiveness of this new logic. This is not a tune that I would recommend. I did 10 partial gear 3rd and 4th gear pulls. For the first 2 pulls, the was running on pump gas only. For pulls #3-7, methanol injection was enabled. For pulls #8-10, methanol was disabled again.

You can see the Aggressiveness parameter increase quickly from 0 to 6-7 in the first 2 pulls when meth isn't active. If I continued to run with no meth, it would stay in this range or thereabouts.

Then methanol was turned on. Methanol, as you know, cools IAT and increases effective octane. It has the ability to turn a "far too aggressive" tune that is knocking and running inconsistently into a great tune that offers solid consistent AND safe power. Once methanol was injected during the pulls, you can see the Procede IMMEDIATELY recognize the change in Aggressiveness. With in a few pulls, Aggressiveness falls to nearly 0.

Then, just to confirm, methanol was turned off for the last few runs. And, as you would expect, the Procede immediately recognizes the presence of knock retard and ramps ups the Aggressiveness level back up to 6-7.

So with the ability to recognize how over or under aggressive any given tune is, at any given time, the Procede will do things that you have always wanted a tune to do but were too afraid to ask

But you'll see that in Demo #2 later this week...

[OpenFlash]

Reserved 2

[stratplaya06]

[ridin135]

lol got to excited and jumped in the thread to early

[dzenno]

teasing is for strippers

[pcmike]

Subscribing....

[Bimmer This]

[Parachute>Seatbelts]

[jpsimon]

I'm going back to Vegas on Friday, there will be enough teasing there. Get to the good stuff now!!

[JacksonHandy]

[zsapphire7]

!

[lamia2super]

Originally Posted by dzenno

teasing is for strippers

+1

[Ferre86]

!! wow just wow !!

V4 Rules!

[migue90]

sounds nice

[mwahlert]

[Ajvar]

oooooooooooooooooooooooh yes

[scottp999]

Bring on the demo!

[lyndon_h]

hopefully, Shiv can work in "FTW" in the demo.

[forza1976]

Good stuff!

[huyner328]

Interested to see the methodologies used to tune the car via computer. Kiiiiiiinda cool. Additionally, the perceived pros and cons vs. the traditional methods.

[ala012]

This is main reason why I switched from JB3 to Procede.

[Ghost170]

When this gets up and running, I'm gonna switch out my old proceed!!!