[OpenFlash]

Originally Posted by luca335i

Ok now I get it. But how do I log meth flow with the p-reader. What channel should I add? I wann make sure its working.

The channel to log is Debug Byte 7 (Meth %). It's all explained in the documentation. Just make sure you put the new datalog configuration files that I attached along with the new 4-15 maps in your procede folder. That will automatically set everything up for you so that you have to do absolutely nothing. Just log it. See what the max steady value is (ignore quick spikes) and put that value into Future Use 1. Just make sure you adjust the meth controller to be spraying at its max. Real easy.

Shiv

[OpenFlash]

Originally Posted by luca335i

Is DTC map switching enabled in prog. meth mode? Or does it switch back and forth according to meth flow?

It is disabled. You will see the SES light flash but there will not be any map switch when in Progressive Meth mode. Map "switching" is completely dependant on the meth flow input signal.

Shiv

[OpenFlash]

Originally Posted by Undies

I thought 1-2 is the most conservative.

Shiv - 4 is the value at cruise. when i full throttle it dropss to 3.5 and 3.7, and rarely goes to 4.2. are these not safe debug byte 6 values for a completely stock car?

The value only updates under boost. If u see 4.2 at cruise, it is because that is the last updated value under boost. That value is fine if not just a little aggressive. You can try running more consevative settings to bring it down a bit. Or just wait for the next update and let the Procede just adjust itself.

Shiv

[OpenFlash]

Originally Posted by cocoturkey

When I'm dataloging (3rd gear WOT) and trying to find the max value of "debug byte 7" for "feature use 1'', do i use firmware #009, 4-15 map and set feature use 1 value to "1" ?

It doesn't matter either way. Might as well keep it set to 0 though. Until you have the right value to put in.

[OpenFlash]

Originally Posted by dzenno

Shiv -

Any chance you could describe in a bit more detail how this value is calculated. I understand the high level in that its monitoring ign timing dropouts when in gear and when above certain rpm (>4300 rpm say to ignore the vanos change over)...how do you arrive at this aggresiveness number? What does say 2.0 represent?

The vanos induced retard is not ignored. And there is no rpm threshold below which this value is not updated. And there are some shift-induced timing retards which are also averaged into the agression value. Which is why it's going to be impossible (or highly unlikely) to ever see a value of 0. Even on race gas.

This aggression value is a running average of the differences between dme target ignition advance and current dme ignition advance. With some additional conditional logic thrown in to filter out conditions where timing will naturally drop which would bias the reading.

We are still early in the game with respect to "ideal" value for max power. So far all we have established is that this value goes up the more the dme responds to knock and down the less it responds to knock. This makes the value an excellent indicator of required octane.

Based upon what we've seen so far, a value of 2 is just fine. You will see this value change as u drive. This is expected and exactly what the procede will react to.

Shiv

[AltecBX]

Shiv, I know you said it's a running average of the differences between dme target ignition advance and current dme ignition advance, but are there set RPM triggers that makes this happen? I've notice the Aggression level does not change after it peaked until I rev it again over 3200 RPM. If the peak stays at 1.7, it doesn't go down until I rev it back above 3200 RPM. The same in reverse, it doesn't raise higher until I rev it over 4300 RPM.

Another observation:
Why I only get readings by .02 & .03. I was data-logging all night and notice this pattern. It starts with .02 then adds .03 then adds .02 then adds .03, etc..

For example the aggression levels are:
0.2 - 0.5 - 0.7 - 1.0 - 1.2 - 1.5 - 1.7 - 2.0 - 2.2 - 2.5 - 2.7 - 3.0

Is this on purpose? If this is from 0-10, there will be a 40 value entry. {4(.02,.05,.07,1.0) x 10}
Will there be aggression level values that we will see like .01, .03, .04, etc..?

[cn555ic]

I also have not seen values higher than .05 I guess my fully modded car settings can be set more aggressively

[OpenFlash]

Originally Posted by AltecBX

Shiv, I know you said it's a running average of the differences between dme target ignition advance and current dme ignition advance, but are there set RPM triggers that makes this happen? I've notice the Aggression level does not change after it peaked until I rev it again over 3200 RPM. If the peak stays at 1.7, it doesn't go down until I rev it back above 3200 RPM. The same in reverse, it doesn't raise higher until I rev it over 4300 RPM.

Another observation:
Why I only get readings by .02 & .03. I was data-logging all night and notice this pattern. It starts with .02 then adds .03 then adds .02 then adds .03, etc..

