0-60mph times
- Thread starter john84
- Start date
ground speed left? you have an ABS sensor (or aftermarket) wired into the ecu for front wheel speed (and traction control I'm assuming?)
need to work on that boost control
need to work on that boost control
Sensors on all 4 wheels, the scaling makes the boost graph look much worse then it is along with the sample rate I was logging at.
On a real gauge you can't see any fluctuation.
Here's the same file stretched out a bit and Drive speed overlaid and you'll notice with TRAC off it's still turning the rears at just under 100Mph
On a real gauge you can't see any fluctuation.
Here's the same file stretched out a bit and Drive speed overlaid and you'll notice with TRAC off it's still turning the rears at just under 100Mph
from the graph it looks liek a 20-30 kPa variations along with the decent jumping around of the timing graph made it seem worse then it was I guess. I wish I had the coin for motec, looks like play with all that would be fun.
Your engine seems to run fairly cold.. where is the sensor located?
Your engine seems to run fairly cold.. where is the sensor located?
Sample rate is low so it looks much worse than it is in the real world as mentioned earlier.
<edit> Just went back through the ECU file that was in the car at that time and(your timing comment got my attention) The TRAC was pulling timing due to wheelspin and that was affecting the boost curve DOH.
The Logging option in my opinion should be standard in the MoTeC as it's an invaluable tool, you can go out do a pull log it come home and using "Lambda Was" adjust the fuel table, I can go from no tables to something that runs and drives quite well in 20>25 minutes
The Temp sensor was screwed into the Stock ECU sensor location, I was running a 77c T-Stat at the time.
<edit> Just went back through the ECU file that was in the car at that time and(your timing comment got my attention) The TRAC was pulling timing due to wheelspin and that was affecting the boost curve DOH.
The Logging option in my opinion should be standard in the MoTeC as it's an invaluable tool, you can go out do a pull log it come home and using "Lambda Was" adjust the fuel table, I can go from no tables to something that runs and drives quite well in 20>25 minutes
The Temp sensor was screwed into the Stock ECU sensor location, I was running a 77c T-Stat at the time.
come to wellsville MO, i'm waiting. lol, i have dynolicious, and let me tell you, its the best 12 bucks i've spent in a good while. I have tons of fun in it, making good matchup's for races, or just seeing what someone's beater runs for shits and grins.
Ahh, that would explain it. Its very quick reacting ehh? Very nice! makes me want motec even more. Off to the bank......IJ.;1340678 said:Sample rate is low so it looks much worse than it is in the real world as mentioned earlier.
<edit> Just went back through the ECU file that was in the car at that time and(your timing comment got my attention) The TRAC was pulling timing due to wheelspin and that was affecting the boost curve DOH.
The Logging option in my opinion should be standard in the MoTeC as it's an invaluable tool, you can go out do a pull log it come home and using "Lambda Was" adjust the fuel table, I can go from no tables to something that runs and drives quite well in 20>25 minutes
The Temp sensor was screwed into the Stock ECU sensor location, I was running a 77c T-Stat at the time.
:2ar15:
You can select a sample rate that gives a smooth graph (200 samples per second max) but I run as low a rate as I can as I've found at really high rates the log files can get buggy and miss data as it load balances.
You have a max of 64 things that can be logged at once in the Mx00 series.
You have a max of 64 things that can be logged at once in the Mx00 series.