[OpenFlash]

In dash gauge is in the works. Along with other things. Just doing important tune related functional stuff first. The things you feel Everytime you put your right foot down.

[cincy335i]

Originally Posted by shiv@vishnu

In dash gauge is in the works. Along with other things. Just doing important tune related functional stuff first. The things you feel Everytime you put your right foot down.

[D.B.S]

Originally Posted by NetVader

Some tuners have a history of inadequate safety nets, search is your friend. These sound like steps in the right direction though.

Search is everyone friend, but from what I've read on majority of the tunes, only a couple have some safety built into them... I'm not looking to spend 2k on a Dinan tune (specially when a few members have had issues getting warranty work from them). JB seems like a good tune, but seems to be geared more towards absolute performance. PROcede seems to have a gearing towards performance (not extreme performance) but a good amount as well as having data logging capabilities, which comes in handy... I'm sure there are a few other tunes I haven't mentioned... Of the three I've mentioned though, I was on the ropes with the JB and the PROcede, but after reading about these new additions to the programming, i think for me this is a better choice... Each person has to make their own choice as to whats best for their application... I don't want all out performance (like the JB tune gives) I want the tune that gives me good performance gains but also a safety net for the 'what ifs'

[bimdaddy]

Shiv, very impressive work! Now translate to English please

[cincy335i]

Originally Posted by Army335xi

Search is everyone friend, but from what I've read on majority of the tunes, only a couple have some safety built into them... I'm not looking to spend 2k on a Dinan tune (specially when a few members have had issues getting warranty work from them). JB seems like a good tune, but seems to be geared more towards absolute performance. PROcede seems to have a gearing towards performance (not extreme performance) but a good amount as well as having data logging capabilities, which comes in handy... I'm sure there are a few other tunes I haven't mentioned... Of the three I've mentioned though, I was on the ropes with the JB and the PROcede, but after reading about these new additions to the programming, i think for me this is a better choice... Each person has to make their own choice as to whats best for their application... I don't want all out performance (like the JB tune gives) I want the tune that gives me good performance gains but also a safety net for the 'what ifs'

I agree with you...it's your choice, your car and if you go the PROcede route, it is a good choice for what you want and expect. I too had the same choice and went the PROcede route, same concerns and I all I can tell you is that I love the tune. The JB tunes are great, but for me the PROcede is better and the way to go for me, but to each his own. After all we all love our Bimmers and want the most out of them, but all have different likes and dislikes about how we get what we want.

Keep up the good work Shiv!

[scalbert]

Originally Posted by NetVader

For these new channels, they appear to be the low speed OBDII channels? How is knock count calculated?

With all due respect, 5 minutes working with OBDII would enlighten you that most of this data is not available via OBDII. I would ask that if you are trying to make an assertion, at least have the facts straight.

While some GM tools do record items such as knock count, they are still not OBDII only. OBDII only is very limited.

Lastly, OBDII does not reside on the CANBus, so again, incorrect information.

[lawdude]

Originally Posted by TheTwinz

I don't get it, you are trying to mock me, but you don't realize that it was Shiv and not I that used the term "coexist peacefully".. I was making fun of his choice of words...

Yep, having a little fun at your expense using cold war humor.

[scalbert]

Looking forward to putting this through its paces.

[Sniz]

lol at some of you guys

looks like very very cool stuff

well done

[Vudoo4u2]

Originally Posted by shiv@vishnu

In dash gauge is in the works. Along with other things. Just doing important tune related functional stuff first. The things you feel Everytime you put your right foot down.

you mean function first!? crazy talk

[OpenFlash]

Originally Posted by scalbert

With all due respect, 5 minutes working with OBDII would enlighten you that most of this data is not available via OBDII. I would ask that if you are trying to make an assertion, at least have the facts straight.

While some GM tools do record items such as knock count, they are still not OBDII only. OBDII only is very limited.

Lastly, OBDII does not reside on the CANBus, so again, incorrect information.

+1

Plus, we are currently logging each CANbus data channel at 10 samples/sec. Way faster than limited OBD data.

Shiv

[marcvtec]

Looks good nice job !!!

[ontopofm]

Originally Posted by NetVader

For those that missed them, here are the Vishnu results from the dyno day.

5) Procede Rev2 CanBus Stage 1, DCI, magnaflow section 3, 91Oct: 337whp, 357torque
6) Procede Rev1 Stage 3, DCI, VK FMIC, AR DPs, 2nd cat delete, 91Oct: 367whp, 369torque
7) Procede Rev2 CanBus Stage 2, Injen DCI, Helix Fmic, 91Oct: 361whp, 353torque
8) Procede Rev2 CanBus Stage 1, DCI, HKS BOV, 100Oct: 326whp, 361torque

For these new channels, they appear to be the low speed OBDII channels? How is knock count calculated?