For example the aggression levels are:
0.2 - 0.5 - 0.7 - 1.0 - 1.2 - 1.5 - 1.7 - 2.0 - 2.2 - 2.5 - 2.7 - 3.0

Is this on purpose? If this is from 0-10, there will be a 40 value entry. {4(.02,.05,.07,1.0) x 10}
Will there be aggression level values that we will see like .01, .03, .04, etc..?

There us no rpm threshold for updating. And just because the value isn't changing doesn't mean that it isn't updating. It is just updating with the same value.

And yes, it will change in .3 increments. That's normal.

[MFKN3]

Originally Posted by Undies

I thought 1-2 is the most conservative.

Shiv - 4 is the value at cruise. when i full throttle it dropss to 3.5 and 3.7, and rarely goes to 4.2. are these not safe debug byte 6 values for a completely stock car?

Some people can't read Shiv's basic instructions

[Glowin]

Originally Posted by themyst

In terms of the 6MT bogging, Shiv provided an explanation that makes perfect sense. I will relog based on his suggestions and post accordingly.

AND? Aren't you going to tell us what the explanation was?

[harry$]

Originally Posted by shiv@vishnu

The value only updates under boost. If u see 4.2 at cruise, it is because that is the last updated value under boost. That value is fine if not just a little aggressive. You can try running more consevative settings to bring it down a bit. Or just wait for the next update and let the Procede just adjust itself.

Shiv

shiv when will the next update be available?

[harry$]

Originally Posted by harry$

shiv when will the next update be available?

Any guess as to when the next update will be available?

[alextremo]

Shiv - are you still suggesting we don't use the launch control function? Can it be turned off in the software? If not, is there a way to brake boost without engaging the launch control?

Thanks.

[OpenFlash]

Here!

Despite the name change (4-15 to 4-30), the maps are the same. As are the datalog files. The only difference is the new firmware file (#10, replacing #9). This little update should solve the CANclear related bug that some of you guys have experienced (12542 code). Everything else is exactly the same.

If there are any other issues with the beta maps/firmware, please email me directly at shiv@vishnutuning.com.

There are new updates coming next week. But I just wanted to get this little bug sorted out in time for the weekend. Enjoy!

Cheers,
Shiv

[Overboost]

Gettin sooo jealous... wish u had the procedes in stock so i can finally get a tracking number. Shiv let me know if we can work something out so i can get mine soon. (Already ordered)

[cn555ic]

Originally Posted by Overboost

Gettin sooo jealous... wish u had the procedes in stock so i can finally get a tracking number. Shiv let me know if we can work something out so i can get mine soon. (Already ordered)

Someone is selling a used one that you can get by next week in the for sale threads!! Thats the only way my friend!

[Overboost]

Originally Posted by cn555ic

Someone is selling a used one that you can get by next week in the for sale threads!! Thats the only way my friend!

I wish but i already placed my order so i'll just wait for now. I'll be patiend anyway because its finals week in college right now so i shouldnt even be on this site considering i'm sittin in the library forcing myself to study microbiology and biochem on a friday afternoon.

[alextremo]

Originally Posted by alextremo

Shiv - are you still suggesting we don't use the launch control function? Can it be turned off in the software? If not, is there a way to brake boost without engaging the launch control?

Thanks.

Shiv-bump

[themyst]

Does this mean next week's update will include a functional autotune? Spill the beans!

[lyndon_h]

Originally Posted by Overboost

Gettin sooo jealous... wish u had the procedes in stock so i can finally get a tracking number. Shiv let me know if we can work something out so i can get mine soon. (Already ordered)

No kidding. I want to order one at the same time I order a JB3 so i can compare them. The only problem is that the procede's are never in stock. Getting impatient. The money is burning a hole in my wallet...

[OpenFlash]

Originally Posted by lyndon_h

No kidding. I want to order one at the same time I order a JB3 so i can compare them. The only problem is that the procede's are never in stock. Getting impatient. The money is burning a hole in my wallet...

Actually, Procedes are almost always in stock. Unique circumstances (global shortage of a single source $1.50 component) pwn3d use this time. But after this batch, we are adopting a substitute component that is far more readily available. So we don't expect this issue ever again.

The good news is that it gives me a little break to get a couple very important features up and running. I'm a glass half full kind of guy...

This current batch that we are waiting for is already almost sold out. So we have already started another batch that will put an end of this out-of-stock nonsense for a very long time.

If you are leaning towards the Procede, try not to let impatience get the best of you and get you to get something else. I think you'll be very upset if you did.

Cheers
shiv

[themyst]

I'm sure all this autotune and in-dash display talk will pent up Procede demand.