Quote:
Originally Posted by adrian@vishnu
Mike, not sure if you have actually driven a dyno, but the last thing you want to do is a very quick shift. The rollers have so much inertia that they will not accelerate quick enough and the car will try to jump forward and/or spin the tyres on the dyno. Not only is this unsafe, but the dyno will not accurately read the power difference as it can only respond to the rollers and the rollers did not respond... the car position/tyre slip did.
The best way to get some objective results is datalogging. This way the driver can also be monitored to make sure they are are changing gears in the same way and not effecting the results by going easier on the gear change on one tune.
As long as enough and the correct channels are logged, datalogs are the great equaliser, as any funny business is immediately evident in the logged data.
It would need to be done on the same car since mods can effect the turbo spool also.
As the Procede can actually view the DBW throttle position, it does have a distinct advantage in implementing this feature. It would certainly be interesting to see if a non-CAN approach can match or better it.
|
Hi Adrian,
The dyno seems like the best option.
Neither a BT or V3 datalog is going to show us how much boost is being held through shifts, only whether or not the throttle blade is open, and what the boost level is in front of the throttle body. It's also not going to show how smoothly that boost is being applied. Doing full 1/4 mile passes on the dyno is very common and a great way to troubleshoot shifting related issues. This goes without saying but datalogs will also be captured to correlate to the runs.
Is it possible to enable the V3 to log via the BT cable? This would greatly simplify things. Many relevant parameters are blocked out / not viewable in the V3, like target boost. Also since TPS is being sampled directly it won't have the same latency you would see picking that signal off the filtered CANbus.
Mike