View Single Post
Old 09-17-2016, 12:49 PM   #52 (permalink)
Jhill
Track Member
 
Join Date: Mar 2016
Location: San jose
Posts: 846
Drives: 2013 370z sport
Rep Power: 3384
Jhill has a reputation beyond reputeJhill has a reputation beyond reputeJhill has a reputation beyond reputeJhill has a reputation beyond reputeJhill has a reputation beyond reputeJhill has a reputation beyond reputeJhill has a reputation beyond reputeJhill has a reputation beyond reputeJhill has a reputation beyond reputeJhill has a reputation beyond reputeJhill has a reputation beyond repute
Default

Quote:
Originally Posted by VitViper View Post
Just settle on the fact your ECUTek map can't and won't do what the MoTeC ecu is doing. In fact I have yet to see any OEM ECU do this as they just implement VDC and the goal is just to keep you from dying and not optimizing acceleration.

Timing retard does not work. Throttle closure does not work.

We target a set driven wheel speed based on non driven speed and hold it there. The driven wheel speed must ALWAYS be a certain amount faster than non driven to have "acceleration" (otherwise you're standing still lol). When you have too much is what "overslip" or "wheel spin" -- the tire couldn't hold traction and RPM takes off and you spin. This won't ever happen with a proper M1 setup. It'll just hold. The how and why is beyond the scope of this thread, lol.

Best I can do is show you -- this is of our 910whp FWD cars (about 750 in the video). Video has a tach & vehicle speed playback part way in, you can see the RPM never breaks out into wheel spin.

https://www.youtube.com/watch?v=6N2IqmAYkxw
Ok I think the video helps. Looks like it's doing it through a fuel cut so the rpm stays down.
Jhill is offline   Reply With Quote