2ndary cats replaced with Magnaflow High Flow Cats, so I still have Cats in there

[OpenFlash]

Originally Posted by ontopofm

2ndary cats replaced with Magnaflow High Flow Cats, so I still have Cats in there

Sounds right for 91oct. You'd see another ~15whp with actual cat deletes.

[Vudoo4u2]

Originally Posted by shiv@vishnu

Sounds right for 91oct. You'd see another ~15whp with actual cat deletes.

firstly, i realize id have to visit a dyno to confirm no matter what...but

since ~15whp/wtq would get him in the 380 whp/wtq range...what is necessary to get to the 400whp mark? just race gas? seems like once you are at stage 3 youve got everything on...just race maps would get you that last 20 whp or so for now (pre meth etc etc) yea?

(not that the sheer who mark really makes a diff..just for my own mental boy racer intuition)

[OpenFlash]

Originally Posted by Vudoo4u2

firstly, i realize id have to visit a dyno to confirm no matter what...but

since ~15whp/wtq would get him in the 380 whp/wtq range...what is necessary to get to the 400whp mark? just race gas? seems like once you are at stage 3 youve got everything on...just race maps would get you that last 20 whp or so for now (pre meth etc etc) yea?

(not that the sheer who mark really makes a diff..just for my own mental boy racer intuition)

A Stg 3 map, with race gas, and User Torque adjusted up to 100% will make a bit over 400whp at 16-17psi. To make more, reduce Ignition correction from 100% to 0% (basically turning it into a race gas map). This will make another ~20whp at the same boost level since you are basically adding the 3-4 degrees of timing that the PROcede took out for pump gas safety, back in. To make absolute max power (430-440whp), you'll have to run 18-19psi. Which is well past the point of deminishing returns and requires a map that we will only provide upon special request.

Shiv

[Slidewayz]

There's only so much you can do given the mass flow rate of the stock turbos in their efficiency range...

I'm guessing we're pretty much maxed out somewhere shy of 400 WHP on pump gas and no meth. Still, 350-375 WHP is nothing to sneeze at...that's over 400 WHP at the crank with big, greasy gobs of torque.

[Vudoo4u2]

Originally Posted by shiv@vishnu

A Stg 3 map, with race gas, and User Torque adjusted up to 100% will make a bit over 400whp at 16-17psi. To make more, reduce Ignition correction from 100% to 0% (basically turning it into a race gas map). This will make another ~20whp at the same boost level since you are basically adding the 3-4 degrees of timing that the PROcede took out for pump gas safety, back in.

Shiv

thanks vm

makes sense to me!

[OpenFlash]

Originally Posted by got psi

would it be safe to assume that you can now reduce ignition correction down to say 50% safely on a stage 1-3 map?

Not without verifying it first by monitoring timing/knock status. Especially on 91oct or in really hot/harsh conditions.

Shiv

[NetVader]

Originally Posted by scalbert

With all due respect, 5 minutes working with OBDII would enlighten you that most of this data is not available via OBDII. I would ask that if you are trying to make an assertion, at least have the facts straight.

While some GM tools do record items such as knock count, they are still not OBDII only. OBDII only is very limited.

Lastly, OBDII does not reside on the CANBus, so again, incorrect information.

There is no assertion here, simply a two part question! The new data that was presented here, oil temp, water temp, throttle blade position, and timing advance are all OBDII standard data. If there was other data that is not OBDII standard that was shown I missed it.

The second question was how the knock count was being computed, or is that not being computed and somehow being read directly from the ECU like you might view it in a scan tool? If people are going to rely on this data for their tuning they should have confidence it is accurate or not.

The data originates from the ECU and I think is output via the can bus using the OBDII can bus standard, that is how the smog computers interface the ECU to check for codes and monitor RPM.

[OpenFlash]

Originally Posted by NetVader

There is no assertion here, simply a two part question! The new data that was presented here, oil temp, water temp, throttle blade position, and timing advance are all OBDII standard data. If there was other data that is not OBDII standard that was shown I missed it.

No. Throttle blade position isn't standard OBD2 info. Nor is oil temp, IIRC. OBD2 is primarily an emissions related system. This is why it does not show much of the useful stuff.

The second question was how the knock count was being computed, or is that not being computed and somehow being read directly from the ECU like you might view it in a scan tool? If people are going to rely on this data for their tuning they should have confidence it is accurate or not.

One of the factory DME parameters is Knock Status. When it detects knock, it counts 1. When it does that twice, we add 1 plus 1. When it does it 5 times, we add 1+1+1+1+1 and come up with 5. To be fancy, we will weigh that count with how long the engine has been running under boost to get a good representation of knock tendency.

Shiv

[BimmerPod]

from an enthusiast that loves and cares for his cars, thank you Shiv.